---
title: "Make Passthrough Request"
method: POST
path: "/api/v1/passthrough"
tags: ["Passthrough"]
---

# Make Passthrough Request

`POST /api/v1/passthrough`

## Headers

- `x-connector-token` string, required

## Request body

- PassThroughRequest
  - `method` 'CONNECT' | 'DELETE' | 'GET' | 'HEAD' | 'OPTIONS' | 'PATCH' | 'POST' | 'PUT' | 'TRACE', required — HTTP methods and descriptions Methods from the following RFCs are all observed: * RFC 9110: HTTP Semantics, obsoletes 7231, which obsoleted 2616 * RFC 5789: PATCH Method for HTTP
  - `path` string, required — Path of the request
  - `headers` object, nullable, required — headers of the request
  - `params` object, nullable — params of the request
  - `data` union — Body of the request
    - string
    - unknown[]
      - unknown
    - object
  - `request_format` 'JSON' | 'XML' | 'MULTIPART'
  - `response_format` 'JSON' | 'XML' | 'MULTIPART' | 'BINARY'
  - `timeout` number, nullable — timeout of the request

## Response `200`

Successful Response

- unknown

## Other responses

- `401` — Missing or invalid bearer authentication credentials.
- `403` — The credentials are valid but do not permit access to this resource, e.g. a connector token used on a different API category or a model whose writes are disabled.
- `422` — Validation Error
- `429` — Rate limit exceeded.

---

[API](https://skmtc.net/bindbee/apis/bindbee-apis.md) · [All operations](https://skmtc.net/bindbee/apis/bindbee-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bindbee/bindbee-apis/versions/7da10dc93a21/schema)