The June API stops working
June API
Stopped working
Requests sent to api.june.so fail after August 8, 2025. The provider announced that the June standalone product will wind down on that day, permanently ending support for these requests.
What to use instead of these calls
Send events to Amplitude instead, using Amplitude's HTTP V2 API or its SDKs, following the June SDK migration guide. Moving analytics to Amplitude or another product requires a product decision.
June shut down: moving its analytics to Amplitude or another product is a product decision.
In June API's words
As part of this transition, the June standalone product will wind down on August 8, 2025.
Facts
- API
- June API
api.june.so - Kind
- Endpoint removal
- Announced
- July 8, 2025
- Takes effect
- August 8, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against June API's own pages
Questions
When does this change take effect?
Calls to these calls on June API stopped working on August 8, 2025.
What happens to calls after August 8, 2025?
They have failed since August 8, 2025.
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.