List legal entity routes
GEThttps://app.shuttleglobal.com/c/api/instances/{instance_key}/legal_entity_routes
Search and list legal entity route objects with pagination support.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Search criteria for filtering routes. Available fields:
- id
- created
- gateway
- legal_entity
- legal_entity_code
- status
- updated
Examples:
status=ACTIVElegal_entity=le_12345_10000gateway=gw_12345_10000
Sort order for results. Supports any field that criteria supports.
Defaults to created:desc if not specified. Append :desc for descending order.
Fields to expand into full objects. Separate multiple fields with commas.
Available fields:
- created_session (session object)
- gateway (gateway object)
- legal_entity (legal entity object)
- updated_session (session object)
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 legal entity routes
object
A mapping between a legal entity and a payment gateway
object
Unique identifier for the route
/^lr_[0-9]+_[0-9]+$/Legal entity ID
Gateway ID
Array of ISO currency codes this route supports
Array of payment method types this route supports (e.g., VISA, MASTERCARD)
Custom key-value pairs
object
Payment routing rules per source type
object
Rules for ecommerce payments
object
Rules for MOTO payments
object
Rules for POS payments
object
Rules for recurring payments
object
Workflow configurations attached to this route
object
Status of the route:
- LINKED - active but not yet used
- ACTIVE - in use
- INACTIVE - no longer in use, no payments may utilise this connection
- RUNDOWN - no longer in use for new card details, saved cards may continue to be used
When the route was created
Session that created this route
When the route was last updated
Session that last updated this route
Version of the record
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.