> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/developer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/developer/guides/api-authentication/request-api-credentials.md).

# Request API credentials

To access admin-level endpoints in the WLL API, you’ll need a set of admin credentials (client ID and secret). These are used to generate admin access tokens via OAuth2.

This article explains how to request your credentials and how they will be securely shared with you.

{% hint style="warning" %}
**Read this article in full before requesting credentials.**
{% endhint %}

***

## How to request credentials

To request your admin credentials, email [**support@whitelabel-loyalty.com**](mailto:support@whitelabel-loyalty.com) with the following:

* The name of your organization, your tenant slug (found in Loyalty Console > Settings), and the data centre your tenant is in
* The environments you need access to (staging, production, or both)
* A brief explanation of your intended usage (e.g. integration, admin reporting, reward management)
* A **secondary contact email** of a colleague

{% code title="Admin credentials request email template" %}

```
Hi WLL Support,

I need API admin credentials.

Organization name: [Insert organization name]
Tenant slug: [Insert tenant slug]
Data centre: EU or US (delete as applicable)

Environments: Staging / Production / Both

Intended usage: Detail intended usage here

Secondary contact: [Name] / [Email] / [Role]

Kind regards
```

{% endcode %}

***

## How credentials are delivered

To keep your credentials secure and compliant with SOC 2 best practices, we follow a two-contact process for delivery:

1. WLL Support generates your credentials and stores them in Bitwarden using Secure Send, with a **14-day expiry**.
2. The **Secure Send link** is emailed to the person requesting the credentials (who opened the support ticket).
3. The **password** to unlock the link is sent in a separate email to the **secondary contact**.

We aim to deliver API credentials within two working days of the request being made.

{% hint style="warning" %}
**Failure to supply all of the information outlined above in your first email will lead to delays in delivering your credentials.**
{% endhint %}