List of client payment tokens
Changed onLists client_gateway_tokens, search and filters allow fine grained lists to be generated.
Query parameters can be added to performed more fine grained filtering of the client_gateway_tokens, these are handled by the ClientGatewayTokenFilters class which defines the methods available
Request
- Base URLhttps://demo.invoiceninja.com
- Authnone declared. Required headers: X-API-TOKEN, X-Requested-With
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Includes child relationships in the response, format is comma separated. Check each model for the list of associated includes
Replaces the default response index from data to a user specific string
ie.
?index=new_index
response is wrapped
{
'new_index' : [
.....
]
}
The number of records to return for each request, default is 20
The page number to return for this request (when performing pagination), default is 1
Headers
The API token to be used for authentication
Used to send the XMLHttpRequest header
Response
A list of client_gateway_tokens
Example response
{
"data": [
{
"id": "Opnel5aKBz",
"client_id": "2",
"token": "2",
"routing_number": "2",
"company_gateway_id": "2",
"is_default": true
}
],
"meta": {
"pagination": {
"total": 1,
"count": 1,
"per_page": 1,
"current_page": 1,
"total_pages": 1
}
}
}Changes
- info
added the new optional
queryrequest parameterpage - info
added the new optional
queryrequest parameterper_page - info
the response optional property
//became read-only for the status
- info
- breaking
the
response's property type changed fromobjectto no type for status
- breaking