> For the complete documentation index, see [llms.txt](https://syticks.gitbook.io/merpi-by-syticks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://syticks.gitbook.io/merpi-by-syticks/api-keys-and-authentication.md).

# API Keys and Authentication

Every request you make to the MERPI API must include your API key and a transaction medium header. This page shows you where to find your keys and how to attach them correctly to your requests.

***

### Finding Your API Keys

In your Dashboard, go to **Settings > API Keys**. You will see two keys listed: one for the Staging environment and one for the Live environment.

<figure><img src="/files/RarQsXabITDJl6sF8Mp6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Never share your API keys or expose them in client-side code, public repositories, or anywhere visible to end users. If you suspect a key has been compromised, contact us at <hello@syticks.com> immediately.
{% endhint %}

***

### Required Headers

Every API request must include the following headers:

| Header              | Required | Description                                                        |
| ------------------- | -------- | ------------------------------------------------------------------ |
| `X-API-KEY`         | Yes      | Your MERPI API key (Staging or Live depending on your environment) |
| `TransactionMedium` | Yes      | The channel your request is coming from: `Web`, `Mobile`, or `POS` |
| `Content-Type`      | Yes      | Always `application/json`                                          |
| `Accept`            | Yes      | Always `application/json`                                          |

***

### Attaching Your Key to a Request

Here is an example of a correctly authenticated request using cURL:

```bash
curl https://api.syticks.com/api/v1/merpi/experience \
  -H "X-API-KEY: your_api_key_here" \
  -H "TransactionMedium: Web" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"
```

{% tabs %}
{% tab title="Web" %}
Use this when making requests from a website or web application.

```bash
curl https://api.syticks.com/api/v1/merpi/experience \
  -H "X-API-KEY: your_api_key_here" \
  -H "TransactionMedium: Web" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"
```

{% endtab %}

{% tab title="Mobile" %}
Use this when making requests from a mobile application (iOS or Android).

```bash
curl https://api.syticks.com/api/v1/merpi/experience \
  -H "X-API-KEY: your_api_key_here" \
  -H "TransactionMedium: Mobile" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"
```

{% endtab %}

{% tab title="POS" %}
Use this when making requests from a point-of-sale terminal.

```bash
curl https://api.syticks.com/api/v1/merpi/experience \
  -H "X-API-KEY: your_api_key_here" \
  -H "TransactionMedium: POS" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"
```

{% endtab %}
{% endtabs %}

***

### Staging vs Live Keys

Your Staging and Live keys are completely separate. Using the wrong key in the wrong environment will either cause requests to fail or result in unintended real transactions.

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><strong>Staging Key</strong></td><td align="center">Use during development and testing. Requests made with this key hit the Staging environment and use test wallet funds. No real money moves.</td></tr><tr><td align="center"><strong>Live Key</strong></td><td align="center">Use in production only. Requests made with this key are real transactions that charge your Live wallet and issue actual tickets.</td></tr></tbody></table>

***

### What's Next

With authentication set up, you have everything you need to start calling the API. Head to the Dashboard overview to understand what you can monitor and manage, or jump straight into the API reference.

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>The MERPI Dashboard</strong></td><td align="center">See what you can monitor, manage, and withdraw from your merchant portal.</td><td><a href="/pages/FKkU5mNF5CCBdIWaVlDW">/pages/FKkU5mNF5CCBdIWaVlDW</a></td></tr><tr><td align="center"><strong>Explore the API Reference</strong></td><td align="center">Browse all available endpoints across all ticket categories</td><td><a href="/pages/1EMlgvD45AWDsTadn69l">/pages/1EMlgvD45AWDsTadn69l</a></td></tr></tbody></table>


---

# 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://syticks.gitbook.io/merpi-by-syticks/api-keys-and-authentication.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.