How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tabs Contracts API

Customer agreements defining dates, terms, obligations, and billing terms.

Tabs Contracts API is one of 8 APIs that Tabs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contracts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.tabsplatform.com.

7 operations 4 paths 3 schemas 3 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.tabsplatform.com
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Tabs Contracts API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — API key passed directly in the Authorization header (Authorization: YOURAPIKEY). Keys are created in the Developers section of the Tabs app and require adminis…

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 3 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Contracts 7

Customer agreements defining dates, terms, obligations, and billing terms.

GET
/contracts
List contracts
listContracts → 200401
POST
/contracts
Create a contract
createContract body → 201401
GET
/contracts/{contractId}
Get a contract
getContract 1 param → 200401404
PUT
/contracts/{contractId}
Update a contract
updateContract 1 param body → 200401
POST
/contracts/{contractId}/files
Upload a contract file
uploadContractFile 1 param body → 201401
GET
/contracts/{contractId}/obligations
List obligations for a contract
listContractObligations 1 param → 200401
POST
/contracts/{contractId}/obligations
Create an obligation on a contract
createContractObligation 1 param body → 201401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Obligation (7 properties), Contract (6 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Contract
object
6 properties
Obligation
object
A commitment linked to a GL item that generates invoice line items.
7 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabs-platform-contracts-api-openapi.yml Raw ↑

Other APIs Tabs publishes across the network.

Tabs Catalog API
Tabs Customers API
Tabs Invoices API
Tabs Obligations API
Tabs Payments API
Tabs Revenue Recognition API
Tabs Usage Events API
Where this information came from

This is an independent, third-party profile of Tabs Contracts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.