Docs

Connect your data to Actuals.

Everything your data team needs: seven ways to get data in, a REST API for real-time transactions, and the security behind it. The full documentation lives at docs.actuals.io.

POST /v1/raw_transactions
curl --location 'https://api.actuals.io/v1/raw_transactions' \
  --header 'Content-Type: application/json' \
  --header 'token: test_••••••' \
  --data '{
    "type": "order",
    "external_id": "123456",
    "timestamp": "2025-01-01T00:00:00Z",
    "object": { "my_custom_key": "my_custom_value" }
  }'
NEW One order received. Sending the same external_id again is ignored.

Data integration

Seven ways to get data in. Pick where your data lives.

  1. 01
    Application connectors

    Standard connectors for payment providers, ERPs, billing and banks, built by Actuals. You share credentials, Actuals collects the data. The most automated option.

    Preferred
  2. 02
    Database connectors

    Give Actuals read access to Snowflake or BigQuery and it runs the queries itself. Efficient once it is set up.

    Preferred
  3. 03
    Actuals SFTP server

    Your system exports files on a schedule and uploads them to a secure server run by Actuals. Reliable when the export can be automated.

    Preferred
  4. 04
    Raw transactions API

    Send each transaction the moment it is final, straight from your website or app. Actuals then has an independent record to match everything else against.

    Use case
  5. 05
    External SFTP server

    Actuals collects files from a server a third party runs. For when that party has no other way to deliver data.

    Use case
  6. 06
    Upload in the platform

    Upload a CSV file with a header row yourself. Good for sources that change rarely.

    Use case
  7. 07
    Email connector

    Send CSV attachments to an address of your Actuals environment and they are imported. The last option, when nothing else is possible.

    Use case

Not sure which fits? A data engineer from Actuals sits down with yours to agree how each source is synchronised.

Raw transactions API

Send it once. Then check that every transaction arrived.

POST https://api.actuals.io/v1/raw_transactions
header token: prod_••••••

{
  "type": "order",
  "external_id": "ORD-123",
  "timestamp": "2025-01-01T00:00:10Z",
  "object": { ... }
}
  • Test first, then live. Keys starting with test_ never touch production data. Swap in a prod_ key when you go live.
  • One transaction per call. The API has no bulk endpoint. Send asynchronously, so your checkout never waits for it.
  • Duplicates can’t slip in. The same external_id with the same content is ignored. With different content it is flagged as an error.
Full API reference

Access and security

Your IT team will ask. Here are the answers.

  • SOC 2 Type II

    Security, availability and confidentiality controls, audited over time.

  • Separate environments

    Every company gets its own environment, with its own data, access rights and users.

  • SSO with Okta

    SAML single sign-on, and SCIM to create and remove users automatically.

  • Fixed IP addresses

    If your SFTP server uses an allowlist, Actuals connects from published addresses.

More on security and compliance

Changelog

What shipped lately. Every release is in the docs.

Full changelog
  1. Manual journal entriesBalanced corrections without overwriting the original transaction.
  2. Administration settingsCompany settings redesigned into five tabs.
  3. SSO with OktaSAML single sign-on, plus stricter multi-currency validation.
  4. SCIM user provisioningUsers created and removed from your identity provider.
  5. Transaction rows for explanationsAn explained difference gets its own row, so everything still sums to zero.
  6. Currencies and FX conversionA new page to manage currencies and exchange rates.

Planning an integration? A 30-minute call with the team about your sources.