Skip to main content
GET
Get the next pay run at a glance

Authorizations

Authorization
string
header
required

Server API key, scoped. pk_test_ keys hit the sandbox tenant.

Headers

X-Request-Id
string

Optional client correlation id, up to 128 characters. It is not echoed: the response's X-Request-Id is always our own req_… id. We log your value with the request as client_request_id, so support can find a request by either id. A longer value is refused with 400 parameter_invalid.

Maximum string length: 128

Response

The upcoming run.

The next pay run card.

object
string
required

Always upcoming_pay_run.

Allowed value: "upcoming_pay_run"
period
string
required

Pay month.

Pattern: ^\d{4}-\d{2}$
name
string
required

Run name.

pay_date
string<date>
required

Calendar date, interpreted in Africa/Lagos.

Example:

"2026-11-07"

approve_by
string<date-time>
required

RFC 3339, UTC.

Example:

"2026-10-27T08:41:00Z"

people_count
integer
required

People to be paid.

net
object
required

An amount in minor units (kobo, cents) with its currency. Never a decimal.

source_account
object
required

One of the business's own PanoFlow accounts (owned by the Accounts service).

source_available
object
required

The source account's balances.available (AccountBalances) when this summary was read.

run_id
string

run_… once prepared.

run_status
enum<string>

CONVENTIONS §8 lifecycle: draft → pending_approval (second approver) → scheduled (waits for pay day) → processing → completed | failed; rejected by the second approver; canceled from draft, pending_approval or scheduled. UI: completed → "Paid". Pay runs are never reversed.

Available options:
draft,
pending_approval,
scheduled,
processing,
completed,
failed,
rejected,
canceled,
reversed
short_by
object

Present when the balance cannot cover net pay ("Top up ₦… before 26 Nov, 4pm").