List contracts
GEThttps://app.shuttleglobal.com/c/api/instances/{instance_key}/contracts
Search and filter contract objects with pagination support.
Available fields for criteria and order:
id, account, alt_key, channel, completed, created, designation, division, frequency, gateway, initiative, legal_entity, next_charge, next_payment, nonce, occurrences, outstanding_amount, payment_method, retry_complete, retry_count, scheduler, status, updated
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Search criteria for filtering contracts. Available fields:
id, account, alt_key, channel, completed, created, designation, division, frequency, gateway, initiative, legal_entity, next_charge, next_payment, nonce, occurrences, outstanding_amount, payment_method, payment_method_status, payment_method_expires, retry_complete
(Y/N)
- retry_count
- scheduler (Y/N)
- status
- updated
Examples:
status=ACTIVE;FAILINGaccount=acc_12345_67890scheduler=Ynext_payment<>2024-01-01;2024-12-31
Sort order for results. Supports any field that criteria supports.
Defaults to created:desc if not specified. Append :desc for descending order.
Separate multiple order fields with commas.
Examples:
order=next_paymentorder=status,created:desc
Fields to expand into full objects. Separate multiple fields with commas.
Available fields:
- account (account object)
- payment_method (payment method object)
- gateway (gateway object)
- legal_entity (legal entity object)
- initiative (initiative object)
- designation (designation object)
- channel (channel object)
- last_transaction (transaction object)
- last_charge (charge object)
- created_session (session object)
- updated_session (session object)
Example: expand=account,payment_method,last_transaction
Number of records to return: 20 if not set, at most 1000.
Number of records to skip before the first one returned. offset + limit can’t exceed 5000; to read further, page by a field such as created instead. See Paging through results.
Responses
Section titled “Responses”List of contracts
object
A contract representing a one-time or recurring payment agreement
object
Associated account ID
Your reference for the contract
Contract amount
Channel ID
When the contract was completed
When the contract was created
Currency code
Description passed to the payment API
Designation ID
Payment frequency for recurring contracts
Payment gateway ID
Contract ID
When the contract was initiated
Initiative ID
Optional. When set to a future date, the contract stays active until this date even after its final scheduled payment is collected, so mid-term amendments can still be applied. Once the date has passed and no balance is outstanding, the contract completes normally. Omitted when not set.
ID of the last charge
ID of the last transaction
Legal entity ID
{ "order_id": "12345", "customer_reference": "CUS-001"}Custom key-value pairs stored on the contract
object
ID of the successor contract (created when amount or frequency is changed)
When the next payment will be attempted
Unique identifier for duplicate payment prevention. If the same nonce is submitted within 24 hours:
- No new contract will be created
- The success status of the previous contract will be returned
Your identifier for the account on this contract
Number of charges raised on this contract
Event date associated with the payment
Amount remaining to be paid
Payment method ID
Whether this is a recurring contract
Whether retry attempts are exhausted
Number of retry attempts made
Current contract status
When the contract was last modified
object
Bad request
Every error has a code and a message. Some add more fields alongside them, with detail about the error.
object
The error code, for example VALIDATION_ERROR, INVALID, INVALID_REQUEST, UNAUTHORIZED, FORBIDDEN or NOT_FOUND. Program against this, not the message.
What went wrong, in words, for logs and support.
Unauthorised: the API key is missing or not valid
Every error has a code and a message. Some add more fields alongside them, with detail about the error.
object
The error code, for example VALIDATION_ERROR, INVALID, INVALID_REQUEST, UNAUTHORIZED, FORBIDDEN or NOT_FOUND. Program against this, not the message.
What went wrong, in words, for logs and support.
Example
{ "code": "UNAUTHORIZED", "message": "Unauthorised"}Was this page helpful?
What went wrong?
Thanks for telling us.