POST
/
passthrough
curl --request POST \
  --url https://api.withterminal.com/tsp/v1/passthrough \
  --header 'Authorization: Bearer <token>' \
  --header 'Connection-Token: <connection-token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "method": "POST",
  "path": "/reports",
  "headers": {},
  "body": "{\"reportId\":\"1234\"}"
}'
{
  "method": "POST",
  "path": "/reports",
  "statusCode": 200,
  "headers": {
    "Content-Type": "application/json"
  },
  "response": {
    "reportId": "1234"
  }
}

This endpoint helps ensure that you are never limited by Terminal. You can use passthrough requests to access capabilities that may be limited to a specific TSP or not yet in the normalized model.

Our team is here and ready to support custom use cases that may need /passthrough.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
Connection-Token
string
required

The token returned when a user authenticated their account. This authorizes access to a specific account.

Example:

"con_tkn_22vUhkC6tgre4kwaYfUkCDA1rzn6eyb4"

Body

application/json

Response

200
application/json

OK

The response is of type object.

POST
/
passthrough
curl --request POST \
  --url https://api.withterminal.com/tsp/v1/passthrough \
  --header 'Authorization: Bearer <token>' \
  --header 'Connection-Token: <connection-token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "method": "POST",
  "path": "/reports",
  "headers": {},
  "body": "{\"reportId\":\"1234\"}"
}'
{
  "method": "POST",
  "path": "/reports",
  "statusCode": 200,
  "headers": {
    "Content-Type": "application/json"
  },
  "response": {
    "reportId": "1234"
  }
}

This endpoint helps ensure that you are never limited by Terminal. You can use passthrough requests to access capabilities that may be limited to a specific TSP or not yet in the normalized model.

Our team is here and ready to support custom use cases that may need /passthrough.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
Connection-Token
string
required

The token returned when a user authenticated their account. This authorizes access to a specific account.

Example:

"con_tkn_22vUhkC6tgre4kwaYfUkCDA1rzn6eyb4"

Body

application/json

Response

200
application/json

OK

The response is of type object.