# Authentication

**Mailzeet API endpoints** are secured with API keys, which you can create from the dashboard. You must include your API key in all API requests to the server as a header field.

To interact with the **Mailzeet API**, you must follow each of your requests with an **Authorization** header including your API key. 

**API keys must remain secret** and should not be used publicly. For better safety, always use the secret keys on the backend server as environment variables if possible. If you suspect your secret key has been compromised and you want to reset it, you can do so from the dashboard.

You can manage your API key from the dashboard, on the **Settings** page on the **Access key** tab.

<figure><img src="/files/oDLqh0w83DgAg7al7Tgu" alt=""><figcaption><p>Public API key</p></figcaption></figure>

### API key Authentication

Each API request should include the API key or token, sent within the Authorization header of the HTTP call using the Bearer method. For instance, a valid **Authorization header** looks like this: `Bearer faeawrafaf:01J2RJJBC6190R7GXK147HXNN5`.

Typically, our [SDKs](broken://pages/sTKNA3eyI69oIAv3RSNE) offer shortcuts to simplify setting the API key and interacting with the API.

In the example below, we use an API key for the POST method to send an email.

```bash
curl https://api.mailzeet.com/v1/mails
-H "Authorization: Bearer YOUR_SECRET_KEY"
-X POST
```

{% hint style="warning" %}
Do not set VERIFY\_PEER to FALSE. Ensure your server verifies the SSL connection to Moneroo.
{% endhint %}


---

# 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.mailzeet.com/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.