Exa API
endCrawlDate body parameter behaviour change on POST /search
Stopped workingSubscribe to Exa APIShare
On April 15, 2026, the body parameter endCrawlDate stopped working on POST /search. Calls that rely on endCrawlDate now fail to apply the filter, as Exa API announced it is silently ignored from April 15.
Calls it hits
POST /searchbody parameter endCrawlDate
What to use instead of these calls
Remove startCrawlDate and endCrawlDate, and use the published date filters instead.
In Exa API's words
startCrawlDate / endCrawlDate (deprecated request parameters): silently ignored from April 15.
Facts
- API
- Exa API
api.exa.ai - Kind
- Behaviour change
- Announced
- April 1, 2026
- Takes effect
- April 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Exa API's own pages
Questions
When does this change take effect?
Calls to POST /search, body parameter endCrawlDate on Exa API stopped working on April 15, 2026.
What happens to calls after April 15, 2026?
They have failed since April 15, 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.
More from Exa API 7
-
/research*Endpoint removal Stopped working -
POST /searchBehaviour change Stopped working -
No date
POST /searchParameter removal Deprecated, no date -
No date
POST /contentsParameter removal Deprecated, no date -
No date
POST /contentsParameter removal Deprecated, no date -
No date
POST /contentsParameter removal Deprecated, no date -
No date
POST /findSimilarEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.