Vessel

Vessel Passthrough API

The passthrough API from Vessel — 2 operation(s) for passthrough.

Documentation GitHub OpenAPI

Operations 2

POST /crm/passthrough Passthrough Request #

POST /api/passthrough Passthrough Request #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/vessel-passthrough-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Vessel Passthrough API
  version: '1.0'
  description: 'Operations tagged passthrough across 2 of this provider''s published API definitions: vessel-crm-v1-openapi.yml, vessel-platform-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.vessel.dev
security:
- VesselAPIToken: []
tags:
- name: passthrough
paths:
  /crm/passthrough:
    post:
      summary: Passthrough Request
      tags:
      - passthrough
      operationId: post-crm-passthrough
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                title: responseBody
                description: ''
                type: object
                properties:
                  headers:
                    type: object
                  url:
                    type: string
                    description: The full URL that the request was sent to.
                  statusCode:
                    type: number
                    description: The HTTP status code of the response from the downstream CRM.
                  body:
                    AnyValue:
                      description: The body of the response from the downstream CRM.
                required:
                - id
              examples:
                example-1:
                  value:
                    headers:
                      content-type: application/json
                    url: https://mydomain.my.salesforce.com/services/data/v53.0/sobjects/Account
                    statusCode: 200
                    body:
                      id: 0011A00001XQ4QSQAZ
                      success: true
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                accessToken:
                  type: string
                method:
                  type: string
                  enum:
                  - GET
                  - POST
                  - PUT
                  - PATCH
                  - DELETE
                path:
                  type: string
                  description: The path to send the request to. Vessel handles the domain so for a request to Salesforce instead of using `https://mydomain.my.salesforce.com/services/data/v52.0/sobjects/Account` you would use `services/data/v52.0/sobjects/Account`.
                body:
                  type: object
                  description: The body of the request.
                query:
                  type: object
                  description: The query parameters to send with the request as key value pairs. These are appended to the URL when the request is sent to the CRM.
              required:
              - accessToken
              - method
              - path
            examples:
              example-1:
                value:
                  accessToken: string
                  method: PATCH
                  path: services/data/v53.0/sobjects/Account/0011A00001XQ4ZUQA1
                  body:
                  - Name: Vessel
        description: ''
      description: Send an authenticated passthrough request to the downstream CRM. This is useful for making requests to endpoints that are not yet supported by Vessel.
    servers:
    - url: https://api.vessel.dev
  /api/passthrough:
    post:
      summary: Passthrough Request
      operationId: passthrough
      parameters:
      - name: x-vessel-access-token
        in: header
        description: Access Token
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                title: responseBody
                description: ''
                type: object
                properties:
                  $native:
                    type: object
                    properties:
                      headers:
                        type: object
                      body:
                        type: object
                      url:
                        type: string
                required:
                - id
              examples:
                example-1:
                  value:
                    $native:
                      headers:
                        content-type: application/json
                      body:
                        id: 123123123123
                      url: https://test.my.salesforce.com/services/data/v52.0/sobjects/Account/0011A00001XQ4ZUQA1
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                method:
                  type: string
                  enum:
                  - GET
                  - POST
                  - PUT
                  - PATCH
                  - DELETE
                path:
                  type: string
                  description: The path to send the request to. Vessel handles the domain, for example, a request to Salesforce would use `/services/data/v52.0/sobjects/Account` instead of `https://mydomain.my.salesforce.com/services/data/v52.0/sobjects/Account`.
                json:
                  type: object
                  description: The JSON body of the request.
                query:
                  type: object
                  description: The query parameters to send with the request as key value pairs. These are appended to the URL when the request is sent to the integration provider.
              required:
              - method
              - path
            examples:
              example-1:
                value:
                  method: PATCH
                  path: /services/data/v53.0/sobjects/Account/0011A00001XQ4ZUQA1
                  json:
                  - Name: Vessel
        description: ''
      description: Send an authenticated passthrough request to the downstream system. This is useful for making requests to endpoints that are not yet supported by Vessel.
      tags:
      - passthrough
    servers:
    - url: https://api.vessel.dev
components:
  securitySchemes:
    VesselAPIToken:
      name: vessel-api-token
      type: apiKey
      in: header
x-refined-from:
- vessel-crm-v1-openapi.yml
- vessel-platform-openapi.yml

Vessel Passthrough API

Operations 2

Documentation

Specifications

SDKs

Other Resources