3. Application and webhook

The individual merchant has a personal application. Its id must be sent in the X-Application-ID header of every API-key call. Then configure the address that will receive webhooks.

Get your personal application

GET/applicationsSession token

Response 200
{
  "success": true,
  "data": {
    "items": [
      {
        "id": 1,
        "name": "Nom Prénom",
        "webhook_url": null,
        "has_webhook": false,
        "is_active": true,
        "created_at": "2026-11-02T08:00:00Z"
      }
    ],
    "pagination": {
      "...": "..."
    }
  },
  "meta": {
    "request_id": "...",
    "timestamp": "..."
  }
}
CodeWhen
401Missing or expired token.

Get the webhook signing secret

POST/applications/{id}/webhook/rotate-secretSession token

Generates a signing secret, shown only once. It is used to check that each webhook really comes from Kratos Pay. Calling it again immediately invalidates the previous secret.

Response 200
{
  "success": true,
  "data": {
    "application": {
      "id": 1,
      "webhook_url": "https://mon-site.cm/webhooks/kratospay",
      "has_webhook": true
    },
    "webhook_secret": "whsec_<secret>"
  },
  "meta": {
    "request_id": "...",
    "timestamp": "..."
  }
}
CodeWhen
404Application not found.