Troubleshooting 403 Errors with Communications Microservice API

If you encounter a 403 error when calling the Communications Microservice API, this typically indicates an API Gateway authentication issue. The most common cause is an API key configuration problem in the usage plan. Common Causes Missing or incorrect API key API stage accidentally removed from the usage plan Usage plan throttling limits exceeded Resolution Steps Verify that your API key is correctly configured in your requests Check that your API stage is properly included in the usage plan Confirm your usage plan settings: Rate limit (typically 10,000 requests) Burst limit (typically 10,000 requests) Daily quota (typically 10,000 requests) Prevention When making changes to API Gateway configurations: Always verify usage plan settings before removing any API stages Document any changes made to API Gateway configurations Use Infrastructure as Code (IaC) when possible to manage API Gateway resources If you continue to experience 403 errors after checking these items, please contact support for further assistance.