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

# Raw Passthrough

`POST /passthrough/raw`

Make an authenticated request to the underlying telematics provider and forward successful provider response bodies directly.

Use Raw Passthrough for provider endpoints that download inspection photos, documents, videos, or other non-JSON files.

Response rules:
- **Provider success (2xx):** the provider body is returned as raw bytes with the provider's `Content-Type` and status.
- **Provider error (non-2xx):** the response is HTTP `200` with a `PassthroughOutput` JSON envelope (`statusCode`, `headers`, `response`), matching `/passthrough`. Unsuccessful provider responses are therefore not surfaced as Terminal API errors; check the envelope's `statusCode` for the provider status.
- **Terminal error:** requests that fail before or around the provider call return a standard Terminal error status and JSON body.

For normal JSON API calls where you want Terminal to parse and wrap successful provider responses too, use `/passthrough` instead.

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

A successful provider response body, forwarded directly without the Terminal `PassthroughOutput` JSON envelope. The `Content-Type` reflects the provider's response (for example `image/jpeg` or `application/pdf`), not necessarily `application/octet-stream`.

## 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)