How can we help?

HTTP status codes are standardized responses used by web services and APIs. You may encounter these codes while using Polyosync, troubleshooting an integration, or reviewing technical error information. The meaning of a status code is general. Its specific cause depends on the request and the service that returned it. 400 — Bad Request The server could not process the request because the submitted information was invalid or did not meet the expected requirements. Check the input and request configuration. 401 — Unauthorized The request lacks valid authentication. Check whether the relevant session or integration authorization is valid. 403 — Forbidden The server understood the request but does not permit the requested action. Review the applicable permissions and access restrictions. 404 — Not Found The requested resource could not be found. Verify the resource reference, URL, and workspace context. 429 — Too Many Requests The service is limiting requests because an applicable rate threshold has been reached. Avoid repeatedly submitting the same request. Review any provider-specific guidance on when requests may be retried. 500 — Internal Server Error The service encountered an unexpected condition while processing the request. This does not, by itself, identify the underlying cause. 502 — Bad Gateway A service acting as a gateway received an invalid response from an upstream service. This may indicate a problem involving a dependent service. 503 — Service Unavailable The service is temporarily unable to handle the request. Possible causes include temporary unavailability, overload, or maintenance. 504 — Gateway Timeout A gateway did not receive a timely response from an upstream service. This may occur when a dependent operation takes too long. Important distinctions A 401 error does not necessarily mean your account has been deleted. A 403 error does not necessarily mean the platform is malfunctioning; access may be intentionally restricted. A 404 error does not prove that a resource never existed. A 500-series error does not automatically identify Polyosync as the failing component; the response may originate from an external service. What should I do? Record the exact status code, the operation that produced it, the approximate time, and the affected service. If the operation could have modified business data, verify its outcome before retrying. When to contact Support Provide the status code together with the full context. A numeric code alone is rarely sufficient to determine the root cause.