Contract use
Generate clients, validate request/response shape and review breaking changes.
DEVELOPER
Treat the packaged OpenAPI contract as a build-time interface description while keeping environment URLs, credentials and deployment policy outside the specification.
Generate clients, validate request/response shape and review breaking changes.
Sandbox and production endpoints/credentials are not hard-coded into generated clients.
A breaking schema or behavior change requires an explicit version/migration path.
OAuth/mTLS requirements are documented but secrets and private keys never belong in the contract bundle.
The OpenAPI file describes a contract, not live availability. Endpoint, credential, policy and version compatibility are confirmed separately per environment.