List FTP mappings
Mappings
List FTP mappings
Retrieve FTP mappings using GraphQL. Supports filtering, sorting, and pagination via relay-style connections.
POST
List FTP mappings
Query Structure
Filter Argument
All filters are passed inside thefilter argument. Each filter field accepts an input object with operators (e.g. eq, ilike, from, to, between):
Available Filters
| Filter | Input Type | Operators | Description |
|---|---|---|---|
mapping_group_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Parent mapping group ID |
account_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Internal account ID |
account_in_file | StringInputType | eq, ilike, like, in, between | Account value in the file |
customer_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Internal customer ID |
delivery_address_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Internal delivery address ID |
collection_address_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Internal collection address ID |
created_at | DatetimeInputType | eq, from, to, between | Creation timestamp |
Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Body
application/json
GraphQL query string
Example:
"query($filter: FtpMappingFilterType) { ftp_mappings { all(filter: $filter) { edges { node { id account { id } customer { id } delivery_address { id } collection_address { id } mapping_fields mapping_group_id } } } } }"
Query variables including the filter object
Example:
{
"filter": { "mapping_group_id": { "eq": "4" } }
}
