CloudConvert has a Sandbox for development purposes. It directs me to a base url of https://api.sandbox.cloudconvert.com (image below). I would like to use this in testing so I don’t waste ClouConvert credits.
I generated a new API key specific for the sanbox but I don’t see where I can enter this so that make.com directs to the sandbox as opposed to the production site of CloudConvert.
Any ideas?
According to CloudConvert API, to call the Sandbox API, you need to use the endpoint beginning with https://api.sandbox.cloudconvert.com/
.
However, to do this, you CANNOT use the CloudConvert modules, because they are using the LIVE endpoint https://api.cloudconvert.com/
So, we are treating the sandbox integration as “not implemented” in Make.
For services that have not been implemented in Make, you can use the HTTP “Make an API Key Request” module.
If the external service has a Developer API Reference/Documentation then you should be able to integrate the endpoints in Make using the app’s universal module (Make an API call) or generic HTTP “Make a request” module.
You can also suggest for it to be made in the Idea exchange. Don’t forget to search for it first, just in case someone already suggested it, so that you don’t end up creating a duplicate.

If you need assistance in setting up the generic HTTP module, please provide additional information about what you have tried with regards to the external service’s Developer API Reference – how you are setting the connection up, a link to the endpoint are you trying to connect to, and what errors you are encountering.
You can also complete this brand new course/tutorial in the Make Academy on how to use external APIs — API calls with HTTP modules
- API and Endpoints
- Header and body
- Multipart/form-data
- OAuth 2.0
samliew – request private consultation
Join the Make Fans Discord server to chat with other makers!
2 Likes