Saltar al contenido principal
GET
Read one recurring series

Autorizaciones

Authorization
string
header
requerido

JWT bearer token issued by the identity provider.

Parámetros de ruta

recurrence_id
string<uuid>
requerido

Series identifier.

Ejemplo:

"01a0d8fb-1a8b-7a10-b3c4-d5e6f7a8b9c0"

Respuesta

OK

accountId
string
requerido

Payer account.

Ejemplo:

"0195948b-bf02-7e4f-9a1b-2c3d4e5f6a7b"

amount
string
requerido

Amount of every occurrence, in BRL.

Ejemplo:

"150.00"

createdAt
string<date-time>
requerido
currency
string
requerido

Always BRL.

Ejemplo:

"BRL"

destination
object
requerido

The payee as photographed at creation. On a DICT series it is compared, before EVERY occurrence settles, against a fresh directory answer (REG-Art.9 section 6), which is why it is stored rather than re-resolved; the occurrences of a MANUAL series are sent to it as photographed, with no second lookup.

id
string
requerido

Series identifier.

Ejemplo:

"01a0d8fb-1a8b-7a10-b3c4-d5e6f7a8b9c0"

initiationType
enum<string>
requerido

How the destination was resolved at creation.

Opciones disponibles:
MANUAL,
DICT,
QR_CODE
Ejemplo:

"DICT"

lastPaymentDate
string<date> | null
requerido

Civil date of the series' final payment, when it has one. Null on an indefinite series, where reporting one would be a fabrication.

Ejemplo:

"2028-07-10"

materializedThrough
string<date> | null
requerido

Civil date up to which occurrences exist -- the edge of the materialized window. Occurrences beyond it do not exist yet. Null on a series that has never been materialized.

Ejemplo:

"2027-10-10"

occurrences
object[]
requerido

The currently materialized occurrences, oldest first -- NOT necessarily the whole series. materializedThrough states how far the window reaches, and a long-running series is enumerated in full through GET /v1/scheduled-payments?recurrence_id=. Empty and never null.

purpose
enum<string>
requerido

Always IPAY: REG-Art.11-P prohibits scheduling any other purpose.

Opciones disponibles:
IPAY
Ejemplo:

"IPAY"

recurrence
object
requerido

The rule the occurrences are computed from.

source
object
requerido

The payer as photographed at creation.

status
enum<string>
requerido

Situation of the SERIES, not of any one occurrence: a cancelled series still has settled occurrences behind it, and each occurrence carries its own status.

Opciones disponibles:
ACTIVE,
COMPLETED,
CANCELLED
Ejemplo:

"ACTIVE"

updatedAt
string<date-time>
requerido
description
string

The payer's memo, carried by every occurrence and returned exactly as stored.

Ejemplo:

"Aluguel"

metadata
object

The annotation the caller sent at creation, returned verbatim. Absent when none was sent -- this service never invents one.

Ejemplo:
payeeKey
object

The directory key a DICT-initiated series resolved at creation. It is kept because the mandatory re-lookup needs the key that was used, and a key is not one of the payee's attributes -- it cannot be reconstructed from the photograph above.