Turn a cURL example into a pipe call

Map each part of a cURL command from an API's documentation (method, URL, headers, body, basic auth) to the fields of an API call in a custom pipe.

  • Verified Nov 17, 2026
  • Classic builder

On this page
  1. Where each part of a cURL command goes
  2. Example 1: a GET request with a bearer token
  3. Example 2: a POST request with a JSON body
  4. Troubleshooting

Most API documentation shows requests as cURL commands. Each part of a cURL command has a matching field in a pipe's API call, so you can copy a working example into a custom pipe piece by piece.

Where each part of a cURL command goes #

Open the pipe, go to API Calls, and click Add New Call (or select an existing call). Then use this table.

In the cURL commandIn the API call
-X GET, -X POST, --request PUT (no -X usually means GET, or POST when there is -d)Overview tab: the method (GET, POST, PUT, DELETE or PATCH).
The URL, including anything after ?Overview tab: URL. Replace values that change with a parameter in curly braces, such as {Customer ID}, and add that parameter on the Parameters tab.
-H "Authorization: Bearer ..."Authorization tab: Bearer Token, with the token in Token. Or add it as a header.
-u username:passwordAuthorization tab: Basic Authorization, with Username and Password.
Any other -H "Name: value"Headers tab: Add New Header, with the part before the colon in Key and the part after it in Value. Bulk Edit accepts the same Name: value lines pasted in one go.
-d '{...}' or --data '{...}' with JSONRequest tab: Request Type RAW Data, Content Type JSON, and paste the JSON.
-F name=value or -d name=value&...Request tab: Request Type Form Data, and Add New Request for each name and value.

Example 1: a GET request with a bearer token #

Shell
curl -X GET "https://api.example.com/v1/users?status=active" \
     -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
  1. Method and URL On the Overview tab, choose GET and enter https://api.example.com/v1/users?status=active as the URL.
  2. Token On the pipe's Global Parameters tab, add a parameter named Access Token with your token as its Default Value and Visibility set to Private. Then, on the call's Authorization tab, choose Bearer Token and enter {Access Token} in Token.
  3. Test Click Save, open the Test tab and click Test. A Status of 200 and a list of users in the Body means the call works. Click Populate Responses to map the values you need.

Example 2: a POST request with a JSON body #

Shell
curl -X POST "https://api.example.com/v1/users" \
     -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"name": "Jane Doe", "email": "jane@example.com"}'
  1. Method and URL On the Overview tab, choose POST and enter https://api.example.com/v1/users.
  2. Token Set the Authorization tab to Bearer Token with {Access Token}, as in example 1.
  3. Content type header On the Headers tab, click Add New Header, enter Content-Type as the Key and application/json as the Value.
  4. Parameters for the values The name and email change with each record, so on the Parameters tab add two parameters, Name and Email.
  5. Body On the Request tab, choose RAW Data and JSON, and enter the body with the parameters in place of the example values. You can insert each parameter with Add Parameter.
JSON
{"name": "{Name}", "email": "{Email}"}

On the Test tab, enter sample values for Name and Email and click Test. When you use the pipe in your app, you map record fields to these parameters; see Run a pipe from a form, field, component or workflow.

Troubleshooting #

  • Test the call first. The Test tab shows the Status code and the response Body (or Raw text). Compare them with the response the documentation shows for the same cURL command.
  • Check the parameter names. Each {Name} must match a parameter's name exactly, including spaces and capital letters.
  • Check quotes in JSON bodies. Text parameters inside JSON need quotes around them ("{Name}"); numbers and true/false do not.
  • Debug in the live app. If the call works on the Test tab but not in your app, check Enable Debug Mode on the pipe's General tab, run the pipe in the live app, and read the response in the browser's developer console.

Was this page helpful?

Something wrong or missing on this page? Tell us.