# cURL to Postman conversion

**URL:** <https://community.postman.com/t/curl-to-postman-conversion/1815>\
**Category:** Help Hub\
**Created:** [June 6, 2018, 8:18pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815 "2018-06-06T20:18:07Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![omena](https://avatars.discourse-cdn.com/v4/letter/o/a698b9/32.png) [@omena](https://community.postman.com/u/omena)\
**Post date:** [June 6, 2018, 8:18pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/1 "2018-06-06T20:18:07Z")

</div>

I’m currently attempting to convert some commands to Postman but I get the error message:  
Error while importing Curl: TypeError: Invalid format for cURL.

the commands are:

1. curl --user admin:password --insecure --data ‘duration=300&capture\_profile\_name=Display/Video (Podcast/Vodcast/EchoPlayer). Optimized for quality/full motion video&description=test-description’ --url [https://192.168.61.10:8443/capture/new\_capture](https://192.168.61.10:8443/capture/new_capture)

2. curl --user admin:password --insecure --data ‘’ --url [https://192.168.61.10:8443/capture/record](https://192.168.61.10:8443/capture/record)

any ideas?

thanks

---

<div class="post-metadata">

**Author:** ![tmccann](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/tmccann/32/3550_2.png) [@tmccann](https://community.postman.com/u/tmccann)\
**Post date:** [June 7, 2018, 1:28pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/2 "2018-06-07T13:28:13Z")

</div>

@omena I am just trying some of your examples locally. I dont do imports like this often so I am not really familiar with this but I am seeing errors when importing.

> error: unknown option `–user’
> 
> error: unknown option `–insecure’

What is interesting is if I do something like this:

> curl --url [https://192.168.61.10:8443/capture/record](https://192.168.61.10:8443/capture/record)

It works fine. Seems to be an issue with other parameters, even though they are valid.  
May need some dev input here. @kunagpal any thoughts?

---

<div class="post-metadata">

**Author:** ![omena](https://avatars.discourse-cdn.com/v4/letter/o/a698b9/32.png) [@omena](https://community.postman.com/u/omena)\
**Post date:** [June 7, 2018, 1:49pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/3 "2018-06-07T13:49:38Z")

</div>

@tmccann

 ![image](https://us1.discourse-cdn.com/getpostman/original/3X/0/a/0a212e0db625fbd036d09920b42043014dacbdbc.png)

So, I used the other section to build the commands, but it doesn’t show the authorization on the URL.  
Is this how it’s supposed to work?

---

<div class="post-metadata">

**Author:** ![tmccann](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/tmccann/32/3550_2.png) [@tmccann](https://community.postman.com/u/tmccann)\
**Post date:** [June 7, 2018, 1:56pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/4 "2018-06-07T13:56:39Z")

</div>

@omena I think you are on the right path here.

Try importing something like this:

> curl -X POST   
> [https://192.168.61.10:8443/capture/record](https://192.168.61.10:8443/capture/record)   
> -H ‘Authorization: Basic YWRtaW46cGFzc3dvcmQ=’   
> -H ‘Cache-Control: no-cache’   
> -H ‘Content-Type: application/x-www-form-urlencoded’   
> -d ‘duration=3000&capture\_profile\_name=Display%2FVideo%20(Podcast%2FVodcast%2FEchoPlayer).%20Optimized%20for%20quality%2Ffull%20motion%20video&description=test-description’

---

<div class="post-metadata">

**Author:** ![omena](https://avatars.discourse-cdn.com/v4/letter/o/a698b9/32.png) [@omena](https://community.postman.com/u/omena)\
**Post date:** [June 7, 2018, 2:00pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/5 "2018-06-07T14:00:36Z")

</div>

I was also told that I need to use wireshark to get the HTTP command…  
Is this correct?

---

<div class="post-metadata">

**Author:** ![tmccann](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/tmccann/32/3550_2.png) [@tmccann](https://community.postman.com/u/tmccann)\
**Post date:** [June 7, 2018, 2:18pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/6 "2018-06-07T14:18:41Z")

</div>

I am not sure how that plays into the cURL calls but if you needed to intercept some sort of traffic to get your data then I can see why.

However that does seem to be a bit odd you would not know some of the basic details to be able to make your API calls successfully unless this is a black box to you?

If you are using Wireshark to capture the calls and export, then import into Postman then I could see that being the issue with why the calls are not importing correctly. Could be an issue with the formatting of Wireshark’s calls.  
You may need to use Wireshark to capture the calls and then manually model them in Postman but in the end you should be able to do the exact same call.

---

<div class="post-metadata">

**Author:** ![omena](https://avatars.discourse-cdn.com/v4/letter/o/a698b9/32.png) [@omena](https://community.postman.com/u/omena)\
**Post date:** [June 7, 2018, 2:37pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/7 "2018-06-07T14:37:47Z")

</div>

So, I have a device, ECHO360, that needs to be controlled with a crestron processor over the network.

the API calls for:  
CURL Example: curl --user admin:password --insecure --data ‘duration=300&capture\_profile\_name=Display/Video (Podcast/Vodcast/EchoPlayer). Optimized for quality/full motion video&description=test-description’ --url [https://192.168.61.10:8443/capture/new\_capture](https://192.168.61.10:8443/capture/new_capture)

I was advised to convert it to POSTMAN then, send the command and see what is on wireshark…

I still don’t quite unsdertant the entire concept…

---

<div class="post-metadata">

**Author:** ![tmccann](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/tmccann/32/3550_2.png) [@tmccann](https://community.postman.com/u/tmccann)\
**Post date:** [June 7, 2018, 3:03pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/8 "2018-06-07T15:03:58Z")

</div>

Wow! yeah I am not sure what to make of that either.  
Sounds like some crazy stuff.

Postman should be able to do what you need for making the API calls. As for monitoring the network and viewing the calls that would be out of my league.

Happy to help you get some of these calls going though. I assume when you issue some of these calls via API that you can see some sort of response from the ECHO360 or see a change if you have access to it?

---

<div class="post-metadata">

**Author:** ![omena](https://avatars.discourse-cdn.com/v4/letter/o/a698b9/32.png) [@omena](https://community.postman.com/u/omena)\
**Post date:** [June 7, 2018, 3:10pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/9 "2018-06-07T15:10:35Z")

</div>

@tmccann  
yes, I believe so.

---

<div class="post-metadata">

**Author:** ![tmccann](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/tmccann/32/3550_2.png) [@tmccann](https://community.postman.com/u/tmccann)\
**Post date:** [June 7, 2018, 4:52pm UTC](https://community.postman.com/t/curl-to-postman-conversion/1815/10 "2018-06-07T16:52:50Z")

</div>

Ok thats great. then you know if your calls were successful or not when you make them.  
That will be useful when it comes to determining if the calls are correct or not.
