> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/api-reference/discovery-check/introduction.md).

# Introduction

The IDlayr Discovery API resolves the mobile phone number associated with the device making the request directly from the mobile network operator. Unlike Secure SNA — where you supply a number and the platform confirms whether it matches the active SIM — Discovery does not take a phone number as input: while the device sits on a cellular data connection, the network operator attributes the session to a phone number and the platform returns that discovered number along with the resolved network.

The flow is asynchronous and customer-driven:

1. **Create** the Check on your backend, and pass the `check_url` to to your application on the device. No phone number is supplied — the device's network session is what gets resolved. You have 120 seconds to complete the flow from here onwards.
2. **Redirect** the device through the verification URL (`url` on the create response). The network operator is consulted during this hop and a single-use code is returned at the end of the redirect chain.
3. **Submit** the code to complete the Check, which resolves the discovered `phone_number` and `network_id`. The code needs to be passed from the application to your backend, so you can submit it in exchange for the final result.

A webhook to `callback_url` (if you supply one) is fired when the Check reaches a terminal status.

Requests authenticate with an OAuth2 Access Token in the `Authorization` header (`Bearer {access_token}`). Tokens are created using a project's `client_id` and `client_secret`.


---

# 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://docs.idlayr.com/api-reference/discovery-check/introduction.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.