Find the right help for
Zoiko iD
Explore guidance for accounts, authentication, credentials, delegated access and integrations. For security, privacy, service status or commercial requests, use the appropriate specialist channel.
Documentation link pending verification. A request form appears only when an approved intake is live.
Suspect account compromise or a security issue?
Use the security reporting path. Never send passwords, recovery codes or private keys in a help request.
Two questions, one primary route
Answer two questions to see the single route that owns your issue. Choosing an answer never asks for credentials and sends nothing.
What do you need help with?
Which describes you best?
Your primary route appears here
One destination, with scope and rationale. The result updates when an answer changes.
Select a category to see its primary and secondary routes to relevant teams.
Start with the topic that matches your question
Each topic states its purpose, the team that owns it and its status. No article counts are shown until the content registry confirms them.
Accounts & Sign-in
Access to your account and sign-in issues.
Authentication & SSO
How sign-in and federation work with your identity provider.
Verification & Credentials
Claims, verification and what credentials do and do not prove.
Organizations & Delegated Authority
Organization admin tasks and delegated access questions.
Machine & AI-agent Identity
Sponsorship, mandates and non-human actors.
APIs & Integrations
Developer guidance, with the documentation for exact interfaces.
Billing or Enterprise Enquiries
Redirects to Talk to Sales. No support promise is made.
Security & Privacy
Specialist routes only. General support does not handle these.
Each kind of issue has one owner
Support does not take over specialist work. A handoff passes your context to the owner and never creates a duplicate request.
Self-service pathways
for builders
Developers start with the documentation. Each pathway opens a verified destination; none is shown until its route is approved.
Developer Overview
Orientation for building on Zoiko iD.
Quickstarts
Step-by-step first integrations.
API Reference
Exact interface contracts.
SDKs
Language packages and their verified status.
A confirmation means the server saved it
Success is shown only after backend persistence. A reference appears only when the backend issued one. Timeouts never claim that a request was created.
Submitting
Repeat submission is disabled while the request is pending.
Confirmed
Shown only after the server saves the request, with a visit reference if one exists.
Timeout or offline
Your text is kept in this session. No "received" message is shown; retry is safe.
Recovery paths for common situations
Each state tells you what happened and what to do next. None invents a result.
No search results
Try a broader term, or browse the topics above. Results never come from a guess.
Search unavailable
The topic list still works. Search returns when the article registry is reachable.
Access not permitted
You see a neutral message and the authorized support route, not account details.
The request form is
shown only when it
is live
No form appears on this page now. The fields below describe the approved intake, so you know what to prepare. Never include passwords, recovery codes or identity documents.
No submit control is shown until an approved backend is live.
Recovering access is separate from proving identity
Password reset and identity proofing have their own steps. We will never ask you to send a password, recovery code or private key, and we cannot promise immediate restoration. If your account is locked and you suspect compromise, use the security route above.
Help is designed to be usable by everyone
This page is built to WCAG 2.2 AA. Privacy questions go to the privacy route, not to general support.
Keyboard
Every control is reachable and has a visible focus state. A skip link is the first step.
Screen readers
Errors are tied to their labels, and results are announced without taking focus away.
Zoom and reflow
Usable at 200% zoom and at 320 CSS px, with no horizontal scrolling for text.
Privacy requests
Route to the privacy specialist. Accessible alternatives are provided where approved.
Frequently asked questions
Find answers to common questions about Zoiko iD
Still need help? Choose the right supported path.
Start with the topic that fits your question. Security and privacy matters always go to their own specialist routes.
Find the right help
for Zoiko iD
Explore guidance for accounts, authentication, credentials, delegated access and integrations. For security, privacy, service status or commercial requests, use the appropriate specialist channel.
Documentation link pending verification. A request form appears only when an approved intake is live.
Search covers approved, public articles only. Queries are limited to 200 characters.
Suspect account compromise or a security issue? Use the security reporting path. Never send passwords, recovery codes or private keys in a help request.
Start with the topic that matches your question
Each topic states its purpose, the team that owns it and its status. No article counts are shown until the content registry confirms them.
Accounts & Sign-in
Access to your account and sign-in issues.
Authentication & SSO
How sign-in and federation work with your identity provider.
Verification & Credentials
Claims, verification and what credentials do and do not prove.
Organizations & Delegated Authority
Organization admin tasks and delegated access questions.
Machine & AI-agent Identity
Sponsorship, mandates and non-human actors.
APIs & Integrations
Developer guidance, with the documentation for exact interfaces.
Billing or Enterprise Enquiries
Redirects to Talk to Sales. No support promise is made.
Security & Privacy
Specialist routes only. General support does not handle these.
Two questions, one primary route
Answer two questions to see the single route that owns your issue. Choosing an answer never asks for credentials and sends nothing.
What do you need help with?
Which describes you best?
Your primary route appears here
One destination, with an optional alternate. The result updates when an answer changes.
If the category is unclear, a general recovery route is shown instead.
Self-service pathways for builders
Developers start with the documentation. Each pathway opens a verified destination; none is shown until its route is approved.
Developer Overview
Orientation for building on Zoiko iD.
Quickstarts
Step-by-step first integrations.
API Reference
Exact interface contracts.
SDKs
Language packages and their verified status.
Each kind of issue has one owner
Support does not take over specialist work. A handoff passes your context to the owner and never creates a duplicate request.
The request form is shown only when it is live
No form appears on this page now. The fields below describe the approved intake, so you know what to prepare. Never include passwords, recovery codes or identity documents.
No submit control is shown until an approved backend is live.
A confirmation means the server saved it
Success is shown only after backend persistence. A reference appears only when the backend issued one. Timeouts never claim that a request was created.
Submitting
Repeat submission is disabled while the request is pending.
Confirmed
Shown only after the server marks the request, with a real reference if one exists.
Timed out or offline
Your text is kept in this session. No "received" message is shown; retry is safe.
Recovery paths for common situations
Each state tells you what happened and what to do next. None invents a result.
No search results
Try a broader term or browse the topics above. Results never come from a guess.
Search unavailable
The topics list still works. Search returns when the article registry is reachable.
Access not permitted
You see a neutral message and the authorized support route, not account details.
Recovering access is separate from proving identity
Password reset and identity proofing have their own steps. We will never ask you to send a password, recovery code or private key, and we cannot promise immediate restoration. If your account is locked and you suspect compromise, use the security route above.
Help is designed to be usable by everyone
This page is built to WCAG 2.2 AA. Privacy questions go to the privacy route, not to general support.
Keyboard
Every control is reachable and has a visible focus state. A skip link is the first stop.
Screen readers
Errors are tied to their labels, and results are announced without taking focus away.
Zoom and reflow
Usable at 200% zoom and at 320 CSS px, with no horizontal scrolling for text.
Privacy requests
Routes to the privacy specialist. Accessible alternatives are provided where approved.
Answers to the questions people ask first
Where do I find integration documentation?
Start with the Developer Overview and Quickstarts. The API Reference holds exact interface contracts.
How should I report a vulnerability?
Use Responsible Disclosure. Do not send exploit material through the help form.
Where can I check service availability?
On Availability / Status, which shows confirmed incidents and maintenance. This page does not predict outages.
Where do I send privacy-related requests?
To the privacy route, which is separate from general support. Sending a help request does not fulfill a rights request.
How do I get help with identity and delegated authority?
Read the topics above first. For complex organization cases, the enterprise route is the right owner.
Still need help? Choose the right supported path.
Start with the topic that fits your question. Security and privacy matters always go to their own specialist routes.
