Skip to main content
Karsa’s developer platform accepts versioned source records through one authenticated ingestion surface. Use the Onboarding tab for a working first integration. Use this section when you need to understand a resource, its identifiers, or how it connects to the rest of the platform.

​
Platform components

​
The contract shared by every component

  • Your source supplies a stable external identifier for each record.
  • Karsa returns a stable resourceId for relationships and an immutable versionId for the exact observation it accepted.
  • A changed observation appends a version; it does not overwrite history.
  • Idempotency-Key makes retrying the same logical request safe.
  • A KYB dossier pins the exact business CustomerVersion and evidence being evaluated.
Read How records fit together for the identifier graph and upload order. Use the API Reference for authoritative fields, validation rules, and response schemas.

​
Continue

Customers and KYB

Model individuals, businesses, UBO Customers, and their relationships.

Accounts

Link financial accounts to the Customers that own or use them.

Documents

Upload immutable evidence and reference its exact version.

Transactions

Send money movement and connect it to known parties and accounts.