How to Convert a Postman Request to cURL / HTTP Syntax (For ZappySys Troubleshooting)

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

:pushpin: Overview

If your API request works in Postman but fails in ZappySys (SSIS PowerPack / ODBC Driver / API Connector), the fastest way to troubleshoot is to share your request as a cURL command.

This helps us:

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

:compass: When Should You Use This?

Use this guide when:

  • You see: “Works in Postman but not in ZappySys”
  • Support asks for request details
  • You want to replicate Postman configuration exactly

:white_check_mark: 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

:counterclockwise_arrows_button: 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

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

:broom: Step 3: Clean Up the cURL (Recommended)

Postman often includes extra headers. Clean them before sharing:

:cross_mark: Remove unnecessary headers:

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

:white_check_mark: Keep only important headers:

  • Authorization
  • Content-Type
  • Any required custom headers

:check_mark: Example (Clean cURL)

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

:locked_with_key: Step 4: Share the cURL Script

Provide your cURL when:

  • Creating a support ticket
  • Replying to ZappySys support

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

:page_facing_up: Step 5: (Optional) Convert to Raw HTTP Format

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

POST /data HTTP/1.1Host: api.example.comAuthorization: Bearer <token>Content-Type: application/json{"name":"test"}

:gear: 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

:star: Best Practice (Highly Recommended)

Whenever reporting:

:red_exclamation_mark: “Working in Postman but not in ZappySys”

:backhand_index_pointing_right: Always include your cURL script

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

:brain: 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

:link: Related Resources

:memo: Final Note

If the issue still persists, share:

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