Skip to content
Other

contract-p.fit

Contract.fit sandbox and mock API

This OpenAPI describes the API exposed by the contract.fit backend. ## Security ### Authentication All endpoints are protected: you need to make authenticated calls. There are 3 authentication mechanisms: - HTTP Basic (Username + Password) - JWT Token - API-Key By default you should have an account allowing you to bootstrap your tenant and create users and roles, using Basic Auth or after creating Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
135
Collections
-
Event types
-
Start this simulation
example request
curl https://your-contract-p-fit.slurry.io/api/about/release_notes \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 135.

  • GET/about/release_notes
  • GET/about/version
  • POST/auth
  • GET/auth/api-key
  • POST/auth/api-key
  • GET/auth/api-key/inbox/{inbox_id}
  • POST/auth/api-key/inbox/{inbox_id}
  • GET/auth/api-key/{key}
  • PATCH/auth/api-key/{key}
  • DELETE/auth/api-key/{key}
  • POST/auth/ephemeral
  • POST/auth/get_JWT