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

# Younium

How to connect Younium to Churned.io\
Log in to the Churned platform and go to the “Integrations” section. Click on “New Integration” and select Younium from the list.

You will be prompted to enter the following credentials:

Required Credentials

* clientId – The client ID from your Younium developer app.
* clientSecret – The secret associated with your client ID.
* apiUrl – The base URL for Younium's API (e.g., <https://api.younium.com>).
* tenant – Your unique Younium tenant name or ID.

Here’s how you can obtain these credentials:

1. Contact Younium support or your customer success manager to register an API application.
2. Retrieve your clientId, clientSecret, and tenant info from the credentials page.
3. Use the Younium API base URL depending on your region (e.g., EU or US instance).

Input the Credentials\
Paste the client ID, secret, tenant, and API URL into the Churned integration form.

Click Save to test the connection. Once it’s working, notify the Churned team to begin syncing data.

Helpful Links

* Younium API Documentation
* Getting Started with Younium API<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.churned.io/churned-docs/integrations/younium.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.