Glossary: PassthroughGlossary
A passthrough is a way to forward requests directly to an integration without going through the unified API.
Unified.to’s unified API is designed to handle the most common use cases for several API categories. For example, our ATS (application tracking system) API provides a unified model for working with entities that are common to ATS SaaS applications, such as managing candidates, jobs, and companies. Each of the ATS SaaS applications that we integrate with may have different names for those entities and different endpoints for creating, reading, updating, and deleting them, but with our unified API, you always use the Unified.to candidate, job, and company models and our endpoints for working with them, regardless of the SaaS integration you’re working with. Our unified approach abstracts away the differences between SaaS applications for the majority of the tasks that your application will perform.
However, there may be times when you need to access functionality or data that is specific to a particular SaaS application that isn’t covered by our unified API. In these edge cases, your application can bypass the unified API and send a platform-specific request directly to an endpoint in that SaaS application’s API. This request passes through the unified API and directly to the endpoint without being altered, hence the name “passthrough.”
Unified.to’s passthrough supports the following HTTP methods:
POST: Sends a POST request to the specified endpoint, complete with payload specific to the SaaS API.PUT: Sends a PUT request to the specified endpoint, complete with payload specific to the SaaS API.GET: Sends a GET request to the specified endpoint, complete with payload specific to the SaaS API.DELETE: Sends a DELETE request to the specified endpoint, complete with payload specific to the SaaS API.