A defined API for financial records.

Read accounts, entities, transactions, statements, receivables and payables. Upload records into the same tenant-scoped financial model that powers every Stratiri module.

Stratiri APIv1

Contract available during implementation

RequestRead scope

GET /v1/receivables?overdue_only=true
  &currency=EUR

Authorization: Bearer STRATIRI_API_KEY
Accept: application/json

200 OK · application/json142 ms

{
  "data": {
    "receivables": [{
      "invoice_number": "INV-18492",
      "customer_id": "CUS-204",
      "currency": "EUR",
      "total_amount": 148500,
      "amount_outstanding": 96200,
      "days_overdue": 17
    }],
    "summary": { "count": 48, "currency": "EUR" }
  }
}

01 / Integration model

Scoped to the work, not to endpoints.

We agree what the module has to do, identify the source records behind it, then define how they are mapped and validated before routine movement begins.

Implementation path

One scoped route from source system to working financial record.

The interface is designed with the operating model. Credentials, refresh expectations, ownership and rejected-record handling are agreed before the connection becomes routine.

Financial responsibilityDefine what the module must support.

Scope

Source contractMap identifiers, entities, dates, currencies and ownership.

Map

Controlled validationCheck samples, totals and rejected records before routine use.

Validate

Operating connectionMonitor the agreed route as source structures change.

Run

02 / Record surface

The contract covers what finance works from.

Read-scoped endpoints expose the maintained financial record types. A separate write scope controls upload, so ingestion is never an accident of read access.

01AccountsBalances, currency and account state

02EntitiesLegal structures and status

03TransactionsAccount activity and dates

04StatementsPoint-in-time account balances

05ReceivablesInvoices, due dates and outstanding value

06PayablesBills, vendors and payment state

03 / Request boundary

Every request has a boundary.

Authentication, access scope, tenant context and schema validation all resolve before a financial record is returned or accepted. Nothing crosses on trust.

01API keyIdentify the integration

02ScopeRead or write capability

03Tenant contextResolve the intended organisation

04SchemaValidate the record contract

05Financial recordsReturn or accept data

200 Success400 Invalid request401 Missing or invalid key403 Insufficient scope404 Record not found429 Rate limit exceeded

Discuss your first integration.

Talk to the technical team