Errors

This section centralizes the error behavior for API Connector endpoints.

Error model

API responses use HTTP status codes and a structured error payload. For operational troubleshooting, review both the status code and the provider context returned by the endpoint.

Common HTTP status codes

Status	Meaning	Typical cause
400	Bad Request	Invalid input, missing required fields, or unsupported parameter values.
401	Unauthorized	Missing, invalid, or expired Google identity token.
403	Forbidden	Authenticated identity without permission to execute the operation.
404	Not Found	Resource does not exist or cannot be resolved for your principal.
409	Conflict	Request conflicts with current state (for example, duplicate or already processed transaction).
429	Too Many Requests	Throughput limits exceeded for the principal.
500	Internal Server Error	Unexpected API Connector internal failure.
502/503/504	Upstream/Availability errors	Carrier or external dependency unavailable or timing out.

Operational recommendations

1. Validate request schema before sending calls in production.
2. Implement idempotency and controlled retry logic for transient failures.
3. Capture request identifiers in your logs to accelerate reconciliation and support workflows.
4. Alert on repeated 401/403 responses to detect IAM misconfiguration early.