Unified.to passthrough: relative paths, __domain, and raw responses

Not specified by the original author.

TL;DR: The path must be relative to the platform base API URL, so for a full endpoint of YOUR_HOST.vendor.com/v2/users you pass v2/users. Context: Official docs (docs.unified.to, Passthrough API): teaches the rules that make passthrough calls succeed. Find each integration's base URL under Feature Support then Passthrough on app.unified.to/integrations (click through to the integration).

Context: Official docs (docs.unified.to, Passthrough API): teaches the rules that make passthrough calls succeed. The path must be relative to the platform base API URL, so for a full endpoint of YOURHOST.vendor.com/v2/users you pass v2/users. Find each integration's base URL under Feature Support then Passthrough on app.unified.to/integrations (click through to the integration). There is exactly one reserved URL parameter: domain, which overrides the default API URL for that integration. Passthrough responses are raw and unmodified, so formats, data structures, and error shapes vary per platform and your code must handle that. If you only need vendor fields missing from the unified model, the docs say to try raw fields or the Metadata API first, and if you reach for passthrough the record's original vendor ID is available in raw._id. Most implementations should not need passthrough at all; for a real gap the docs suggest contacting them so the capability can be added to the unified API instead.

Checklist from the docs: 1. Pass the path relative to the platform base URL, never the full URL. 2. Look up the base URL per integration under Feature Support then Passthrough. 3. Use domain only to override the default API URL. 4. Expect raw, platform-specific responses and error formats, no normalization. 5. Grab the original vendor ID from raw.id when you need it for passthrough calls. 6. Try raw fields or the Metadata API before building on passthrough, and report genuine gaps so they can be added to the unified API.

When to use

You hit exactly this: Unified.to passthrough: relative paths, __domain, and raw responses in Unified.to passthrough.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Unified.to passthrough (versions mentioned here: v2).

Official docs page: https://docs.unified.to/passthrough/overview. What it documents: Official docs (docs.unified.to, Passthrough API): teaches the rules that make passthrough calls succeed. The path must be relative to the platform base API URL, so for a full endpoint of https://api.vendor.com/v2/users you pass v2/users. Find each integration's base URL under Feature Support then Passthrough on app.unified.to/integrations (click through to the integration). There is exactly one reserved URL parameter: domain, which overrides the default API URL for that integration. Passthrough responses are raw and unmodified, so formats, data structures, and error shapes vary per platform and your code must handle that. If you only need vendor fields missing from the unified model, the docs say to try raw fields or the Metadata API first, and if you reach for passthrough the record's original vendor ID is available in raw.id. Most implementations should not need passthrough at all; for a real gap the docs suggest contacting them so the capability can be added to the unified API instead. The verified guidance distilled above: Checklist from the docs: 1. Pass the path relative to the platform base URL, never the full URL. 2. Look up the base URL per integration under Feature Support then Passthrough. 3. Use domain only to override the default API URL. 4. Expect raw, platform-specific responses and error formats, no normalization. 5. Grab the original vendor ID from raw.id when you need it for passthrough calls. 6. Try raw fields or the Metadata API before building on passthrough, and report genuine gaps so they can be added to the unified API.