Exa API
numSentences body parameter removal on POST /contents
Deprecated, no dateSubscribe to Exa APIShare
Exa API has deprecated the body parameter numSentences on the POST /contents endpoint without a shutdown date. Calls continuing to use this parameter will eventually fail once it is removed.
Calls it hits
POST /contentsbody parameter numSentences
What to use instead of these calls
Use highlights.maxCharacters instead.
In Exa API's words
maxCharacters for highlights: now the preferred way to control highlight length. numSentences and highlightsPerUrl are deprecated.
Facts
- API
- Exa API
api.exa.ai - Kind
- Parameter removal
- Announced
- February 2, 2026
- 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 numSentences 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 7
-
/research*Endpoint removal Stopped working -
POST /searchBehaviour change 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 /findSimilarEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.