> For the complete documentation index, see [llms.txt](https://developer.flash-payments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.flash-payments.com/compliance/adverse-media-search/ams-statuses.md).

# AMS statuses

Adverse media search request statuses

1. You submit a search. The request is created and queued.\
   `INITIALISED`
2. The background scan starts — web sources are fetched and analysed.\
   `INITIALISED` → `PENDING`
3. `PENDING` →
   * `COMPLETED` — the scan finished successfully. Results are available in the `results` field. ***Final status.***
   * `FAILED` — the scan could not be completed due to an error. The request is not billable. ***Final status.***

#### Most common status transitions

**Happy path**

`INITIALISED` → `PENDING` → `COMPLETED`

**Unhappy path**

`INITIALISED` → `PENDING` → `FAILED`

{% hint style="info" %}
A `FAILED` request is not billed. You may submit the same search again — a new request will be created and processed.
{% endhint %}

#### Results

Once a request reaches `COMPLETED`, the `results` field is populated with an array of `AmsWebSearchResult` objects. Each result represents a single web article found during the scan and includes:

| Field                | Description                                                                   |
| -------------------- | ----------------------------------------------------------------------------- |
| `title`              | Title of the web page                                                         |
| `snippet`            | Web search snippet                                                            |
| `link`               | URL of the article                                                            |
| `adversityScore`     | Overall adversity score, 0–100. Higher = more adverse content found           |
| `personSimilarity`   | Similarity between the search subject and the person in the article, 0–100    |
| `role`               | Role of the subject in the article — e.g. `perpetrator`, `victim`, `other`    |
| `roleDetails`        | Further detail on the role or alleged involvement                             |
| `summary`            | One-sentence summary of the article                                           |
| `extractedCountry`   | ISO country code extracted from the article, if detected                      |
| `extractedState`     | State or region extracted from the article, if detected                       |
| `locationMismatch`   | `true` if the article's detected location does not match the supplied country |
| `paywall`            | `true` if the article is behind a paywall and could not be fully analysed     |
| `exactFullNameMatch` | `true` if the article contains an exact match of the full name                |
| `dob`                | Date of birth extracted from the article, if detected                         |
| `ageInArticle`       | Age of the person extracted from the article, if detected                     |
| `articlePublishDate` | Publication date of the article, if detected                                  |
| `lookup`             | Keywords found in the article and their occurrence counts                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.flash-payments.com/compliance/adverse-media-search/ams-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.