How to Export a Postman Request as cURL for ZappySys Support

SSIS PowerPack JSON / REST
, , , , , ,
1

Overview

If an API request works in Postman but fails in ZappySys, sharing the request as cURL helps compare the API call and identify configuration differences.

This helps us:

  • Reproduce your exact request
  • Identify missing headers or authentication issues
  • Fix configuration problems quickly

When Should You Use This?

Use this guide when:

  • You see: “API works in Postman but fails in ZappySys”
  • Support needs the exact API request details

Step 1: Verify Your Request in Postman

Before exporting, double-check:

  • HTTP Method (GET, POST, PUT, DELETE)
  • Request URL & query parameters
  • Headers (Authorization, Content-Type, etc.)
  • Request Body (JSON, form-data, x-www-form-urlencoded)

Full Postman request view
Full Postman request view1117×438 48.1 KB

Step 2: Convert Postman Request to cURL

  1. Click the Code (</>) button (top-right, near the Send button)
  2. This opens the Code Snippet window
  3. Select cURL from the dropdown
  4. Click Copy to Clipboard

Code button → cURL selection
Code button → cURL selection484×335 30.4 KB

Note: Postman supports multiple languages, but always choose cURL for troubleshooting with ZappySys.

Step 3: Clean Up the cURL (Recommended)

Postman often includes extra headers. Review headers before sharing. Make sure required headers, such as Authorization and Content-Type, are included.:

Remove unnecessary headers:

  • Postman-Token
  • User-Agent (optional)
  • Accept-Encoding (optional)

Keep only important headers:

  • Authorization
  • Content-Type
  • Any required custom headers

Example (Clean cURL)

curl --location 'https://api.example.com/data' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data-raw '{"name":"test"}'

Step 4: Share the cURL Script

Provide your cURL when:

  • Creating a support ticket
  • Replying to ZappySys support

Important: Always mask sensitive data
(Access Tokens, API Keys, Client Secrets)

Step 5: (Optional) Convert to Raw HTTP Format

If needed, you can also share your request like this:

POST /data HTTP/1.1
Host: api.example.com
Authorization: Bearer <token>
Content-Type: application/json

{"name":"test"}

How This Helps in ZappySys

With the cURL request, we can:

  • Reproduce your API call in:
    • REST API Task
    • JSON/XML/CSV Source or Web API Destination
    • ODBC / JSON Driver / XML Driver
  • Quickly identify:
    • Missing headers
    • Incorrect authentication
    • Body formatting issues

Best Practice (Highly Recommended)

Whenever reporting:

“Working in Postman but not in ZappySys”

Always include your cURL script

This avoids back-and-forth and significantly speeds up resolution.

Advanced Tips

  • OAuth 2.0 → Ensure token is included in Authorization header
  • Redirects → Keep --location in cURL
  • Cookies → Include Cookie header if required
  • Large payloads → Verify JSON formatting and escaping

Related Resources

Final Note

If the issue still persists, share:

  • cURL script
  • ZappySys configuration screenshots
  • Component used (SSIS / ODBC / Power BI / API Connector)