> For the complete documentation index, see [llms.txt](https://developer.younium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.younium.com/documentation/developer-resources.md).

# Developer resources

API summaries

## API v2

API V2 is a RESTful API designed for transactional integrations and automation, well suited for CRUD‑style integrations where clients need to create, read, update or delete data in Younium. Common use cases involve managing accounts, products, subscription lifecycles and invoice flows.

[API references](/api-s/api-2.1.md)

[Resources](/documentation/developer-resources/developer-resources.md)

## Data Export API

Designed for exporting and syncing Younium data into data warehouses, BI platforms, and reporting systems. It is optimized for high-volume data retrieval, fetching records entity by entity and ensures speed and reliability.

[API references](/api-s/api-data_export.md)

[Resources](/documentation/developer-resources/api-v3-name.md)

## **Insights API**

**Insights API** provides external access to the structured data available in the Insights view of the Younium application. It exposes these data entities through a standard OData v4 interface, making it possible to query and filter the information using familiar OData syntax.

[Resources](/documentation/developer-resources/insights-api.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.younium.com/documentation/developer-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.