Documentation for
identity, authority
and evidence.
Explore Zoiko iD concepts, architecture and implementation guidance. Understand the difference between identity, delegated authority, continuous trust and evidence, then follow verified technical references when available.
Search by
topic or
question
Search matches published documentation only. Typed queries are not recorded in analytics.
No documentation matches your search
Try a broader term or browse the topic families. Results are never generated, so nothing is invented when a search has no match.
Common
tasks with a
next step
Each path links to a verified destination. Paths with no approved target stay visible as pending.
Understand identity
Who or what an actor is, and how that is established.
Understand delegated authority
How bounded permission to act for another party works.
Explore evidence
How decisions are recorded so they can be reviewed.
Plan enterprise integration
Architecture and integration considerations for organizations.
Find implementation references
Exact interface contracts live in the developer references.
Get support
When documentation does not answer your question.
Six groupings,
each with an
owner
These groupings are editorial proposals. Listing a family does not mean every topic inside it has published content.
Identity & Credentials
Who or what is represented, and how credentials relate to claims.
Delegation & Authorization
What an actor may do, on whose behalf, and for how long.
Continuous Trust & Revocation
How permissions are reassessed as context changes.
Evidence & Auditability
Recording decisions so they can be inspected later.
APIs & Integrations
Pointers to the specialist developer references.
Trust & Operations
Assurance, status and operational routes.
Only
maintained,
owned guides
are featured
A guide is featured only when it has an owner, a verified review date and a current status. Until then, this area stays empty rather than filled with placeholders.
No featured guides yet
When guides pass review, they appear here with their title, summary, owner and last reviewed date.
Every article
follows the
same order
A consistent order shows what is a prerequisite, what is a step, and what is context.
Examples
are labelled,
and code is
gated
Code samples come only from the approved engineering registry. No working endpoint is shown on this page.
// Illustrative example - not a verified implementation contract status: "sample-only", source: "engineering-registry: pending" runnable: false
Copy controls
Copy works only with clipboard permission. Unsupported languages show a plain-text version.
Source unavailable
If a sample cannot be verified, the example is withdrawn and the surrounding text stays.
Jump lists
and anchors
Desktop shows a sticky table of contents only for long articles. Mobile uses a collapsible jump list.
Desktop table of contents
Mobile jump list
Collapsed by default. Expanding it moves focus to the list. Anchors keep their scroll offset.
Every page
shows its
state
Unverified dates block publication. An article without an owner and a verified review date cannot be published as current.
Contracts
live in their
own
destinations
Documentation explains concepts and points to the owner of each contract. It never duplicates a contract.
API Reference
Exact endpoints and schemas, owned by Developers.
Quickstarts
Step-by-step guidance for a first integration.
Webhooks & Events
Event contracts, owned by Integrate & Operate.
SDKs, Integrations, Sandbox, Changelog
Only verified availability is shown.
Each question
has one
destination
Case details are never passed automatically between routes.
Every destination above is marked pending until its route is verified.
Who can
read, edit
and publish
Every article
record has
the same
fields
Categories
only, never
typed text
Recorded
- topic_entry and article_opened, by category
- documentation_search_submitted, category only
- specialist_handoff_clicked and help_route_clicked
Never recorded
- Raw search query text
- Passwords, access tokens or credential identifiers
- Identity claims or free-text security detail
WCAG 2.2
AA, at every
width
- Desktop: restrained article column with an optional table of contents.
- Tablet and mobile: one column, collapsible topics, no horizontal clipping.
- 200% and 400% zoom: every function still works.
- Visible focus, logical order, live-region announcements, reduced motion honoured.
Source-
backed
metadata
only
Acceptance
and owners
This page is an approval candidate and is not locked.
Release rule. The interface may be production-ready while a specific guide or specialist destination stays gated. Publish only verified content and truthful unavailable states.
Frequently asked questions
Find answers to common questions about Zoiko ID
Browse, or get help with
your use case.
Start with the topic that fits your question. If documentation does not answer it,
Help & Support takes account and product questions.
SUPPORT & ACCESSIBILITY / DOCUMENTATION
Documentation for identity, authority and evidence.
Explore Zoiko ID concepts, architecture and implementation guidance. Understand the difference between identity, delegated authority, continuous trust and evidence, then follow verified technical references when available.
The developer documentation link appears only once its destination is approved.
01 · SEARCH AND FINDER
Search by topic or question
Search matches published documentation only. Typed queries are not recorded in analytics.
No documentation matches your search
Try a broader term or browse the topic families. Results are never generated, so nothing is invented when a search has no match.
02 · START HERE
Common tasks with a next step
Each path links to a verified destination. Paths with no approved target stay visible as pending.
Understand identity
Who or what an actor is, and how that is established.
Understand delegated authority
How bounded permission to act for another party works.
Explore evidence
How decisions are recorded so they can be reviewed.
Plan enterprise integration
Architecture and integration considerations for organizations.
Find implementation references
Exact interface contracts live in the developer references.
Get support
When documentation does not answer your question.
03 · FAMILIES
Six groupings, each with an owner
These groupings are editorial proposals. Listing a family does not mean every topic inside it has published content.
Identity & Credentials
Who or what is represented, and how credentials relate to claims.
Owner: Product
Delegation & Authorization
What an actor may do, on whose behalf, and for how long.
Owner: Product
Continuous Trust & Revocation
How permissions are reassessed as context changes.
Owner: Product and Engineering
Evidence & Auditability
Recording decisions so they can be inspected later.
Owner: Product and Privacy
APIs & Integrations
Pointers to the specialist developer references.
Owner: Developer Experience
Trust & Operations
Assurance, status and operational routes.
Owner: Trust and Operations
04 · FEATURED GUIDES
Only maintained, owned guides are featured
A guide is featured only when it has an owner, a verified review date and a current status. Until then, this area stays empty rather than filled with placeholders.
No featured guides yet
When guides pass review, they appear here with their title, summary, owner and last reviewed date.
05 · ARTICLE STRUCTURE
Every article follows the same order
A consistent order shows what is a prerequisite, what is a step, and what is context.
06 · ARTICLE BODY AND EXAMPLES
Examples are labelled, and code is gated
Code samples come only from the approved engineering registry. No working endpoint is shown on this page.
// Illustrative example - not a verified implementation contract status: "sample-only" source: "engineering-registry: pending" runnable: false
Copy controls
Copy works only with clipboard permission. Unsupported languages show a plain-text version.
Source unavailable
If a sample cannot be verified, the example is withdrawn and the surrounding text stays.
07 · IN-PAGE NAVIGATION
Jump lists and anchors
Desktop shows a sticky table of contents only for long articles. Mobile uses a collapsible jump list.
Desktop table of contents
Mobile jump list
Collapsed by default. Expanding it moves focus to the list. Anchors keep their scroll offset.
08 · CONTENT TRUST AND LIFECYCLE
Every page shows its state
Unverified dates block publication.
An article without an owner and a verified review date cannot be published as current.
09 · DEVELOPER HANDOFFS
Contracts live in their own destinations
Documentation explains concepts and points to the owner of each contract. It never duplicates a contract.
API Reference
Exact endpoints and schemas, owned by Developers.
Quickstarts
Step-by-step guidance for a first integration.
Webhooks & Events
Event contracts, owned by Integrate & Operate.
SDKs, Integrations, Sandbox,
Changelog
Only verified availability is shown.
10 · SECURITY, PRIVACY AND OPERATIONS
Each question has one destination
Case details are never passed automatically between routes.
maintenance
help
Every destination above is marked pending until its route is verified.
11 · PERMISSIONS
Who can read, edit and publish
12 · CONTENT DATA CONTRACT
Every article record has the same fields
13 · ANALYTICS
Categories only, never typed text
Recorded
- topic_entry and article_opened, by category
- documentation_search_submitted, category only
- specialist_handoff_clicked and help_route_clicked
Never recorded
- Raw search query text
- Passwords, access tokens or credential identifiers
- Identity claims or free-text security detail
14 · RESPONSIVE AND ACCESSIBILITY
WCAG 2.2 AA, at every width
- Desktop: restrained article column with an optional table of contents.
- Tablet and mobile: one column, collapsible topics, no horizontal clipping .
- 200% and 400% zoom: every function still works.
- Visible focus, logical order, live-region announcements, reduced motion honoured.
15 · SEO AND ANSWER-FIRST
Source-backed metadata only
RELEASE GATE
Acceptance and owners
This page is an approval candidate and is not locked.
Release rule. The interface may be production-ready while a specific guide or specialist destination stays gated. Publish only verified content and truthful unavailable states.
16 · QUESTIONS
Answers to the first questions
What is documentation on Zoiko iD?
Explanatory and implementation guidance, labelled by type. Each page states whether it is conceptual or a verified technical reference.
Where are the API references?
In the API Reference, owned by Developers. This page points to it and does not restate its contracts.
How does authorization differ from authentication?
Authentication establishes who is signing in. Authorization decides what that party may do.
How do I get support?
Use Help & Support for account and product questions. Security and privacy matters go to their own routes.
NEXT STEP
Browse, or get help with your use case.
Start with the topic that fits your question. If documentation does not answer it, Help & Support takes account and product questions.
