Passthrough
Passthrough
curl --request POST \
--url https://app.vessel.dev/api/passthrough \
--header 'x-vessel-access-token: <x-vessel-access-token>' \
--header 'x-vessel-api-token: <x-vessel-api-token>' \
--data '{
"method": "<method>",
"path": "<path>"
}'
{
"$native": {
"body": {
"id": 123123123123
},
"headers": {
"content-type": "application/json"
}
},
"data": {
"id": 123123123123
}
}
curl --request POST \
--url https://app.vessel.dev/api/passthrough \
--header 'Content-Type: application/json' \
--header 'x-vessel-api-token: ' \
--header 'x-vessel-access-token: ' \
--data '{
"method": "PATCH",
"path": "/sobjects/Account/0011A00001XQ4ZUQA1",
"json": [
{
"Name": "Vessel"
}
]
}'
Authorizations
x-vessel-api-token[header]required
string
Headers
x-vessel-access-tokenrequired
string
Access Token
Body
json
object
The JSON body of the request.
methodrequired
string
Available options:
GET
, POST
, PUT
, PATCH
, DELETE
pathrequired
string
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
.
query
object
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.
Response
$native
object
data
object
curl --request POST \
--url https://app.vessel.dev/api/passthrough \
--header 'Content-Type: application/json' \
--header 'x-vessel-api-token: ' \
--header 'x-vessel-access-token: ' \
--data '{
"method": "PATCH",
"path": "/sobjects/Account/0011A00001XQ4ZUQA1",
"json": [
{
"Name": "Vessel"
}
]
}'
{
"$native": {
"body": {
"id": 123123123123
},
"headers": {
"content-type": "application/json"
}
},
"data": {
"id": 123123123123
}
}