Use Voyced with Zapier
Connect Voyced to a Zap with Webhooks by Zapier. Start in Sandbox and move to Live only after the Zap works.
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.
Check Zap access and history before Live
The token request contains the API secret and later steps use a bearer token. Keep the Zap in a controlled workspace, restrict editors and check what request and response data appears in task history. Never copy a full token response into another step unless that step needs the token.
Plan access can vary
Zapier availability for webhook actions can depend on your Zapier plan. Check your account before building the complete workflow.
Example: read call credit
1
Add a token request
Add a Webhooks by Zapier action and select a POST or Custom Request event.
| Field | Description |
|---|---|
URL | https://sandbox.voycedconnect.eu/v1/auth/token |
Headers | Accept: application/jsonContent-Type: application/json |
Body | {"api_key":"YOUR_SANDBOX_API_KEY","api_secret":"YOUR_SANDBOX_API_SECRET"} |
2
Test and find the token
Run the step. Use the returned data.access_token value in the next action.
3
Add the balance request
Add another Webhooks by Zapier action using GET.
| Field | Description |
|---|---|
URL | https://sandbox.voycedconnect.eu/v1/balance |
Header | Authorization: Bearer [token from step 1] |
Accept | application/json |
4
Use the result
Read data.call_credit_balance. Add a Filter step when you only want the Zap to continue below a chosen amount.
Move the Zap to Live
- Duplicate or pause the Sandbox Zap.
- Replace the base URL with
https://api.voycedconnect.eu/v1. - Replace the Sandbox key and secret with separate Live credentials.
- Run the token, connection-test and capabilities steps again.
- Enable the Live Zap only after all tests pass.
Polling, not instant events
The current read-only API is suited to scheduled checks and actions. Instant Voyced event triggers will be documented when public webhooks are available.