REST Connector
The REST Connector lets you integrate Adeptia with any external service that exposes a REST API, enabling you to send data to and receive data from HTTP endpoints as part of your automation workflows.
What you can do
With a REST connection configured, you can.
Combine REST connections with other connector types to build end-to-end integrations across systems.
What you configure
When setting up a REST connection, you provide the URL of the API endpoint you want to connect to, along with the authentication details required by that service.
Authentication options
The REST Connector supports several authentication approaches. You select the one that matches what the target API requires.
| Authentication type | How it works |
|---|---|
| Basic | You supply a username and password, which are used to authenticate requests to the endpoint. |
| OAuth 2.0 | You authorize access through an OAuth 2.0 flow. The supported grant types are Authorization Code, Implicit, Client Credentials, and PKCE (Proof Key for Code Exchange). |
OAuth 2.0 grant types
Each OAuth 2.0 grant type follows a distinct flow:
- Authorization Code: Redirects you to the service's authorization page, where you grant access. The platform then exchanges the resulting code for an access token.
- Implicit: Redirects you to the authorization page and receives the token directly in the browser callback, without a separate code-exchange step.
- Client Credentials: The platform authenticates directly using a client ID and client secret, without user interaction. Credentials can be sent as query parameters, in the request body, or in an authorization header, depending on what the target service requires.
- PKCE (Proof Key for Code Exchange): An Authorization Code flow that uses a code verifier and code challenge pair.