Skip to main content

Call a connected app's API as the user

POST 
/api/v1/integrations/pipedream/proxy

Makes an HTTP request through the selected connected account. The account must belong to the effective user and the destination is subject to the provider's allowed-domain rules. Those checks do not replace permission for the requested action. Each upstream app defines its own payload.

Upstream response handling​

Section ID: DOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#upstream-response-handling

Read the returned upstream status before treating the operation as successful: Travila can return HTTP 200 while the app's response contains a 404. Upstream headers and the body are returned as data, including on non-success status codes. Decode the body according to its content type; headers and bodies can contain third-party sensitive data.

Redirects are returned, not followed. Treat Location as untrusted: it need not be a signed or credential-free download URL. Validate the destination before opening it and never forward platform or account credentials to it.

The provider request timeout is 30 seconds. Page large results or use an appropriate provider download flow to stay within the response-body limit. A timeout can leave the external action's outcome unknown; check that action before retrying.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.

Use this in a guide: Let your assistant answer questions about a customer’s calendar

Request​

Responses​

The upstream response, whatever its status

Replace accountId with the authenticated user’s connected GitHub account; request that provider’s profile endpoint.​

Section ID: DOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#example-connected-apps-pipedreamProxyForCurrentUser-request

Request example

{
  "accountId": "apn_example",
  "method": "GET",
  "url": "https://api.github.com/user"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.​

Section ID: DOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#example-connected-apps-pipedreamProxyForCurrentUser-response

Response example

{
  "status": 1,
  "headers": {},
  "body": "ZXhhbXBsZQ=="
}

Document ID: DOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser. Section identities and revisions.

SectionStable reference
Call a connected app's API as the userDOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#overview
RequestDOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#request
ResponsesDOC-IN-tools-connections-apps-api-pipedreamProxyForCurrentUser#responses