Version v0.129.720

API reference

The DattaRemit API is Cybrid-compatible — the same paths, fields, GUIDs and {status, error_message, message_code} error bodies as Cybrid, so an existing Cybrid integration moves over with a base-URL and key change. Authenticate with your secret key as a bearer token. Every surface is generated from an OpenAPI spec tested against the live router in both directions, so this page cannot drift. Pick a domain, or use ⌘K to jump straight to a call.

Getting started

Every request carries a secret key as a bearer token. Keys are server-side only — anyone holding one can move money on your behalf.

Base URL

https://bank.dattaremit.com

Organization endpoints live on https://organization.dattaremit.com.

Environments

sk_test_Sandbox. No real money.

sk_live_Production. Needs an active organization and a populated IP allowlist.

Only shipped endpoints appear here

Endpoints still being built are absent rather than listed as “coming soon”. If it is on this page, you can call it today. See the quickstart to make your first call.

Authentication

curl https://bank.dattaremit.com/api/customers \
  -H "Authorization: Bearer sk_test_YOUR_KEY"

Error shape

{
  "status": 401,
  "error_message": "Signature verification raised",
  "message_code": "authentication_failed"
}

Errors match Cybrid exactly. Branch on message_code — it is the stable contract.

The API

Cybrid-compatible Bank and Organization APIs — the same paths, fields, GUIDs and error bodies as Cybrid. Bank endpoints take a bank-scoped key; Organization endpoints take an organization-scoped key.

Bank API

Accounts, customers, transfers, trades, plans and every other Bank resource.

Organization API

Organizations and webhook subscriptions, events and deliveries.

Objects

The object shapes referenced by the endpoints — identical to Cybrid's schemas.