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

# Enrichment Request Statuses, Email Fields, and Freshness

> Learn what accepted, in-progress, completed, not_found, and failed mean for Dmand AI requests, how replays work, and how Dmand keeps emails fresh.

Every NPI you submit to the Dmand AI API becomes a request with its own `status`. This page explains each status, the per-result email fields, the `replayed` flag, and how Dmand makes sure returned emails are current.

## Request statuses

| Status        | Meaning                                                                                                    | Charged?                      |
| ------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------- |
| `accepted`    | The request was received and is queued for processing.                                                     | Credits are held              |
| `in-progress` | Dmand is still resolving this NPI. Check again later or wait for a webhook.                                | Credits are held              |
| `completed`   | An email was found. The result includes `email`, `email_type`, `email_status`, and `email_last_validated`. | Yes                           |
| `not_found`   | No email was found for this NPI. Email fields are null.                                                    | No, held credits are refunded |
| `failed`      | The request timed out or could not be completed. Credits are refunded.                                     | No                            |

Most NPIs resolve quickly from Dmand's existing data. NPIs that need live enrichment can take longer, typically up to about `15` minutes. Requests that time out become `failed` and the held credits are refunded.

## Email fields in results

When a request is `completed`, the result item includes these fields:

| Field                  | Type           | Description                                                                                         |
| ---------------------- | -------------- | --------------------------------------------------------------------------------------------------- |
| `email`                | string \| null | The enriched email address.                                                                         |
| `email_type`           | string \| null | Which type was returned, for example `professional` or `personal`.                                  |
| `email_status`         | string \| null | The verification status of the returned email: `valid` when an email is returned, otherwise `null`. |
| `email_last_validated` | string \| null | ISO 8601 timestamp of when the email was last validated.                                            |

For `not_found` or `failed` requests, these fields are null.

## The `replayed` flag

`replayed: true` means your organization already received a result for this NPI within the last `30` days, and the API returned that result again at no charge. See [Credits](/general/credits).

## Email freshness

Dmand only returns emails it considers current:

* Emails must be marked valid and validated within the last **`30` days**.
* Emails that have not been validated are re-verified before they are returned.
* When several valid emails exist, Dmand returns the most recently validated one for the email type you requested.