OpenAPI JSON
Machine-readable contract snapshot.
Developer Console for OAuth2, Subjects, Processes, Identification Groups and transaction tracing; deterministic offline fixtures send no production requests.
Every operation is tied to API version, auth, request/response fixture, source status and evidence/trace context.
/
Versioned local OpenAPI assets and keeps sandbox/mock separate from production.
Machine-readable contract snapshot.
Portable specification for tooling.
Public · Partner · Administrative · Requires approval
Standardize the published endpoint specification structure as: Purpose → Authentication → Schema → Request → Response → Result → Evidence → Source.
| Layer | Requirement |
|---|---|
| Auth | OAuth2 client credentials / Bearer per contract |
| Headers | M/O/RC/A + format + example |
| Request | Schema + enum + sanitised example |
| Response | HTTP + response schema + business result |
| Evidence | Process/transaction/billcode references when defined |
| Source | API version + source section + publication status |
No offline action may automatically call a live environment.
Every operation must have enough information before it can be treated as “Documentation complete”.
Method, path, auth, headers and source version.
Request/response field models with type, enum and mandatory/optional M/O/RC/A.
Sanitised request/response plus offline simulation with deterministic results.
Result codes, evidence references, related process/SDK/device context.