The Ramp Accounts API exposes general ledger account resources used to map Ramp activity to accounting systems. Base URL https://api.ramp.com/developer/v1.
Its catalog entry carries eleven distinct artifact types: OpenAPI, Documentation, Arazzo, AsyncAPI, GraphQL, JSONSchema, JSONStructure, JSONLD, SpectralRules, Examples, and APIs.json.
That Arazzo entry is the one worth stopping on.
Why Arazzo belongs here
Arazzo describes API workflows — the ordered sequence of calls that accomplishes a job, with the outputs of one step feeding the inputs of the next. Most APIs do not need it. This one does.
Mapping corporate card spend into a general ledger is not a single call. It is: fetch the chart of accounts, resolve the department and location dimensions, match a transaction to a GL code, handle the ones that do not match, then post. Getting that order wrong produces a reconciliation mess in someone’s accounting system, which is the specific failure mode finance teams cannot tolerate.
A workflow definition turns that sequence from tribal knowledge in an integration guide into something executable. As this week’s Mistral piece noted about onboarding, and the Wise 3DS piece about sandboxes — the artifacts that matter are the ones addressing where integrations actually break.
Spectral rules and the governance signal
The SpectralRules property means Ramp ships the linting rules its own definitions are governed against. That is a small artifact with a large implication: the API is not just described, it is described consistently, and there is machinery enforcing it.
For a consumer, published governance rules are a predictability guarantee. The naming conventions, error shapes, and pagination patterns you learn on the Accounts API will hold on the next Ramp API you integrate, because a linter enforces them.
The semantic stack
JSONSchema, JSONStructure, and JSONLD together are the full semantic ladder: structure, shape, and meaning. For accounting data that ladder is unusually load-bearing — a field called account_id could be Ramp’s internal identifier or the customer’s GL code, and getting that wrong silently corrupts a ledger. A JSON-LD context makes the distinction explicit rather than conventional.
Takeaway
Eleven artifact types on an API that maps card transactions to ledger accounts — including a workflow definition for the multi-step sequence and the governance rules the definitions are linted against. Ramp specified the parts of this integration that actually fail, which is the whole point of the exercise.
See it at docs.ramp.com, and the provider entry at apis.io/providers/ramp/.