> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enrichley.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Making API calls

> How to make your first request to the Enrichley API.

# Making API calls

This guide walks you through making your first request to the Enrichley email validation API. Whether you are new to APIs or an experienced developer, the steps below will help you integrate Enrichley quickly.

## Quick start

### 1. Obtain your API key

1. Log in to the [Enrichley app](https://app.enrichley.io/sign-in).
2. [Sign up](https://app.enrichley.io/sign-up) for a paid plan if you haven’t already.
3. Go to your [account profile](https://app.enrichley.io/profile) and locate your **API key**.
4. Copy the key and store it securely.

API keys are generated automatically when you sign up for a paid plan and can be used across all Enrichley APIs.

### 2. Make your first API call

Use any HTTP client (curl, Postman, your backend language, etc.) to call the single email validation endpoint:

```bash theme={null}
curl -X POST "https://api.enrichley.io/api/v1/validate-single-email" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -d '{
    "email": "user@example.com"
  }'
```

* **URL:** `https://api.enrichley.io/api/v1/validate-single-email`
* **Method:** `POST`
* **Auth header:** `X-Api-Key: YOUR_API_KEY`

### 3. Check the response

A successful request returns a JSON object describing the status of the email address (for example, whether it’s valid and whether the domain is catch-all). The exact fields depend on your integration, but typically you’ll see:

* Whether it's valid (`true`or `false` ).
* The status of the email ( `ok `,`catch_all_validated`,`catch_all`,`unknown`,` or invalid )`
* Statuses `ok` and `catch_all_validated` are the only valid emails, the rest should not be emailed.

Use this response to decide how to treat the email in your application (send, suppress, or review).

> 💡 **Keep your key secret:** Treat your API key like a password. Never commit it to public repositories, client-side code, or share it in screenshots or support tickets.