PATCH
Proxies a downstream PATCH request to a service and injects the necessary credentials into a request stored in Vault. This allows you to have an additional security layer and logging without needing to rely on Unify for normalization. Note: Vault will proxy all data to the downstream URL and method/verb in the headers.
Headers
ID of the consumer which you want to get or push data from
The ID of your Unify application
Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
Specify which unified API to use for the connection lookup. Required for multi-API connectors (e.g., Workday) to ensure the correct credentials are used.
Downstream URL
Downstream authorization header. This will skip the Vault token injection.
Override the default downstream request timeout in milliseconds. The default is 28000 (28 seconds).
Set to false to opt out of the redirect to the presigned download URL. Instead of a 30x response, you receive a 200 JSON body { url, expires_at } containing the URL and its expiry, which you can fetch explicitly. Use this if your client automatically forwards the Authorization header onto redirects, since the downstream storage provider will reject that request. Any value other than false (or omitting the header) preserves the default redirect behavior.
Response
Ok. When the request includes x-apideck-follow-redirects: false and the downstream response would otherwise redirect to a presigned URL (oversized responses), the body is instead an application/json object { url, expires_at } — fetch url explicitly (without the Authorization header) to retrieve the payload.