Use Voyced with Make
Use Make's HTTP app to request a token and call Voyced API endpoints.
Protect your Voyced access from the first test
Your API credentials can access customer information and the functions allowed for that key. Treat the API secret like a password. Store it only in protected server-side settings or a trusted secret store.
- Never put an API key, API secret or bearer token in public code, browser JavaScript, screenshots, URLs or support messages.
- Keep Sandbox and Live credentials separate. Give each integration only the permissions it needs.
- Rotate the secret and disable the old key at once when exposure is suspected.
Protect values outside the scenario
Use Make's protected credential or keychain storage where the HTTP module supports it. Do not place real credentials in a scenario you may export or share. Review scenario history and access before enabling Live.
Example scenario
Scheduler or manual run
→HTTP: request token
→HTTP: read balance
→Filter or action
1
Request a Sandbox token
| Field | Description |
|---|---|
Module | HTTP: Make a request |
Method | POST |
URL | https://sandbox.voycedconnect.eu/v1/auth/token |
Body type | JSON |
Body | {"api_key":"YOUR_SANDBOX_API_KEY","api_secret":"YOUR_SANDBOX_API_SECRET"} |
2
Read the balance
| Field | Description |
|---|---|
Module | HTTP: Make a request |
Method | GET |
URL | https://sandbox.voycedconnect.eu/v1/balance |
Header | Authorization: Bearer {{data.access_token}} |
Response | Parse as JSON |
3
Add error handling
Handle 401 by requesting a new token. Back off on 429. Record the Voyced request ID for other errors.
Move the scenario to Live
- Clone the tested scenario.
- Change the base URL to
https://api.voycedconnect.eu/v1. - Replace all Sandbox credentials with separate Live credentials.
- Run the Live connection test and capabilities request.
- Enable scheduling after the Live test succeeds.
Make HTTP setup worksheetReference values for the token and balance modules
Download