> 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/help-center/readme/support.md). # Support How to reach IDlayr depends on what you're trying to do. The fastest path is usually your **IDlayr account team**, who route requests to the right specialists internally. ## Production incidents If you're seeing impact on a live integration — failed verifications, callback delivery issues, elevated error rates — first check the [Status page](/help-center/readme/status.md) for a known incident. If nothing is reported there, contact your IDlayr account team immediately. Include: * Your project ID and the data-residency region (`eu` / `us`). * A small sample of affected `check_id` values. * The time window when the issue started (in UTC). * The behaviour you're seeing (HTTP status code, error code, callback shape). ## Integration questions For questions about how a product works, how to design an integration, or how to handle an edge case the docs don't cover — contact your IDlayr account team. They'll loop in the appropriate engineer or solutions architect. Before reaching out, it usually helps to check: * The [product page](https://docs.idlayr.com/products) for the product in question. * The [Changelog](https://docs.idlayr.com/changelog) for recent changes that might affect behaviour. * The [Glossary](/help-center/readme/glossary.md) if you're new to carrier terminology. ## Security issues Suspected vulnerabilities or security-related findings should be reported through your IDlayr account team, who will route the report to the security team and coordinate disclosure. Please do not disclose suspected vulnerabilities publicly before coordinating with us. ## Account and access changes To request new projects, additional credentials, SSO setup for the Enterprise Portal, or other access-related changes — contact your IDlayr account team or, for general product enquiries, . ## Compliance and procurement For procurement, vendor reviews, and access to the current attestations (SOC 2, etc.), the IDlayr Trust Center is the canonical source — see [Compliance & Security](/help-center/readme/compliance-and-security.md). For documents or evidence not published on the Trust Center, contact your IDlayr account team. ## Self-serve resources While you wait for a response, the docs themselves cover most integration questions: * [Get started](https://docs.idlayr.com/documentation) — quickstart, your first request, concepts, SDKs. * [Products](https://docs.idlayr.com/products) — full product documentation. * [SDKs](https://docs.idlayr.com/get-started/sdks) — iOS, Android, SDK versioning. * [Changelog](https://docs.idlayr.com/changelog) — what changed and when. --- # 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/help-center/readme/support.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.