What a Secure Issuer API Must Guarantee Before It Adds Convenience
Authentication is only the first layer. The harder promise is that every read and write stays inside the calling issuer's boundary.
An API can be correctly authenticated and still be dangerously broad. For a platform serving multiple issuers, every endpoint must answer a second question after checking the key: does this specific resource belong to the caller's issuer?
Scope belongs in the query
CigyID's issuer API applies the issuer identifier directly to resource operations. A supplied profile, tag, reservation or asset identifier is never treated as sufficient proof of access on its own.
Enable only what the integration needs
- System administrators enable individual API capabilities per issuer.
- API keys are stored as hashes rather than recoverable plaintext.
- Asset endpoints remain unavailable when the asset module is disabled.
- Operational actions are recorded for traceability.
Design for failure as well as success
A dependable integration returns clear authorization and module-state errors, avoids leaking whether another issuer's resource exists and makes retries safe where external systems may repeat requests.
“The strongest multi-tenant API is not the one with the most endpoints. It is the one whose boundaries remain true on every endpoint.”
