> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/android/set-up-luciq-for-android/integrate-luciq-on-android/configure-custom-endpoints.md).

# Configuring Custom SDK Endpoints

By default, the Luciq SDK sends all data to Luciq's default production cluster. If your account is hosted on a different cluster — for example a regional cluster such as the **EU cluster**, or a dedicated deployment — you need to point the SDK at that cluster's endpoints so your data is routed to the correct location.

You configure custom endpoints using a `luciq_config.json` resource file. This is a one-time setup you do after integrating the SDK.

{% hint style="info" %}
Custom endpoints are only required if your Luciq account is provisioned on a non-default cluster. If you're using the default cluster, you can skip this page — no endpoint configuration is needed.
{% endhint %}

## Prerequisites

* Integrate the production SDK first, following the [Integrate Luciq on Android](/android/set-up-luciq-for-android/integrate-luciq-on-android.md) guide.
* Obtain the endpoints for your cluster from Luciq Support — these are not visible in your Luciq account.

## Configure the endpoints

#### Step 1: Create the configuration file

1. Create a folder named `raw` inside your app's `res` directory (if it doesn't already exist).
2. Inside the `raw` folder, create a file named `luciq_config.json`.

#### Step 2: Set the endpoint keys

Add the following to `luciq_config.json`, setting each key to your cluster's domain:

| Key            | Description                                                  |
| -------------- | ------------------------------------------------------------ |
| `luciq-domain` | Domain for the SDK (bug reporting, crashes, sessions, etc.). |
| `apm-domain`   | Domain for Application Performance Monitoring (APM).         |

{% code title="res/raw/luciq\_config.json" overflow="wrap" %}

```json
{
    "luciq-domain": "YOUR-SDK-DOMAIN",
    "apm-domain": "YOUR-APM-DOMAIN"
}
```

{% endcode %}

#### Step 3: Validate the configuration

Ensure the endpoints are reachable and correctly configured — the SDK sends all requests to the specified domains. Report a sample bug to confirm the data reaches your cluster.

## EU cluster

To route your data to the EU cluster, use the following domains:

| Key            | EU domain             |
| -------------- | --------------------- |
| `luciq-domain` | `api-eu.luciq.ai`     |
| `apm-domain`   | `api-eu-apm.luciq.ai` |

{% code title="res/raw/luciq\_config.json" overflow="wrap" %}

```json
{
    "luciq-domain": "api-eu.luciq.ai",
    "apm-domain": "api-eu-apm.luciq.ai"
}
```

{% endcode %}

{% hint style="info" %}
Make sure you also use the App Token generated for your EU account, not your default-cluster token.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/android/set-up-luciq-for-android/integrate-luciq-on-android/configure-custom-endpoints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.