API Reference

Technical contracts you can
inspect, not infer.

Find source-approved interface versions, resources, operations, schemas,
errors and access boundaries when published. Exact production behavior
appears only from governed ZoikoLogia™ technical sources.

Browse API Reference Search documentation

Documentation visibility does not itself confirm API availability, production access, entitlement,
integration support, service level or product coverage.

On this page

Built for the people who have to trust the details.

Different technical roles come here for different jobs. Each gets the same honest answer about what's
published.

The short answer. API Reference is the public presentation layer for approved technical contract information. It shows only the interface facts, versions, schemas, errors and access context that governed sources support, and says so plainly where they don't yet.

Engineers & architects

Check contracts, schemas and limits before
designing anything.

Security reviewers

Find the access boundary and where security
evidence lives.

Procurement & vendor risk

See what's documented and what's not,
without a sales call.

Finance & accounting leads

Understand how a technical decision may
touch your workflows.

Implementation partners

Scope an evaluation against published facts,
not assumptions.

Technical evaluators

Reach a specific item or a safe fallback in
three steps.

Where this comes from, before any syntax appears.

Technical syntax without source provenance isn't production documentation. Every field below is
shown only if a governed source supplies it.

Field	Status
Owning source	Source required
Publication state	Source required
Contract context	Source required
Reviewed / updated	Not published
Artifact reference	Not published
Limitations	Not publicly documented

Provenance rule. If we can't identify the authoritative source and applicable contract context, the item doesn't render as current production truth.

No version selector until a version is actually established.

A selector isn't permission to invent "v1", "latest", "stable", support windows or sunset dates.

No public contract context is currently published

When a version or environment is source-established, a selector will appear here, defaulting only to a context the technical source designates. An unavailable context shows an explicit state and never silently redirects to another contract. Seeing a context is never evidence of your entitlement or environment access.

Not availableContext selector hidden until a source exists

Search and browse the governed inventory.

Search covers approved public labels, descriptions and identifiers only. Please don't paste secrets or
credentials.

Context: none published

Resource tree

The tree mirrors the governed taxonomy. It stays empty rather than implying interfaces that aren't published.

No public reference inventory is currently published

This doesn't mean no interface exists, and it doesn't mean one does. It means nothing is published here yet. For technical questions, use an evaluation route.

Book a Demo Request Pilot

Filters appear only when they cover a complete governed dimension. Order is stable or alphabetical, never "recommended".

What a published reference item will look like.

This is the layout only. Every panel stays empty until its source is approved.

Reference item (layout specimen)

Identity, context and state are shown here when sourced.

Illustrative · not production

Interface identity

The exact approved label, interface kind and contract context. A method, path, protocol or topic appears only when a governed source defines it. We don't normalize anything to REST terminology.

Source requiredNothing is shown until published

How a schema will be presented.

Names, types and requirements come from the source, character for character.

Field	Type	Required	Description
example_field	Source required	Source required	Illustrative row. Real fields, types and descriptions appear only from a governed source.
example_object	Source required	Source required	Nested fields expand in a tree that preserves hierarchy and source order, and indentation is never the only cue.

Names

Never "cleaned up"

Technical identifiers are shown exactly as the source states them.

Requirements

Stated, not inferred

Required, optional, nullable and conditional states appear only with a defined rule.

Values

Synthetic only

Examples never contain real customer, contract, accounting or transaction data.

Documentation and access are separately governed.

Being able to read a contract is never the same as being able to use it.

Topic	What this page does
Authentication	Names a protocol or flow only from an approved technical or security source.
Authorization	Shows a scope or permission model only when governed.
Environments	Distinguishes sandbox, non-production and production only if a source establishes them.
Entitlement	Visibility grants none. A documented interface isn't enabled for every customer.
Credentials	Never shown, in docs, examples, analytics or URLs.

No "Try it" console. We don't show an interactive request executor, credential generator or environment switcher, and not a disabled mock either, because a mock implies a capability that may not exist. For access and security, see Privacy & Security.

An honest gap beats a convincing fake.

Error behavior is documented only where a source documents it.

No error catalog is published yet.

We list exact documented errors, request-tracing concepts and retry behavior
only when they're source-approved. We never infer retryability from a status
family, and we never show stack traces, internal service names or tenant
identifiers.

Traceability

Source-defined only

Correlation and trace field names stay exactly as published.

Unknown behavior

Marked, not guessed

"Not public" or "undocumented" states route you to an approved evaluation path.

Live health

A separate concern

Contract documentation is distinct from any future operational-status page.

Code and payloads, clearly labeled.

Anything not copied from an approved governed source is marked as illustrative. It demonstrates
layout only.

Illustrative example · not production syntax

// Layout specimen only. Not a real interface.
POST https://example.invalid/resource
{
  "example": "source-controlled fields would appear here"
}

The host is a deliberately non-production placeholder. Language tabs and SDK examples appear only when approved examples exist.

Credentials

Never in examples

No tokens, secrets, certificates, tenant IDs or signed material, ever.

Copy

Sanitized content only

Copying announces success or failure, and the text stays selectable.

Downloads

Only if public

No spec or schema download unless an approved public artifact exists.

Two destinations, two different jobs.

API Reference describes the current approved contract. Release Notes owns change history.

Question	Where
What changed?	Release Notes
Is it deprecated?	Only a source-defined lifecycle status, or Release Notes.
What replaces it?	An approved replacement link, if one exists.
Is it breaking?	Never inferred from a version number or schema difference.
How long is it supported?	No support window is implied.

Routed to the team that owns the answer.

Security, compliance and accessibility claims live with their owners. We link, and we don't repeat them.

Governance and oversightOwner: Governance.Governance Procurement processOwner: Procurement Support. Process help, not API facts.Procurement Support A commercial question about access or packagingOwner: Contact Sales. No entitlement is implied.Contact Sales How does this relate to Workflow Mode or Review Mode?Only when a verified technical mapping exists. Otherwise it's a product evaluation question.Kriton™

API questions, answered honestly.

The source-governed public presentation layer for approved technical contracts. It doesn't imply that every product
capability has an API.

Bring the interface questions that matter to your architecture.

Inspect the public technical information available, then use the right product, trust or evaluation route for anything outside it.

Book a Demo Request Pilot Sign In

No API availability, entitlement, integration readiness, SLA, implementation support or production access is implied.