PApaymongo
Triggers

List triggers by organization ID

get/v1/workflows/triggers

Request

  • Base URL
    https://api.paymongo.com
  • URL
    https://api.paymongo.com/v1/workflows/triggers
  • Auth
    none required

Query parameters

organization_idstring

Override organization ID (superuser only)

organization_idsstring

Filter by multiple organization IDs, comma-separated (superuser only, mutually exclusive with organization_id)

event_namestring

Filter by event_name in condition JSONB

statestring

Filter by state (active, pending, failed, deleted)

exclude_deletedboolean

Exclude deleted triggers (cannot be used with state=deleted)

limitinteger

Limit

after_idstring

Return the page after this position: either the opaque next_cursor from a previous response, or a bare trigger ID; excludes before_id

before_idstring

Return the page before this position: either the opaque prev_cursor from a previous response, or a bare trigger ID; excludes after_id

sort_by'created_at' | 'updated_at'

Sort column (default: created_at descending)

sort_order'asc' | 'desc'

Sort direction; requires sort_by

Headers

Organization-Idstring required

Organization ID

Response

OK

has_moreboolean

HasMore is true when more results exist beyond this page: after the last row when paging forward, before the first row when paging backward with before_id. It is a pointer so a non-paginated response omits the field rather than asserting false.

metaunknown
next_cursorstring

Opaque cursor for the last row on the page. Echo it as after_id to read the next page. It normally carries the sort it was issued under, so sort_by need not be repeated; for a very long text sort value the API falls back to a plain row id, which carries no sort, so a client pinning a non-default sort should keep sending sort_by. It sits beside has_more rather than inside meta, and is omitted when the page has no rows.

prev_cursorstring

Opaque cursor for the first row on the page. Echo it as before_id to read the previous page. It normally carries the sort it was issued under, so sort_by need not be repeated; for a very long text sort value the API falls back to a plain row id, which carries no sort, so a client pinning a non-default sort should keep sending sort_by. It sits beside has_more rather than inside meta, and is omitted when the page has no rows.

Example response

{
  "data": [
    {
      "created_at": "2026-01-15 10:30:00+00:00",
      "deleted_at": "2026-01-16 10:30:00+00:00",
      "id": "tr_abc123",
      "livemode": true,
      "organization_id": "org_abc123",
      "schedule_id": "schedule_abc123",
      "state": "active",
      "updated_at": "2026-01-15 10:30:00+00:00",
      "workflow_id": "flow_abc123"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.