Connections

Call a connected app's API directly

Make an authenticated HTTP request to a connected app's own API, for endpoints no tool covers. Credentials are injected server-side and never exposed - do not send an Authorization header. The app's own status code is returned in the body (status), so a 404 there is the app's answer, not a failure of this call. Governed by the same approval policy as /execute: reads run now (200), writes freeze a pending approval (202). Only app connections proxy; MCP servers (use /execute) and social/ads connections (use their native /v1 endpoints) are refused with 409.

post/connections/{id}/proxy

Request

  • Base URL: https://api.crevio.co/v1
  • URL: https://api.crevio.co/v1/connections/{id}/proxy
  • Auth: API key in header Authorization

Path parameters

idstring required

Unified public connection id, as returned by GET /connections/connected. Opaque — pass it back verbatim.

Headers

Idempotency-Keystring

Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.

Request body

endpointstring required

Path relative to the app's API base URL (e.g. /gmail/v1/users/me/messages), or an absolute URL on the app's own domain.

method'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE'
headersobject

Extra headers forwarded to the app. Authorization and other transport headers are ignored.

Response

The app's response, verbatim

object'connection_proxy_response' required
connectionstring required

The connection public id

endpointstring nullable
statusinteger required

The status code the app returned

truncatedboolean

The response body exceeded the size cap and was cut

Changes

No recorded changes to this operation across all 2 revisions of this API.