If you're on the Basic or Professional plan, you can simply go to your management console to add a new member. With our Auto-Flex team policy, you won't be billed for the new users until either your next billing cycle for monthly plans or on a recurring quarterly basis for annual plans. During this monthly or quarterly period, you will also have the ability to assess your needs and add more licenses or remove them before the billing date. For additional information, please refer to this article in the Postman Learning Center. If you're on the Enterprise plan, contact us at sa...@postman.com and we'll help you add more licenses.
i am testing an api in postman that works fine. i am exporting it using the functionality in postman. the export language is curl. i am pasting it in the bubble api connector but it does not work. is there a process to easily transfer apis from postman to bubble?
Yes, the signature comes from postman. i try it in another tool and it works. but if i try it in bubble it does not work. below you can see the raw text, the api connector and the other tool so you can compare. i literealy copy and paste the same. i do not know what else to change to make it work!
The problem is not the authorization key since i copy it directly from postman and it works in req bin. For some reason the exact same code does not work in bubble.
I have figured out already how to generate the authorization key but i first need to make the call work
Hi Jaime i am struggling with the exact same issue on Bubble, the call in postman works and gives me a working signature that doesnt work on Bubble. I am copying the exact same body on postman and on Bubble.
I also faced the same issue, but the trick was I implemented both the methods that were stated earlier in the stack.First I turned off the postman proxy as shown in below image.
I was not able to make any calls from postman to docker container running Couchbase Server. Very frustrating. Turns out I had proxy setting configured to some aws instance which has been long deleted.
If you have active proxy in your system then make sure Global Proxy Configuration and Use System Proxy are turned off. To do this go to Postman preferences > Proxy. You can also try sending a request in postman without typing localhost (e.g. :8080/send)
But for the past few days, I've been trying to do the same action either via postman or via lunix command line by doing a curl -X POST https:... and nothing works. As you said, maybe it's an authentication problem?
Great example on getting up and running on MLE requests quickly in postman. Especially insightful was the fact that for encryption we needed the Server Encryption Certificate instead of the client certificate if generated via CSR.
the great thing about the Xwiki API is that you really can navigate down the tree in postman just by clicking links. So starting from :port/xwiki/rest/wikis/ you can just start clicking links until you reach :port/xwiki/rest/wikis/xwiki/spaces/Dashboard/spaces/API_Test_1/pages/WebHome/attachments.
I'm not sure what the missing piece. I've double-checked my bearer authorization and I know that's accurate. I don't think I'm giving postman enough information to parse the csv file. I defined the course_id as a variable... maybe I need to add something under parameters?