API

Troubleshooting

Find out what actually reached WiseParts.

Every Voice API request is recorded with the payload as received, the response, the status and how long it took. The history is per account, newest first, so you are always looking at your own traffic.

A request that fails authentication is never recorded, because the account could not be identified. If nothing appears at all, check the token first.

Two ways to see it

For a quick look, navigate to Integrations > Logs and expand an entry to read its full request and response — see Integration Logs. That screen covers every integration, so filter by type to isolate the Voice ones.

For automated checks, call List request history. It returns the same Voice entries as JSON, so your own monitoring can poll for failures instead of someone watching a screen.

Narrowing to the failure

On the API, set scopeOnlyErrors to return only entries whose status is error, scopeBetween to limit the range to from,to dates, and search_term to search across the request, response and status — the call id you sent is a good search term when you are chasing one specific call.

Sensitive fields are scrubbed from the recorded payload, so what you read back is not byte-for-byte what you sent.

List request history

Every Voice API request is recorded with its payload, response, status and duration.