Skip to main content
The Syrto API is a bespoke, per-client offering. Syrto provisions a dedicated API for an organization on request, for specific use cases - it is not a self-serve public product. This section applies only if Syrto has set up an API for your organization. To request one, contact sales.
The Syrto API is a REST layer over Syrto’s financial database. Each organization gets its own API, tailored to its use case: the available endpoints, their pricing, and their response shapes are configured per client. Your own OpenAPI schema - fetched with your API key - is the authoritative reference for exactly what your API exposes. The pages in this section document the conventions shared by every Syrto API (authentication, the response envelope, errors, rate limits, versioning) and walk through example endpoints that illustrate the kind of resources Syrto can provision.

​
Base URL

All endpoints are served over HTTPS. Your API key determines which organization’s API you reach and which endpoints you can call - see Authentication.

​
Your endpoints

Because endpoints are configured per client, there is no single fixed list. The endpoints provisioned for your organization are described in your own schema, which you can fetch and preview with your API key. The example endpoints below show the kind of resources Syrto commonly exposes - your API may include some, all, or bespoke variants of them:

Company financials

A financial snapshot for a single company by tax ID.

Credit report

A full credit report - identity, risk indicators, ownership, officers, and recent financials.

Company profile

A company profile that adapts to size: peers for large companies, a deeper risk view for smaller ones.

Company report

A comprehensive report with multi-year financial statements, branches, and beneficial owners.

​
Response envelope

Every successful response is a JSON object with two top-level fields: data and meta.
​
object
The endpoint’s resource. On a 200 response data is always present and non-null - a request that matches no company returns 404 not_found instead, never a 200 with an empty body.
​
object
Metadata about the call:
  • requestId - a unique id for the request (req_ followed by a UUID). Quote it in support requests.
  • endpoint - the endpoint slug that served the request.
  • usage - the usage measure recorded for the call, as { quantity, unit }.

​
Response headers

Alongside the JSON body, responses carry a few headers:

​
Quickstart

Once Syrto has provisioned your API and you have a key, call one of your endpoints (the exact path depends on your schema):
A successful call returns 200 with a { data, meta } body. If the key is missing or invalid you get 401; if no company matches, 404. See Errors for the full list.

​
Support