Hi there, I just bought this in hopes that it lets us get Azure & Gemini API's but then realized it says ChatGPT, can you confirm if you also support these other leading endpoints to troubleshoot/make fully working? is this kinda like Postman meets the simple ux of webhook.site?
A: Hi! 👋 In NativeRest you can make requests to many popular APIs that support HTTP. The advantage for ChatGPT is that NativeRest has a built-in token and you don't need to enter your own. But this does not limit you in any way to use the API of other AI models (you will need your token). NativeRest does not have a folder created on first run with ready-made request templates. This is a good idea...
Hi. I'm not a programmer, just too curious. 1. Could this app convert code from JavaScript to Python, Java, C#, PHP, and Swift, and vice versa? 2. If it could, can it be for tier 1 or use AI (ChatGPT)? Thanks!
A: Hi! 👋 NativeRest is a REST Client, like the popular tool called Postman. It is intended for creating, testing and debugging API. NativeRest does not convert code.
You need to click the "AI" ✨ button on the top left to create an AI request. Then in the "Body" of the message, enter your request (prompt) to the AI model. Click the "Send" button. On the right, you will see the response generated by the AI model. It looks very similar to a regular REST request.
looking forward to updated documentation; the hardest thing in picking an alternative to (the defacto standard, like postman) is the lack of youtube videos and thorough docs online which AI can parse through easily.
Thanks for the addition. New training videos are also planned.
Q: Pre-request script feature as in Postman (to sign requests)?
Hello, so I bought Nativerest and I'm trying to use it to build an integration to a service (https://developers.3commas.io/quick-start/signing-a-request-using-hmac-sha256). However, for this I need to generate a custom HMAC signature for each request based on my secret key.
With Postman I have the pre-request feature that can do this. However, how can I do this in NativeRest?
I can of course do this in the Mac terminal, but it's just quite a pain to work like this whenever you make requests.
A: Hello! 👋 Thank you for purchasing NativeRest. ✨ Currently, NativeRest only has a sha256 hashing function with one parameter. It won't work in this case. I looked at the API on your link and understand what is required. In a few days, I will add the hmac-sha256 function with two parameters to NativeRest. I'll reply to you here additionally as soon as it appears in NativeRest. 🙌
Hi! Yes, I have great news! Right now the new version of NativeRest 2.6.2 is available. I just finished the necessary release notes and wanted to write to you. Now you need to use the new hmac.sha256 function to fill in the Signature header. This function has 2 parameters: Data, Key. In the first - payload, and in the second - secret. Signature: {{hmac.sha256({{payload}},{{secret}})}}
This is a continuation of my answer: In my example, 2 parameters are declared payload and secret, in which the values are written: payload = /public/api/ver1/users/change_mode?mode=paper secret = NhqPtmdSJYdKjVHj... In my opinion, variables are more convenient, but it is not necessary to use them.
Awesome, thank you! I made a GET request successfully using your new feature! I will let you know if I have further issues.
But have a comment about the Mac app. I don't think the shortcuts are very logical. 1. I wonder why for the duplication, why do you have to add shift to every keyboard shortcut? 2. also when you tap around to select words, you use very weird keys for the Mac.
Continued... Mac uses option/alt+arrow left/right to jump between words. You use command+shift+arrow left/right to select the whole line. And most importantly, you use shift+alt+arrow left/right to select a word. This is not how it works in Native Rest. So it feels quite unintuitive when working on a Mac. I hope this can be fixed in the Mac version. Check app on Mac to see (TextEdit, browsers etc)
Finally I wonder if it's possible to get this work in a way where I don't have to specify the endpoint twice. Because right now I have to specify the endpoint path in the variables. And continuously update this, it could be nice if it would simply take the endpoint path from the URL bar. Then I could insert that variable in the signature generation.
In addition, whenever I work on a new request, I have to go back and update the workspace variable to use a different payload for every request since the payload is not part of the request itself, but part of the workspace variables. So I can't really keep multiple requests open in a working state, it seems, because the payload variable I have to set each time - it is not saved with the request.
To clarify the last part. "Because the payload variable I have to set each time - it is not saved with the request." This is because the payload variable is set as a "workspace variable" in your example so it applies to all the requests that you have created in NativeRest so it is continuously overwritten and breaks other requests. Not good. How can I avoid this so "payload" save with the requests
And I just realized that this is actually a big issue. Because sometimes the payload is not just the path, but naturally needs to include a body as well. You have to enter lots twice. So again, it would be nice to also be able to reference this from the Body section directly. Couldn't you make it possible to variable to the Body section.
Example: Body: { "account_id": 12345, "pair": "USDT_BTC", "position": { "type": "buy" } } I have to repeat this - how about making a variable? payload: /public/api/ver1/smart_trade{"account_id":12345,"pair":"USDT_BTC","position":{"type":"buy"}}
Hi! 👋 Thank you for these suggestions and comments. 🙌 1. I'll take another look at the standard hotkeys for working with text in macOS and try to improve this in NativeRest. 2. Please try the variable {{request.uri.path}} – it returns the path (/public/api/ver1/users/change_mode). For example: Signature: {{hmac.sha256({{request.uri.path}}?mode=paper,{{secret}})}}
Would you like a new {{request.body}} variable to get the request body for use in headers? If you prefer, you can write to me at support@nativesoft.com. The message length limit here is too small for our discussion. 😆
Q: Persona Verified
Can you please have founder persona verified for credibilty?
uhaleks
Sep 23, 2025A: Hi! 👋 This is Alex, the founder of NativeRest. What would you like to know more about the founder? 😊
Share NativeRest
Q: Azure
Hi there, I just bought this in hopes that it lets us get Azure & Gemini API's but then realized it says ChatGPT, can you confirm if you also support these other leading endpoints to troubleshoot/make fully working? is this kinda like Postman meets the simple ux of webhook.site?
uhaleks
Sep 9, 2025A: Hi! 👋 In NativeRest you can make requests to many popular APIs that support HTTP. The advantage for ChatGPT is that NativeRest has a built-in token and you don't need to enter your own. But this does not limit you in any way to use the API of other AI models (you will need your token). NativeRest does not have a folder created on first run with ready-made request templates. This is a good idea...
Share NativeRest
Q: Covert Code
Hi. I'm not a programmer, just too curious.
1. Could this app convert code from JavaScript to Python, Java, C#, PHP, and Swift, and vice versa?
2. If it could, can it be for tier 1 or use AI (ChatGPT)?
Thanks!
uhaleks
Jul 28, 2025A: Hi! 👋 NativeRest is a REST Client, like the popular tool called Postman. It is intended for creating, testing and debugging API. NativeRest does not convert code.
Share NativeRest
Q: How to use AI Request?
I bought the tool, and it really is lighter than Postman.
But I was in doubt about how to use the AI Request feature. I didn't find anything in the documentation.
uhaleks
Jul 20, 2025A: Hi! 👋
Thank you for purchasing NativeRest. 🤗
You need to click the "AI" ✨ button on the top left to create an AI request. Then in the "Body" of the message, enter your request (prompt) to the AI model. Click the "Send" button. On the right, you will see the response generated by the AI model. It looks very similar to a regular REST request.
I will add a description of AI requests to the...
Share NativeRest
Verified purchaser
looking forward to updated documentation; the hardest thing in picking an alternative to (the defacto standard, like postman) is the lack of youtube videos and thorough docs online which AI can parse through easily.
Thanks for the addition. New training videos are also planned.
Q: Pre-request script feature as in Postman (to sign requests)?
Hello, so I bought Nativerest and I'm trying to use it to build an integration to a service (https://developers.3commas.io/quick-start/signing-a-request-using-hmac-sha256). However, for this I need to generate a custom HMAC signature for each request based on my secret key.
With Postman I have the pre-request feature that can do this. However, how can I do this in NativeRest?
I can of course do this in the Mac terminal, but it's just quite a pain to work like this whenever you make requests.
uhaleks
Jun 26, 2025A: Hello! 👋
Thank you for purchasing NativeRest. ✨
Currently, NativeRest only has a sha256 hashing function with one parameter. It won't work in this case. I looked at the API on your link and understand what is required. In a few days, I will add the hmac-sha256 function with two parameters to NativeRest. I'll reply to you here additionally as soon as it appears in NativeRest. 🙌
Share NativeRest
Verified purchaser
Awesome man! Thank you and much appreciated! Really looking forward to your update!
Verified purchaser
Hi, I'm curious if there's any updates on this?
Hi! Yes, I have great news!
Right now the new version of NativeRest 2.6.2 is available. I just finished the necessary release notes and wanted to write to you.
Now you need to use the new hmac.sha256 function to fill in the Signature header.
This function has 2 parameters: Data, Key.
In the first - payload, and in the second - secret.
Signature: {{hmac.sha256({{payload}},{{secret}})}}
This is a continuation of my answer:
In my example, 2 parameters are declared payload and secret, in which the values are written:
payload = /public/api/ver1/users/change_mode?mode=paper
secret = NhqPtmdSJYdKjVHj...
In my opinion, variables are more convenient, but it is not necessary to use them.
See an example of using hmac.sha256 in NativeRest in this screenshot:
https://nativesoft.com/static/images/using-hmac-sha256-function.png
Verified purchaser
Awesome, thank you! I made a GET request successfully using your new feature!
I will let you know if I have further issues.
But have a comment about the Mac app. I don't think the shortcuts are very logical.
1. I wonder why for the duplication, why do you have to add shift to every keyboard shortcut?
2. also when you tap around to select words, you use very weird keys for the Mac.
Verified purchaser
Continued... Mac uses option/alt+arrow left/right to jump between words. You use command+shift+arrow left/right to select the whole line. And most importantly, you use shift+alt+arrow left/right to select a word. This is not how it works in Native Rest. So it feels quite unintuitive when working on a Mac. I hope this can be fixed in the Mac version. Check app on Mac to see (TextEdit, browsers etc)
Verified purchaser
Finally I wonder if it's possible to get this work in a way where I don't have to specify the endpoint twice. Because right now I have to specify the endpoint path in the variables. And continuously update this, it could be nice if it would simply take the endpoint path from the URL bar. Then I could insert that variable in the signature generation.
Verified purchaser
In addition, whenever I work on a new request, I have to go back and update the workspace variable to use a different payload for every request since the payload is not part of the request itself, but part of the workspace variables. So I can't really keep multiple requests open in a working state, it seems, because the payload variable I have to set each time - it is not saved with the request.
Verified purchaser
To clarify the last part. "Because the payload variable I have to set each time - it is not saved with the request." This is because the payload variable is set as a "workspace variable" in your example so it applies to all the requests that you have created in NativeRest so it is continuously overwritten and breaks other requests. Not good. How can I avoid this so "payload" save with the requests
Verified purchaser
And I just realized that this is actually a big issue. Because sometimes the payload is not just the path, but naturally needs to include a body as well. You have to enter lots twice. So again, it would be nice to also be able to reference this from the Body section directly. Couldn't you make it possible to variable to the Body section.
Verified purchaser
Example:
Body: {
"account_id": 12345,
"pair": "USDT_BTC",
"position": {
"type": "buy"
}
}
I have to repeat this - how about making a variable?
payload: /public/api/ver1/smart_trade{"account_id":12345,"pair":"USDT_BTC","position":{"type":"buy"}}
Hi! 👋 Thank you for these suggestions and comments. 🙌
1. I'll take another look at the standard hotkeys for working with text in macOS and try to improve this in NativeRest.
2. Please try the variable {{request.uri.path}} – it returns the path (/public/api/ver1/users/change_mode). For example:
Signature: {{hmac.sha256({{request.uri.path}}?mode=paper,{{secret}})}}
Would you like a new {{request.body}} variable to get the request body for use in headers?
If you prefer, you can write to me at support@nativesoft.com. The message length limit here is too small for our discussion. 😆
Verified purchaser
Also you cannot put the cursor in a string and then shift-click before or after this to select everything in between.