Introduction

The Trimline API gives you programmatic access to the same data and actions as the Trimline dashboard: the vendors we’ve found in your books, their contracts and notice deadlines, upcoming renewals, live negotiations, the drafts waiting for your approval, and the savings we’ve confirmed.

Teams use it to pipe renewal dates into their finance calendar, approve drafts from Slack or an internal tool, sync savings into their FP&A model, and get a webhook the moment a vendor replies.

Base URL

https://api.trimline.tech/v1

The API is organized around REST. It accepts JSON request bodies, returns JSON responses, and uses standard HTTP status codes and verbs. Every request is made over HTTPS. Plain HTTP requests are refused rather than redirected.

Start here

How the objects fit together

Every recurring supplier we find becomes a vendor. Each vendor has one or more contracts describing the term, notice period and price. As a contract approaches its end date, Trimline opens a renewal. If you choose to negotiate, the renewal gets a negotiation, which produces drafts for you to approve and, once terms are agreed, a savings record.

vendor ─┬─ contract ── renewal ── negotiation ─┬─ draft (×n)
        │                                      └─ offer (×n)
        └─ contract ── renewal ── savings

Conventions

• IDs are strings with a type prefix, such as ven_, ctr_ or ren_. Treat them as opaque, and don’t parse them.
• Money is always an object with an integer amount in the currency’s minor unit (cents for USD) and an ISO 4217 currency code.
• Timestamps are ISO 8601 strings in UTC. Fields that are dates only, like renews_on, use YYYY-MM-DD.
• Nullable fields are always present in responses with a value of null, never omitted.

Beta access

During the private beta, API keys are issued to beta customers on request. If you’re on the waitlist and want to build against the API, tick API access on the signup form and we’ll send you sandbox keys first.