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.
Authorizations
API key in the format: Bearer {api_token}
Headers
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.
255Path Parameters
Unified public connection id, as returned by GET /connections/connected. Opaque — pass it back verbatim.
Body
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.
GET, POST, PUT, PATCH, DELETE Request body, sent verbatim. Ignored for GET.
Extra headers forwarded to the app. Authorization and other transport headers are ignored.
Response
The app's response, verbatim

