Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fendpoints.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fendpoints.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Deprecation of legacy log ingestion endpoints

**Published**: July 1, 2025

**Effective**: September 30, 2026

## Deprecation notice[​](#deprecation-notice "Direct link to Deprecation notice")

As part of our long-term platform modernization effort, Coralogix will permanently deprecate legacy data ingestion endpoints on September 30, 2026.

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[​](#why-this-is-happening "Direct link to 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.<br /><!-- -->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[​](#whats-affected "Direct link to What’s affected")

The following legacy ingestion endpoints will be permanently disabled.

### Deprecated public endpoints[​](#deprecated-public-endpoints "Direct link to Deprecated public endpoints")

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

### Deprecated private endpoints[​](#deprecated-private-endpoints "Direct link to 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[​](#what-you-need-to-do "Direct link to What you need to do")

### Update your ingestion endpoints[​](#update-your-ingestion-endpoints "Direct link to 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>/logs/v1/bulk`    |
| `api.<coralogix domain>/logs/rest/singles` | `ingress.<coralogix domain>/logs/v1/singles` |
| `api.<coralogix domain>/logs/rest/bulk`    | `ingress.<coralogix domain>/logs/v1/bulk`    |

### Update authentication headers[​](#update-authentication-headers "Direct link to 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)[​](#update-ip-whitelisting-if-applicable "Direct link to 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 September 30, 2026?[​](#what-will-happen-after-september-30-2026 "Direct link to What will happen after September 30, 2026?")

* 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[​](#additional-resources "Direct link to Additional resources")

|                                            |                                                                                                                                                            |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Use this guide to update your integrations | [Everything you need to know about the new Coralogix endpoints](https://coralogix.com/blog/everything-you-need-to-know-about-the-new-coralogix-endpoints/) |
| Coralogix Endpoints                        | [Coralogix Endpoints](https://docs-docusaurus.kinsta.page/integrations/coralogix-endpoints/.md)                                                            |

## Need help?[​](#need-help "Direct link to Need help?")

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