> 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/get-started/concepts/allowed-networks.md). # Allowed networks Allowed networks is the list of mobile networks a project is authorised to use. It applies per project — different projects in the same workspace can have different lists. ## Why it exists A project's allowed networks reflect: * The carriers your commercial agreement covers. * The carriers that have approved your use case. * The carriers IDlayr has integrated and validated for the products you're calling. Restricting a project to its allowed networks prevents traffic from being sent to a carrier that hasn't approved the use case, or to a carrier where the product isn't supported. ## What you see In API responses where a network is identified (e.g. on Secure SNA results), the network identifier is one your project is allowed to use. Networks outside your project's allowed list are not surfaced — IDlayr does not expose its full carrier routing topology to customer-facing APIs. ## What happens when the target number is out of scope If you submit a request for a phone number whose carrier is not in your project's allowed networks, the response indicates the situation. Depending on the product: * The request fails with `mno_not_supported` (400). * The Eligibility check returns the product as unavailable for that number. Route the verification to an alternative path in either case. Use Eligibility as a pre-check if you want to know in advance. ## Adding networks to a project This is a commercial-and-approval workflow, not a self-service config. Contact your IDlayr account team to extend a project's allowed networks. Each new carrier may require carrier-side approval before going live. --- # 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/get-started/concepts/allowed-networks.md?ask=&goal= ``` `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.