Aircall API
GET /v1/calls/{id}/realtime_transcription endpoint removal
Deprecated, no dateSubscribe to Aircall APIShare
Aircall API deprecated GET /v1/calls/{id}/realtime_transcription without giving a shutdown date yet.
Calls it hits
GET /v1/calls/{id}/realtime_transcription
What to use instead of these calls
Call GET /v1/calls/{call_id}/transcription, which also serves the realtime mode at the end of the call.
In Aircall API's words
The realtime_transcription endpoint is in its deprecation phase. As the deadline is approaching, update/migrate to transcription endpoint as soon as possible, to avoid service disruption.
Facts
- API
- Aircall API
api.aircall.io - Kind
- Endpoint removal
- Announced
- February 20, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Aircall API's own pages
Questions
When does this change take effect?
Aircall API deprecated GET /v1/calls/{id}/realtime_transcription without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Aircall 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 Aircall API 6
-
GET /v1/campaigns/{id}/contact_imports/{id}/rowsRemoval Stopped working -
POST /v1/campaigns/{id}/contact_imports/{id}/promoteRemoval Stopped working -
No date
GET /v1/usersEndpoint removal Deprecated, no date -
No date
GET /v1/users/{id}Endpoint removal Deprecated, no date -
No date
POST /v1/usersEndpoint removal Deprecated, no date -
No date
PUT /v1/users/{id}Endpoint 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.