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

# Quickstart

> Create an API key and send one Hanto enrichment request.

This guide sends one request to the Hanto API and handles the two normal outcomes: `found` and `not_found`.

## Prerequisites

Before you begin, you need:

* Access to a Hanto workspace.
* An active Hanto API key.

## Send your first request

<Steps>
  <Step title="Create an API key">
    Sign in to Hanto, open **API keys**, and create a key for your integration.

    Copy the key when it is shown. Hanto shows the plaintext key only once.
  </Step>

  <Step title="Call the enrich endpoint">
    ```bash theme={null}
    curl https://api.hanto.ai/api/v1/person/enrich \
      -H "Authorization: Bearer sk_live_REPLACE_WITH_YOUR_KEY" \
      -H "Content-Type: application/json" \
      -d '{"email":"person@gmail.com"}'
    ```
  </Step>

  <Step title="Read the result">
    A found response returns a `200` status and a LinkedIn profile URL.

    ```json theme={null}
    {
      "lookup_id": "lookup_2F0knGH5CSqVAveuPlyCelx1",
      "status": "found",
      "profile": {
        "linkedin_url": "https://www.linkedin.com/in/person"
      }
    }
    ```

    A no-match response returns a `404` status and no `profile` object.

    ```json theme={null}
    {
      "lookup_id": "lookup_XbVW9yUdTzakGWNmZheBHvuV",
      "status": "not_found"
    }
    ```
  </Step>
</Steps>

## Next steps

* Review [authentication](/authentication) before storing a key in production.
* Review [errors and limits](/errors-and-limits) before adding retries.
* Read the [`POST /api/v1/person/enrich` reference](/api-reference/enrich-a-person) for the full contract.