> 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/ios/setup-luciq-for-ios/integrate-luciq-on-ios/configure-custom-endpoints.md).

# Configuring Custom SDK Endpoints

Point the Luciq iOS SDK at a custom cluster endpoint, such as a regional EU cluster or a dedicated deployment, using a LuciqConfig.plist file.

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 `LuciqConfig.plist` 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 iOS](/ios/setup-luciq-for-ios/integrate-luciq-on-ios.md) guide.
* Obtain the endpoints for your cluster from Luciq Support — these are not visible in your Luciq account.

## Configure the endpoints

#### Step 1: Add the configuration file

Add a `LuciqConfig.plist` file to your project and include it in the target that runs Luciq.

#### Step 2: Set the endpoint keys

Open `LuciqConfig.plist` and set the following keys to your cluster's endpoints:

| Key          | Description                                                    |
| ------------ | -------------------------------------------------------------- |
| `SDKBaseURL` | Base URL for the SDK (bug reporting, crashes, sessions, etc.). |
| `APMBaseURL` | Base URL for Application Performance Monitoring (APM).         |

{% code title="LuciqConfig.plist" overflow="wrap" %}

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>SDKBaseURL</key>
	<string>https://YOUR-SDK-ENDPOINT</string>
	<key>APMBaseURL</key>
	<string>https://YOUR-APM-ENDPOINT</string>
</dict>
</plist>
```

{% 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 endpoints:

| Key          | EU endpoint                   |
| ------------ | ----------------------------- |
| `SDKBaseURL` | `https://api-eu.luciq.ai`     |
| `APMBaseURL` | `https://api-eu-apm.luciq.ai` |

{% code title="LuciqConfig.plist" overflow="wrap" %}

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>SDKBaseURL</key>
	<string>https://api-eu.luciq.ai</string>
	<key>APMBaseURL</key>
	<string>https://api-eu-apm.luciq.ai</string>
</dict>
</plist>
```

{% 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 by asking a question.

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

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/integrate-luciq-on-ios/configure-custom-endpoints.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.