---
title: "Verify the sending domain"
description: "Check the domain of the merchant's own sending address (sender_address) now, with Amazon SES and with a DNS lookup of each record SES expects, and return where it stands: the same sender_domain object GET /account/sendin"
url: https://docs.stoqapp.com/v2-reference/account-sending/verify-the-sending-domain/
api: "API v2 reference"
method: POST
path: "/account/sending/verify_domain"
---

# Verify the sending domain

`POST https://app.stoqapp.com/api/v2/external/account/sending/verify_domain`

Check the domain of the merchant's own sending address (sender_address) now, with Amazon SES and with a DNS lookup of each record SES expects, and return where it stands: the same sender_domain object [`GET /account/sending`](https://docs.stoqapp.com/v2-reference/account-sending/get-sending-settings/) returns, checked fresh.

**Note:** status: verified | pending (SES has not seen the records yet, or is re-checking) | failed (SES gave up looking) | not_started (SES has no check for the domain) | not_set (use_custom_email_address is off, or the address is STOQ's or on a free mail domain) | error (SES did not answer). records lists each CNAME to add: host, expected value, the value DNS holds now (found) and status ok | missing | wrong_value | lookup_failed. next_step: add_records | fix_records | wait_for_ses | restart_verification | none. in_use is true when the domain is verified and the plan allows a custom sender. This call registers the domain with SES the first time (not_started) and restarts a failed check once the records are right, then answers with the status after that. The answer is saved, so custom_address_status follows it at once. DNS changes can take up to 72 hours to reach SES.

## Headers

- `Idempotency-Key` (string): A fresh unique key for every write (a new UUID, say); reuse it only to retry that write. Keys are remembered for 1 hour: the same key and the same request within that hour returns the first result, with `Idempotent-Replayed: true`, without running again; the same key with a different method, path or body is refused (422 `idempotency_key_reused`); a retry while the first is still running gets 409 `idempotency_key_in_progress`. Keys are per store. Server errors and rate limits are not kept, so their retry runs.

## Returns

- `domain` (string): e.g. `stridesupply.com`
- `dkim_verified` (boolean): e.g. `false`
- `dkim_enabled` (boolean): e.g. `false`
- `dns_records` (array of objects)
  - `name` (string): e.g. `exampletoken1aaaabbbbccccdddd._domainkey.stridesupply.com`
  - `type` (string): e.g. `CNAME`
  - `value` (string): e.g. `exampletoken1aaaabbbbccccdddd.dkim.amazonses.com`

Rate limit: this call costs 2 points ([rate limits](https://docs.stoqapp.com/docs/rate-limits/)).

## Example request

```sh
curl -X POST "https://app.stoqapp.com/api/v2/external/account/sending/verify_domain" \
  -H "X-Auth-Token: $STOQ_API_KEY"
```

## 200

Success: example response shown.

```json
{
  "domain": "stridesupply.com",
  "dkim_verified": false,
  "dkim_enabled": false,
  "dns_records": [
    {
      "name": "exampletoken1aaaabbbbccccdddd._domainkey.stridesupply.com",
      "type": "CNAME",
      "value": "exampletoken1aaaabbbbccccdddd.dkim.amazonses.com"
    },
    {
      "name": "exampletoken2eeeeffffgggghhhh._domainkey.stridesupply.com",
      "type": "CNAME",
      "value": "exampletoken2eeeeffffgggghhhh.dkim.amazonses.com"
    }
  ]
}
```

## 401

Missing or invalid `X-Auth-Token`.

```json
{
  "errors": [
    "Invalid API key"
  ],
  "code": "auth_invalid",
  "details": [
    {
      "code": "auth_invalid",
      "message": "Invalid API key",
      "path": null,
      "value": null,
      "expected": null
    }
  ]
}
```

## 409

An earlier request with the same Idempotency-Key is still running. Wait, then resend the same request with the same key.

```json
{
  "errors": [
    "A request with this Idempotency-Key is still running"
  ],
  "code": "idempotency_key_in_progress",
  "details": [
    {
      "code": "idempotency_key_in_progress",
      "message": "A request with this Idempotency-Key is still running",
      "path": null,
      "value": null,
      "expected": null
    }
  ]
}
```

## 422

The request failed validation.

```json
{
  "errors": [
    "name is required"
  ],
  "code": "validation_failed",
  "details": [
    {
      "code": "validation_failed",
      "message": "name is required",
      "path": null,
      "value": null,
      "expected": null
    }
  ]
}
```

## 429

Rate limited: cost-weighted per token (read 1, write 2; 360 points / 60s). Check `Retry-After`.

```json
{
  "errors": [
    "Rate limit exceeded"
  ],
  "code": "rate_limited",
  "details": [
    {
      "code": "rate_limited",
      "message": "Rate limit exceeded",
      "path": null,
      "value": null,
      "expected": null
    }
  ]
}
```

