Contract coverage

Open the Scalar API reference to browse methods, paths, schemas and examples in the selected contract. The renderer and assets are served by this site.

Core source snapshot

The current snapshot has 771 paths, 1,142 operations and 1,546 named schemas. It is copied byte-for-byte from the generated core artifact. The source contract passes structural validation. Whole-core semantic and runtime conformance require further evidence.

There are 119 untyped-response dispositions in the internal source review. Ninety bodies were recovered from source, twenty handlers have no success entity, seven responses bind to the scoped local profile and two framework responses remain unresolved. A missing raw response schema requires the endpoint’s reviewed supplement before client generation.

Download the core JSON or inspect the snapshot hashes and counts.

Local banking profile

The separately selected local profile contains 33 paths, 34 operations and 45 schemas for local NGN/NPS Transfer and customer-consented read-only account access. It carries selected LOCAL_SYNTHETIC journey and focused-unit evidence. Each operation still needs the stated institution, grant and environment. It supplies no live NIBSS certification or whole-core qualification.

Download the local profile. These operations overlap the core snapshot and their counts should be read separately.

Add-ons and target contracts

The Product Bible defines the global product target, including separately licensed add-ons and institution-built experiences. Proposed extension contracts, agent tools and canonical events are design artifacts. They are introduced through the add-on, partner and agent guides. The API explorer displays only the two labelled existing source/profile documents.

Errors and uncertain outcomes

Check HTTP status, media type and the exact endpoint contract. Older shared core errors can use numeric business codes, local Transfer uses string codes, and several legacy handlers return their own JSON representation. HTTP 200 can contain a rejected legacy licence result.

A timeout after a financial submission requires status enquiry and reconciliation with the original instruction identity. Repeating the workflow under a new identity can duplicate money movement. Keep the record pending with a named owner until authoritative evidence resolves it.