POST /contents → endpoint removal
Exa API
Deprecated, no date
The body parameter livecrawl on POST /contents is deprecated without a shutdown date. Calls continuing to use the parameter will eventually fail once it is removed. The change affects requests sent to api.exa.ai using this parameter.
Calls it hits
POST /contentsbody parameter livecrawl
What to use instead of these calls
Use maxAgeHours with livecrawlTimeout instead.
In Exa API's words
Historical entry: the livecrawl string parameter is now deprecated. For new integrations, use maxAgeHours with livecrawlTimeout.
Facts
- API
- Exa API
api.exa.ai - Kind
- Endpoint removal
- Announced
- June 7, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Exa API's own pages
Questions
When does this change take effect?
Exa API deprecated POST /contents, body parameter livecrawl without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Exa API has not given a shutdown date yet.
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 Exa API 6
-
/research*Endpoint removal Stopped working -
/research*Endpoint removal Stopped working -
POST /searchBehaviour change Stopped working -
POST /searchBehaviour change Stopped working -
POST /searchBehaviour change Stopped working -
POST /searchBehaviour change Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.