Vapi
/logs* endpoint removal
Stopped workingSubscribe to VapiShare
Calls to /logs* on Vapi stopped working on September 29, 2025.
Calls it hits
/logs*
What to use instead of these calls
Use call artifacts, monitoring plans and end-of-call reports instead.
In Vapi's words
Replace /logs endpoint usage with call artifacts, monitoring plans, and end-of-call reports for comprehensive logging.
Facts
- API
- Vapi
api.vapi.ai - Kind
- Endpoint removal
- Announced
- February 17, 2025
- Takes effect
- September 29, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Vapi's own pages
Questions
When does this change take effect?
Calls to /logs* on Vapi stopped working on September 29, 2025.
What happens to calls after September 29, 2025?
They have failed since September 29, 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.
More from Vapi 2
-
/knowledge-base*Endpoint removal Stopped working -
/test-suite*Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.