Deprecation of Legacy Log Ingestion Endpoints

Published: July 1, 2025

Effective: December 12, 2025

Deprecation notice

As part of our long-term platform modernization effort, Coralogix will permanently deprecate legacy data ingestion endpoints on December 12, 2025.

These endpoints were originally built around a single global load balancer. Over the past three years, we’ve transitioned to region-specific endpoints and infrastructure to improve availability, observability, and security.

Action is required to ensure uninterrupted log ingestion.

Why this is happening

Legacy ingestion traffic was routed through a shared global load balancer, which made it harder to isolate failures and scale efficiently.
By moving to region-specific ingestion domains and dedicated infrastructure, we now offer:

Domain isolation to reduce the impact of failures
Improved production observability and monitoring
Unified naming conventions (e.g., us1.coralogix.com, eu1.coralogix.com)
Streamlined endpoint and IP management

What’s affected

The following legacy ingestion endpoints will be permanently disabled.

Deprecated public endpoints

api.<coralogix domain>/api/v1/logs
api.<coralogix domain>/logs/rest/singles
api.<coralogix domain>/logs/rest/bulk

Deprecated private endpoints

private-link.<coralogix domain>
private-link-api.<coralogix domain>

These endpoints may be used in:

Log shipper configurations (e.g., OpenTelemetry, Filebeat, FluentBit)
Kubernetes manifests or Helm values files
AWS Lambda, ECS, or container environment variables
CI/CD pipelines or automation scripts

Check your configurations for these patterns to identify usage.

What you need to do

Update your ingestion endpoints

Replace legacy URLs with the new regional format as follows:
Legacy URL New URL
api.<coralogix domain>/api/v1/logs ingress.<coralogix domain>
api.<coralogix domain>/logs/rest/singles ingress.<coralogix domain>/logs/v1/singles
api.<coralogix domain>/logs/rest/bulk ingress.<coralogix domain>/logs/v1/singles

Note: The new singles endpoint replaces both the singles and bulk legacy endpoints.
Refer to the full regional endpoint list to find the correct replacement for your environment.

Update authentication headers

Replace the legacy header format:

Old: token: <your_api_key>
New: Authorization: Bearer <cx_api_key>

Ensure all tools and scripts reflect this change.

Update IP whitelisting (if applicable)

If your infrastructure restricts outbound access by IP, update to the new CIDR ranges.

Examples:

US1 (Ohio): 18.97.138.64/26
EU1 (Ireland): 18.97.198.64/26
AP2 (Singapore): 18.99.41.64/26

What will happen after December 12, 2025?

Legacy ingestion endpoints will be permanently shut down
Any tools using them will fail to ship logs, possibly without warning
Data may be lost if configurations are not updated in time
Platform monitoring and visibility may be affected

Additional resources

Update your integrations using this guide: Everything you need to know about the new Coralogix endpoints.

Need help?

Reach out via our 24/7 in-app support or contact your Technical Account Manager directly. We’re here to help.

Legacy URL	New URL
`api.<coralogix domain>/api/v1/logs`	`ingress.<coralogix domain>`
`api.<coralogix domain>/logs/rest/singles`	`ingress.<coralogix domain>/logs/v1/singles`
`api.<coralogix domain>/logs/rest/bulk`	`ingress.<coralogix domain>/logs/v1/singles`