pub.highlight.io stops working
Highlight.io
Stopped working
Highlight.io services on pub.highlight.io will stop working on February 28, 2026. The provider is deprecating services and moving its infrastructure and services to LaunchDarkly. Any calls directed to pub.highlight.io will fail after that day.
What to use instead of these calls
Replace the Highlight SDK with LaunchDarkly Observability by initializing the LaunchDarkly SDK with a client-side ID along with the Observability and SessionReplay plugins. The move requires more than changing an identifier, as it needs a LaunchDarkly account, a new SDK key, and a LaunchDarkly plan.
Moving to LaunchDarkly Observability needs a LaunchDarkly account, a new SDK key and a LaunchDarkly plan.
In Highlight.io's words
Highlight.io will be deprecating services on **February 28, 2026** and moving 100% of our infrastructure and services to LaunchDarkly.
Facts
- API
- Highlight.io
pub.highlight.io - Kind
- Endpoint removal
- Announced
- November 13, 2025
- Takes effect
- February 28, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Highlight.io's own pages
Questions
When does this change take effect?
Calls to these calls on Highlight.io stopped working on February 28, 2026.
What happens to calls after February 28, 2026?
They have failed since February 28, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.