Authorizations
Paxos APIs use OAuth 2 with the client credentials grant flow.
Token URLs:
- Production: https://oauth.paxos.com/oauth2/token
- Sandbox: https://oauth.sandbox.paxos.com/oauth2/token
Learn more in the API credentials guide →
Path Parameters
The unique id
in the Transaction
object.
Response
A successful response.
Transaction returned on create (Create Transaction), list (List Transactions) and get (Get Transaction) requests.
The transaction identifier used to query or refer to a specific transaction.
Idempotency key.
The start of the window which the transaction is eligible for settlement.
If omitted, transactions are immediately eligible for settlement upon success.
RFC3339 format, like YYYY-MM-DDTHH:MM:SS.sssZ
. ex: 2006-01-02T15:04:05Z
.
The end of the window which the transaction is eligible for settlement.
Transactions which are not cancelled or settled by this time will expire.
RFC3339 format, like YYYY-MM-DDTHH:MM:SS.sssZ
. ex: 2006-01-02T15:04:05Z
.
The Profile ID (profile_id) of the entity submitting the transaction.
The Profile ID (profile_id) of the entity receiving the transaction.
The obligations (representing one-way asset movements) to be settled atomically.
- PENDING: Initial state of a settlement transaction upon creation.
- SETTLED: Indicates all obligations belong to the settlement transaction have been enacted.
- EXPIRED: Indicates the settlement transaction is no longer eligible for settlement.
- CANCELLED: Indicates the settlement transaction was cancelled by the source profile.
- AFFIRMED: Indicates the settlement transaction will be eligible for settlement once within the window.
PENDING
, SETTLED
, EXPIRED
, CANCELLED
, AFFIRMED
The timestamp when the transaction was first created, RFC3339 format, like YYYY-MM-DDTHH:MM:SS.sssZ
.
The timestamp when the transaction was last updated, RFC3339 format, like YYYY-MM-DDTHH:MM:SS.sssZ
.