Create new transaction
Authentication
The API key should be passed in the request headers as api-key for authentication.
Path parameters
Request
Transaction amount. A positive value creates a credit transaction and a negative value creates a debit transaction (unless transactionType is explicitly provided).
Unique identifier (UUID) of the associated balance definition.
Explicit transaction type. If not provided, the type is inferred from the sign of the amount (positive = credit, negative = debit).
Unique identifier of the contact involved in the transaction. Required unless LoyaltySubscriptionId is provided.
Unique identifier for the loyalty subscription. Required unless contactId is provided.
Time-to-live for the transaction in seconds. Must be at least 10 seconds if provided.
Timestamp specifying when the transaction event occurred (ISO 8601 / RFC 3339 format).
Response
Unique identifier (UUID) of the transaction.
Unique identifier (UUID) of the associated loyalty program.
Unique identifier (UUID) of the associated balance definition.
Optional timestamp indicating when the transaction event occurred (ISO 8601 format).
Reason for rejection if the transaction was declined (nullable).
Timestamp when the transaction was rejected (nullable).
Expiry date of the transaction (nullable).
Timestamp when the transaction was completed (nullable).
Timestamp when the transaction was canceled (nullable).