> For the complete documentation index, see [llms.txt](https://verify-doc.tiller-verify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verify-doc.tiller-verify.com/verify-api/endpoints/api-reference/references.md).

# References

The References API serves as a central repository for various reference data types for verification. This API provides access to reference information, which are organised into categories. These include: 

* **Country:** A list of countries and their ISO codes. 
* **Document types:** These are the available document types that the customer can select as part of the proof of address upload.
* **Industry:** A list of selectable industries for your account settings.
* **Individual check field status:** Each check can have a set of underlying results. These are represented by the check field results and can have the following status; 'pending', 'accepted', 'rejected'. These underlying results are what determines whether the check has passed or needs to be reviewed.
* **Individual check status:** Each check can have the following status; 'pending', 'review', 'accepted', 'manually\_accepted' or 'manually\_rejected'.
* **Individual status:** The progress of the customer completing their mobile app actions. They can be 'pending' or 'completed'. Only 'completed' individuals will have a customer report. 
* **Mandate status:** The progress of the application. This can be 'new', 'in progress', 'in review', 'completed' or 'rejected'. 
* **Mandate type:** A list of mandate/application types available. The information gathered and checks completed for the individuals associated with the mandate.
* **Title:** The acceptable titles for submitting the customers details as part of the create application process.

{% openapi src="/files/d3yB4cFl16j0xlR4QP71" path="/ext/references" method="get" %}
[TillerTechnologies-verify-api-v1-oas3.json](https://content.gitbook.com/content/0zS5rWXn6QhdPJuSHu9k/blobs/QIqANJoV2sVgHqFFWsfb/TillerTechnologies-verify-api-v1-oas3.json)
{% endopenapi %}


---

# 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://verify-doc.tiller-verify.com/verify-api/endpoints/api-reference/references.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.