Get Payment Events

curl --request GET \
  --url https://meet.briq.tz/api/v1/payments/{id}/events \
  --header 'Authorization: Bearer <token>'

{
  "status": "success",
  "code": 123,
  "message": "<string>",
  "data": [
    {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "transaction_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "status": "<string>",
      "message": "<string>",
      "actor_type": "<string>",
      "created_at": "2023-11-07T05:31:56Z"
    }
  ],
  "meta": {}
}

GET

api

payments

{id}

events

Get Payment Events

curl --request GET \
  --url https://meet.briq.tz/api/v1/payments/{id}/events \
  --header 'Authorization: Bearer <token>'

{
  "status": "success",
  "code": 123,
  "message": "<string>",
  "data": [
    {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "transaction_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "status": "<string>",
      "message": "<string>",
      "actor_type": "<string>",
      "created_at": "2023-11-07T05:31:56Z"
    }
  ],
  "meta": {}
}

Audit trail of status events for a payment, oldest first. Each event records the status, a human-readable message, and the source that triggered it in actor_type (merchant for actions you initiated; system, psp, poller, and admin for PayGrid-side updates).

Authorizations

Authorization

string

header

required

API key obtained from the merchant dashboard. When using the 'Try It' feature, enter only the key—the 'Bearer ' prefix is added automatically. For direct API calls, the 'Authorization: Bearer ' format is mandatory.

Path Parameters

string<uuid>

required

Response

Payment events

Standard success envelope wrapping all API responses.

status

enum<string>

Available options:

success

code

integer

HTTP status code echoed in the body

message

string

data

object[]

Response payload (object or array depending on endpoint)

Show child attributes