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

# API Settings

> Configure Enrow API access, your API key, a default webhook URL, and the country_code parameter from the dashboard

API settings control how you access the Enrow API and how it behaves on every request. This page covers who can access the API, where to find your API key, how to set a default webhook URL, and how the `country_code` parameter changes search behavior.

## Who can access the Enrow API?

The Enrow API is available to customers with an **active subscription** or **pay-as-you-go credits**. If your account has neither, the API section won't be accessible. To see how credits are consumed per endpoint, see [Credits & billing](/credits-billing).

## Where do I find my API key?

Your API key is in the [Enrow Dashboard](https://app.enrow.io) — click **API** in the left menu and copy the key. The same key authenticates every endpoint through the `x-api-key` header. For request examples and error handling, see [Authentication](/authentication).

<Warning>
  Keep your API key secure. Never commit the API key to version control or share it publicly. Treat it like a password.
</Warning>

## How do I set a default webhook URL?

You can configure a default webhook URL in the dashboard. This URL is used whenever no `webhook` is specified in an individual request, so you don't have to repeat it on every call. A per-request `webhook` in the `settings` object always overrides the dashboard default.

For payload formats, retries, and security, see [How Webhooks Work](/how-webhooks-work).

## What does the country\_code parameter do?

The `country_code` parameter (ISO 3166-1 alpha-2) sets which local version of Google the API uses to resolve a company. Pass it in the `settings` object of your request. If nothing is provided, the default is `US`.

<Info>
  The country code is only useful when searching with `company_name` (not `company_domain`). It tells Enrow which local version of Google to use for resolving the company — for example, `google.de` for Germany or `google.fr` for France.
</Info>

The country code is particularly useful for **homonyms** — companies that share the same name in different countries:

```json theme={null}
// Dove the soap brand (UK)
{
  "company_name": "Dove",
  "fullname": "John Doe",
  "settings": { "country_code": "GB" }
}

// Dove the chocolate brand (Germany)
{
  "company_name": "Dove",
  "fullname": "Hans Müller",
  "settings": { "country_code": "DE" }
}
```

The `settings` object also accepts `webhook` (a per-request webhook URL), `retrieve_gender` (boolean) and `retrieve_company_info` (boolean). See the [Find Single Email](/api-reference/email-finder/find-single) reference for the full list of available settings.

## FAQ

<AccordionGroup>
  <Accordion title="Do I need a separate API key per endpoint?">
    No. One API key authenticates every endpoint — [Email Finder](/api-reference/email-finder/find-single), [Email Verifier](/api-reference/email-verifier/verify-single), and [Phone Finder](/api-reference/phone/find-single). Pass the key in the `x-api-key` header on every request.
  </Accordion>

  <Accordion title="Does country_code work with company_domain?">
    No. The `country_code` parameter only affects searches that use `company_name`. When you pass a `company_domain`, the domain already identifies the company, so the country code has no effect.
  </Accordion>

  <Accordion title="What happens if I set both a dashboard webhook and a per-request webhook?">
    The per-request `webhook` in the `settings` object takes priority. The dashboard default is only used when a request does not include its own `webhook` URL.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    How to pass your API key in the x-api-key header.
  </Card>

  <Card title="How Webhooks Work" icon="bell" href="/how-webhooks-work">
    Set up webhooks to get notified when a search completes.
  </Card>

  <Card title="Credits & billing" icon="coins" href="/credits-billing">
    See how credits are consumed for each endpoint.
  </Card>

  <Card title="Find an email" icon="envelope" href="/api-reference/email-finder/find-single">
    Run a single email search with custom settings.
  </Card>
</CardGroup>