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.
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" }
}'
Data integration
Seven ways to get data in. Pick where your data lives.
- 01Application connectorsPreferred
Standard connectors for payment providers, ERPs, billing and banks, built by Actuals. You share credentials, Actuals collects the data. The most automated option.
- 02Database connectorsPreferred
Give Actuals read access to Snowflake or BigQuery and it runs the queries itself. Efficient once it is set up.
- 03Actuals SFTP serverPreferred
Your system exports files on a schedule and uploads them to a secure server run by Actuals. Reliable when the export can be automated.
- 04Raw transactions APIUse case
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.
- 05External SFTP serverUse case
Actuals collects files from a server a third party runs. For when that party has no other way to deliver data.
- 06Upload in the platformUse case
Upload a CSV file with a header row yourself. Good for sources that change rarely.
- 07Email connectorUse case
Send CSV attachments to an address of your Actuals environment and they are imported. The last option, when nothing else is possible.
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": { ... }
}
GET https://api.actuals.io/v1/raw_transactions
?timestamp_gte=2025-01-01T00:00:00
×tamp_lt=2025-01-02T00:00:00
&expand=raw_transactions&limit=500
{
"raw_transaction_count": 5,
"next_cursor": "eyJ0cyI6...",
"raw_transactions": [ { "external_id": "ORD-123", ... } ]
}
- 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.
- Filter on business time. Results follow the timestamp you sent, not the moment Actuals received it. So a day in your books is a day in the API.
- Compare every day. Ask for the count once a day has closed. If it doesn’t match your database, ask again with the list of external_ids and resend what is missing.
- Allow four hours. A transaction can take up to four hours to show up here after it was sent.
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.
- Manual journal entriesBalanced corrections without overwriting the original transaction.
- Administration settingsCompany settings redesigned into five tabs.
- SSO with OktaSAML single sign-on, plus stricter multi-currency validation.
- SCIM user provisioningUsers created and removed from your identity provider.
- Transaction rows for explanationsAn explained difference gets its own row, so everything still sums to zero.
- 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.