The production Swagger is at [api.ripscloud.com/swagger](https://api.ripscloud.com/swagger). Its original OpenAPI 3.1 document is at [api.ripscloud.com/doc](https://api.ripscloud.com/doc).

[Download the integration OpenAPI JSON](/openapi.json) · [View snapshot metadata](/contract.json)

## Two views of one production source

This site publishes a curated integration contract at `/openapi.json`. It preserves operation IDs, request and response schemas, required fields, examples, and error codes from production.

The integration view includes operations that accept a PAT and the basic API health check. It excludes interactive administration, PAT management, and upstream diagnostics. Use the portal for those tasks. The original production spec remains available at `/doc` on the API host.

The JSON contract retains its original Spanish descriptions and exact field names. This site explains the integration flows in English. Do not translate JSON property names or enum values in requests.

## Verify provenance

The [metadata file](/contract.json) records the source URL, retrieval timestamp, API version, number of published operations, and SHA-256 digests of the source and curated contract.

A successful documentation build checks the source checksum, resolves schema references, and validates all published request examples. It does not perform production writes. Examples use synthetic values; schema validity is not clinical correctness or ministry acceptance.

## Update your client

1. Save the contract version and checksum used by your integration.
2. Compare a new spec with that snapshot before regenerating.
3. Review required fields, enums, response types, and operation IDs.
4. Test the complete workflow against the target environment's own contract.
5. Deploy the client only after state and error handling checks pass.

The docs build refreshes its source from the published production API. It fails if the source cannot be retrieved or if its server is not production. Offline builds use the committed snapshot explicitly; they do not silently use sandbox.

## Supported surface

These docs describe HTTP requests and responses. They do not advertise an official SDK, public upstream proxy, webhook, MCP service or throughput SLA. [Subscription terms](/guides/subscription/) are published separately from the API contract.