Ingest Endpoint Failover

For continuous production workloads, we provide an ingestion endpoint with automatic failover: ingest.amberflo.io.

This endpoint is backed by a multi-regional deployment, so that if our main endpoint is having problems, you'll still be able to send us your meter events.

To fully benefit from using this endpoint, we recommend you set up a retry policy on your API client. Here is a general guideline:

• Use a backoff strategy and make sure a couple of atempts happen after 20 seconds from the first failure;
• Retry for HTTP status codes: 429 and 5xx.

If you use one of our SDKs, we've updated them to use this endpoint with a suitable retry policy. The SDK versions using the new endpoint start at:

• 3.1.0 for Python
• 2.6.0 for TypeScript / JavaScript
• 2.1.0 for Go
• 2.1.0 for Java