Contract.fit API

Messaging · Unknown · 30d uptime 7.14%

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 a Token - see */auth* endpoints. If you are missing credentials or permissions, please [contact us](https://contract.fit/contact-us). ### Authorization The security system is RBAC based: users must be granted scoped roles, allowing them to access resources. Each role grants a defined set of permissions, which can be restricted to a given inbox or document - see */roles* endpoints. ## Upload and Processing Below is a short description of common use cases of the API. ### Simple Upload The easiest

Trust signals

Pricing
UNKNOWN
Auth
UNKNOWN
CORS
Yes
Rate limit
Unknown
Health
106ms
Trust score
63 (C)

Usable with review; improve 30 day uptime.

Links

Integration checklist

  • Auth is UNKNOWN
  • CORS enabled — callable directly from browsers.
  • Rate limit: not documented
More messaging APIs