Using A Postman API Call With Integrate.io's REST API Connector

If you've built a working API call in Postman, getting it into Integrate.io ETL is now as simple as copying a cURL command. The REST API source and destination components include an Import cURL button that automatically populates the URL, method, headers, and body from any cURL command — including those exported directly from Postman.

For APIs that use OAuth 2.0 authentication, Integrate.io now also supports Universal OAuth connections, which handle token retrieval and refresh automatically. This guide covers both.

Moving Your Postman Calls to Integrate.io ETL

Ready to use your Postman calls in Integrate.io? Let's get started!

• In Postman, click the code button (<>).

• Select cURL from the language dropdown. Copy the entire cURL command.

   
• In the REST API source or destination component, click the Import cURL button in the Request section (Step 2).
  
• Paste the cURL command into the dialog and click Import.
  
• Integrate.io will automatically populate the Method, URL, Headers, and Body fields from your cURL command. Review the imported values to confirm they look correct, then proceed to configure the response schema as normal.
• Note: If your Postman call includes a hardcoded Bearer token in the Authorization header, the Import cURL will bring that token value across. For a durable integration where the token is refreshed automatically, replace the hardcoded token with a Universal OAuth connection — see the OAuth section below.

OAuth 2.0 Authorization

Postman makes OAuth easy — you enter your credentials and it fetches and injects a token automatically. Integrate.io now offers the same experience through Universal OAuth connections, which handle token retrieval, injection, and refresh without any manual setup.

Recommended approach: Use a Universal OAuth connection

Rather than copying a token from Postman (which will eventually expire) or manually configuring Curl functions and variables, create a Universal OAuth connection in Integrate.io:

1. Navigate to Connections and create a new Universal OAuth connection.
2. Select the authentication method that matches your API — OAuth 2.0, Client Credentials, or Custom Auth.
3. Configure the connection using the same credentials you used in Postman (Client ID, Client Secret, Token URL, etc.).
4. In Step 1 of the REST API source or destination component, select Connection and choose your Universal OAuth connection.

The token is injected automatically on every request and refreshed before it expires. No hardcoded values, no package variables needed.

For full setup instructions, see Allowing Integrate.io ETL access to any API with OAuth.

Using Import cURL with a temporary token

If you just want to test quickly and already have a working Bearer token from Postman, you can use Import cURL to bring across the full request including the Authorization header. Keep in mind that hardcoded tokens expire — for any production pipeline, replace the token with a Universal OAuth connection as described above.

Advanced: Manual OAuth setup using Curl functions

For APIs with highly non-standard authentication flows that cannot be configured through Universal OAuth, the manual approach using package variables and Curl functions is still available. See the API Ingestion Guide (example #4) for a full walkthrough.

Conclusion

With the Import cURL button, translating a working Postman call into an Integrate.io pipeline takes seconds. For OAuth-protected APIs, Universal OAuth connections give you the same seamless token handling you're used to in Postman — without hardcoded credentials or manual refresh logic. If you have questions, our support team is available via live chat in the platform.