# API Keys

{% hint style="warning" %}
To execute via Lambda 2.0 with basic + advanced order types, telegram trading or via our alert feeds — you’ll need to connect to your preferred centralised exchange via secure API keys.
{% endhint %}

<figure><img src="https://miro.medium.com/max/712/1*9YB5Md9VVZMycevc-GfXaw.png" alt=""><figcaption><p>Lambda 2.0 — securely integrate your CEX account</p></figcaption></figure>

```
// Prior to enabling API integration, this documentation will be updated with extensive information to ensure absolute user security.
```

We will use a thoroughly tested + third party audited security layer for the **storage of user API keys** — we check to ensure that these keys are only ever enabled to be ‘trade only’ and never ‘withdraw or move funds’ — all routes have security guards + logs are monitored extremely closely.

<figure><img src="https://miro.medium.com/max/933/0*6pOWaDbmiF1OjiZM.png" alt=""><figcaption></figcaption></figure>

### Important:

For those who’d like to dive deeper on how we plan to treat user API keys:

{% embed url="<https://aws.amazon.com/kms/>" %}

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

<br>


---

# Agent Instructions: 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.lambda.markets/lambda-markets/getting-started/authentication/api-keys.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.