---
title: "Passthrough"
method: POST
path: "/passthrough"
tags: ["Data Management"]
---

# Passthrough

`POST /passthrough`

Make an authenticated request to the underlying telematics provider. 

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`.

## Headers

- `Connection-Token` string, required

## Request body

- object
  - `method` 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE', required — The method for the third-party request, such as GET or POST.
  - `path` string, required — The path for the third-party request, such as `/reports`
  - `headers` object — The headers to use for the request (Terminal will handle the connection's authorization headers)
  - `body` string — The request body

## Response `200`

OK

- object
  - `method` string, required — The HTTP method that was used when making the request.
  - `path` string, required — The path that was called with the passthrough request.
  - `statusCode` integer, required — The resulting status code from the passthrough request.
  - `headers` object, required — Any returned headers from the passthrough request.
  - `response` union, required — The response body from the passthrough request
    - object
    - string
    - number
    - boolean

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `422` — Unprocessable Entity
- `429` — Too Many Requests
- `500` — Internal Server Error
- `501` — Not Implemented
- `502` — Bad Gateway
- `504` — Gateway Timeout Error

---

[API](https://skmtc.dev/withterminal/apis/terminal-telematics-api.md) · [All operations](https://skmtc.dev/withterminal/apis/terminal-telematics-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/withterminal/terminal-telematics-api/revisions/90249c4a1739/schema)