How it works
Unified models cover the common fields, but every platform has endpoints and objects that fall outside them. A passthrough request names the native path and method, and the provider attaches the connection's credentials, applies rate limits and records the call. The response comes back in the platform's own format, not the unified schema.
Example
A NetSuite customer stores warranty data in a custom record type. The product calls the custom record endpoint through passthrough, using the existing connection, instead of asking the customer for separate credentials.
In integrations
In Unify Int, passthrough requests reuse the connection's auth and appear in Unify Monitor next to unified calls, so you can reach any native endpoint without a second integration. Passthrough is different from a pass-through API, which describes a no-storage data model rather than a native call. Passthrough keeps you from waiting on a vendor's roadmap. Use it for the long tail, and ask for frequently used native fields to be modeled properly so your code does not depend on raw formats.