Skip to main content
GET
Check where a mandate approval stands

Headers

x-sumvin-ceremony-ticket
string | null

Ticket from the approval link. Treat it as a secret: it addresses a live spending authorisation, carries exactly one decision, and stays usable until that decision is made or the approval window closes.

X-Timestamp-Format
string

Controls how timestamp fields are serialized in JSON response bodies.

Default (header omitted or any other value): epoch milliseconds as integers. iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.

Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".

Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.

Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.

Example:

"iso8601"

Response

Where the approval stands

Where an approval stands, and nothing that could be signed.

HAL-style hypermedia links for navigation.

status
enum<string>
required

Where the approval stands. proposed is still awaiting the account holder. stamped means they authorised it, declined means they refused it or it was withdrawn first, and expired means the window closed with no answer. The last three are final.

Available options:
proposed,
stamped,
declined,
expired
expires_at
integer
required

When this approval lapses, in epoch milliseconds. After it, nothing can be signed.