# API Documentation

## Parameters

### transaction_token
- **Type**: uuid  
- **Required**: Yes  
- The token of the transaction to route.

### financial_account_token
- **Type**: uuid  
- **Required**: Yes  
- The token of the financial account to route the transaction to.

## Response Codes

### 202
Accepted

### 400
A parameter in the query given in the request does not match the valid queries for the endpoint.

### 401
| Description | Reason |
| --- | --- |
| User has not been authenticated | Invalid or missing API key |
| API key is not active | The API key used is no longer active |
| Could not find API key | The API key provided is not associated with any user |
| Please provide API key in Authorization header | The Authorization header is not in the request |
| Please provide API key in the form Authorization: \[api-key\] | The Authorization header is not formatted properly |
| Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](/content/contact/index.html) |
| Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege |

### 404
The specified resource was not found.

### 422
Unprocessable entity.

### 429
Client has exceeded the number of allowed requests in a given time period.  
| Description | Reason |
| --- | --- |
| Rate limited, too many requests per second | User has exceeded their per second rate limit |
| Rate limited, reached daily limit | User has exceeded their daily rate limit |
| Rate limited, too many keys tried | One IP has queried too many different API keys |

## Example Request

```bash
curl --request POST \
     --url https://sandbox.lithic.com/v1/transactions/transaction_token/route \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '\n{\n  "financial_account_token": "00000000-0000-0000-0000-0000-000000000000"\n}\n'\n```

## Examples
- application/json  
- `400`  
- `401`  
- `404`  
- `422`  
- `429`