Symptomsresponse": { "statusCode": 403, "status": "Forbidden", "body": "{\"errors\":{\"class\":\"InvalidInput\",\"invalid_data\":\"Call must be present\"}}",Applies ToSignal APIResolutionYou could either delay their requests a bit to account for t...
Symptoms403 error occurs on only a handful of callsApplies ToTransactions APIResolutionCheck the transaction ID associated with the error to see if a transcript is associated with the call. If not, you should expect to see a 403. If there is a transc...
SymptomsA large amount of Signals were reported to our Partner integrations as occurring at the same time, on the same day. Instead of when they actually converted.Applies ToSignal API, Signal File Upload, IntegrationsResolutionIf you want to send I...
SymptomsNo calls appear in the "current_calls" bracketsApplies ToCalls in Progress APIResolutionCheck whether a valid destination number and calling phone number combination are used.The API can only return calls that Invoca routes to the end destina...
Symptoms403 error when sending a GET requestNo data within the request Applies ToCalls in Progress APIResolutionCheck with the support team to ensure the Calls in Progress flags are enabled for your account CauseCalls in Progress feature flags ma...
SymptomsWhen applying Revenue along with a Signal using the Signal API, the request updates the Signal and gets a 200 response code, but the Revenue value is not applied.Applies ToSignal API requests including the `revenue` parameter. Example request...
