How can we help?

External API and webhook integrations can fail for several reasons, including authentication problems, incorrect configuration, unsupported operations, network issues, and provider-side restrictions. Identifying the specific failure is the most effective way to resolve the problem. Common API integration problems 1. Incorrect endpoint URL. The configured URL may be invalid or may reference the wrong API environment. 2. Invalid credentials. An API key, token, or other credential may have expired, been revoked, or been entered incorrectly. 3. Insufficient permissions. The external account may not have access to the requested resource or operation. 4. Invalid request format. The API may reject missing parameters, incorrect data types, or unsupported request structures. 5. Rate limiting. The provider may temporarily reject requests after usage limits are exceeded. 6. External service unavailability. The provider may be experiencing an outage or degraded performance. 7. Unsupported integration functionality. The requested operation may not be available through the configured integration. Common webhook problems 1. Incorrect destination URL. 2. Invalid or missing authentication. 3. Unsupported event subscription. 4. Unexpected payload structure. 5. Endpoint response errors. 6. Delivery timeouts. 7. Duplicate event delivery. 8. Changes to the provider's webhook configuration. How to troubleshoot an external API Step 1: Identify the failing operation. Determine exactly what the integration was attempting to do. Step 2: Check the endpoint. Verify the URL, HTTP method, and required parameters. Step 3: Review authentication. Confirm that the credentials are valid and have the necessary permissions. Step 4: Inspect the response. Review the HTTP status code and any available error details. Step 5: Verify the request format. Compare the request with the provider's API documentation. Step 6: Check provider availability. Determine whether the external service is experiencing an incident. Step 7: Test with controlled data. Use a minimal request that does not affect important production records. Step 8: Review the related Polyosync operation. Where execution details are available, check the relevant result or error information. How to troubleshoot a webhook Step 1: Confirm that the source event occurred. Step 2: Verify the configured destination URL. Step 3: Check the provider's webhook delivery history. Step 4: Inspect the HTTP response status. Step 5: Verify authentication or signature validation. Step 6: Review the payload format. Step 7: Confirm that the receiving system supports the event. Step 8: Test the complete event flow again. What does HTTP 401 mean? The request may be missing valid authentication. What does HTTP 403 mean? The credentials may be valid, but access to the requested operation is not permitted. What does HTTP 429 mean? The external service may be enforcing a rate limit. What does HTTP 500 or 503 mean? The external service may be experiencing an internal problem or temporary unavailability. Can a webhook be delivered successfully without completing the intended business operation? Yes. Receipt of an event and successful completion of downstream processing are separate outcomes. What should I provide when contacting Polyosync Support? Include: 1. The external service name. 2. The affected workspace. 3. The intended API or webhook operation. 4. The approximate time of the failure. 5. The HTTP status code, if available. 6. The relevant error message. 7. Whether the integration worked previously. 8. Any recent configuration changes. Do not include passwords, API keys, bearer tokens, signing secrets, or other confidential credentials. Recommended approach Troubleshoot one operation at a time. Avoid changing multiple settings simultaneously, as this can make the underlying problem more difficult to identify.