Troubleshooting checklist
Resolve common Business API authentication, validation, permission, and delivery failures.
Start with the HTTP status and the operation name. The same checks work for SDK and cURL callers.
Diagnose request failures
401 Unauthorized
- Confirm the environment variable contains the complete
ov_key. - Confirm the SDK was configured before the operation ran.
- Confirm cURL sends
x-api-keyexactly, including the hyphen. - Rotate the key if it was exposed or revoked.
403 Forbidden
Check the required permission on the operation reference. A valid key without reviews write permission cannot create an owner response. A key for one project cannot access another project.
400 Bad Request
Compare the body with the generated SDK type. Common causes include missing question fields, an invalid enum, fewer than two entries in a question's answers.options, a validityMinutes value outside 1 through 43200, or a knowledge-base item that provides neither supported field.
Empty lists
Remove filters and verify scope
An empty collection can mean the project has no matching data or that your filters exclude every row. Remove optional filters, request page 1, and verify the project ID before opening a support request.
Webhook delivery
Check the receiver and destination
Use the webhook guide to confirm the destination URL, subscribed topics, and portal configuration. Keep your receiver available over HTTPS and return a successful response after it accepts the event.