Djamo

Djamo Business API

REST API for businesses to collect payments, send single and mass transfers, check balance, manage sub-companies, and receive HMAC-signed webhooks.

Documentation GitHub

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/djamo:djamo-business-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

AsyncAPI Specification

generated: '2026-07-18'
method: generated
source: https://docs.djamo.com/api/webhooks.html
spec_type: AsyncAPI
note: >-
  Djamo publishes no AsyncAPI document; this 3.0.0 spec is generated faithfully
  from the four documented webhook event types and the documented HMAC-SHA256
  signature scheme. Payload fields mirror the documented `data` object.
asyncapi: 3.0.0
info:
  title: Djamo Business API Webhooks
  version: v1
  description: >-
    Server-to-server webhook events emitted by the Djamo Business API for
    transaction lifecycle and charge status changes. Each delivery is signed with
    an HMAC-SHA256 signature (base64) in the `x-djamo-hmac-sha256` header, computed
    over the raw request body using the partner SECRET_KEY.
  externalDocs:
    url: https://docs.djamo.com/api/webhooks.html
defaultContentType: application/json
components:
  securitySchemes:
    hmac:
      type: httpApiKey
      name: x-djamo-hmac-sha256
      in: header
      description: Base64 HMAC-SHA256 of the raw payload keyed with the partner SECRET_KEY.
  messages:
    transactionStarted:
      name: transactions/started
      title: Transaction started
      summary: A transaction request has been received and queued.
      payload:
        type: object
        properties:
          topic: { type: string, const: transactions/started }
          data: { type: object }
    transactionCompleted:
      name: transactions/completed
      title: Transaction completed
      summary: The transaction has been successfully executed.
      payload:
        type: object
        properties:
          topic: { type: string, const: transactions/completed }
          data: { type: object }
    transactionFailed:
      name: transactions/failed
      title: Transaction failed
      summary: The transaction failed to execute.
      payload:
        type: object
        properties:
          topic: { type: string, const: transactions/failed }
          data: { type: object }
    chargeEvents:
      name: charge/events
      title: Charge status updated
      summary: The status of a charge was updated.
      payload:
        type: object
        properties:
          topic: { type: string, const: charge/events }
          data: { type: object }
channels:
  transactionsStarted:
    address: transactions/started
    messages:
      transactionStarted:
        $ref: '#/components/messages/transactionStarted'
  transactionsCompleted:
    address: transactions/completed
    messages:
      transactionCompleted:
        $ref: '#/components/messages/transactionCompleted'
  transactionsFailed:
    address: transactions/failed
    messages:
      transactionFailed:
        $ref: '#/components/messages/transactionFailed'
  chargeEvents:
    address: charge/events
    messages:
      chargeEvents:
        $ref: '#/components/messages/chargeEvents'
operations:
  receiveTransactionStarted:
    action: receive
    channel: { $ref: '#/channels/transactionsStarted' }
    security:
      - $ref: '#/components/securitySchemes/hmac'
  receiveTransactionCompleted:
    action: receive
    channel: { $ref: '#/channels/transactionsCompleted' }
    security:
      - $ref: '#/components/securitySchemes/hmac'
  receiveTransactionFailed:
    action: receive
    channel: { $ref: '#/channels/transactionsFailed' }
    security:
      - $ref: '#/components/securitySchemes/hmac'
  receiveChargeEvents:
    action: receive
    channel: { $ref: '#/channels/chargeEvents' }
    security:
      - $ref: '#/components/securitySchemes/hmac'