Messenger error 2018390: Invalid call id
Last verified against Meta for Developers - Messenger Platform error codes
The call id provided in the api call is invalidWhat error 2018390 means
Code 2018390 means the call_id in your Messenger calling request does not identify a call the platform recognizes: "The call id provided in the api call is invalid." Meta's guidance is to "confirm that the call ID matches the one received in the incoming call webhook."
In the consumer-to-business flow, a person calls the Page, your app receives a connect webhook on the calls field, and you answer by POSTing to /{page-id}/calls with action set to accept and that webhook's call_id. The ID is the only link between the event and your response, so anything that alters, swaps or invents it ends here.
The call-specific state errors have their own codes: 2018395 for a call that failed and 2018396 for one that ended. When the ID is real but the request goes to the wrong Page, Meta lists separate codes for that too. So 2018390 points first at the identifier itself.
What it looks like
{
"error": {
"message": "(#2018390) The call id provided in the api call is invalid",
"type": "OAuthException",
"code": 2018390,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Copying the wrong field from the connect webhook into call_id.
- Type or encoding changes: the ID converted to a number, trimmed or re-encoded.
- Using an ID from a test or staging environment against production.
- Mixing up IDs when several calls arrive at once.
How to fix Messenger error 2018390
- 1Log the raw connect webhook and the outgoing request side by side and compare the IDs.
- 2Store call_id as a string exactly as received.
- 3Key in-flight calls by call_id so concurrent calls cannot be swapped.
- 4Send the request to the Page ID that received the webhook.
How to stop it recurring
Pass the webhook's call ID straight through: no transformation, string type end to end, and a per-call state object keyed by it. If calling events go through a queue, check that the queue does not reorder or merge payloads. The webhook debugging guide covers delivery problems on the inbound side.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
- 2018391: Invalid connection parameterThe connection parameter cannot be empty when calling accept call api
- 2018392: Invalid SDP parameterThe SDP parameter provided in the accept call api is not valid
- 2018395: Cannot join failed callYou cannot join a call that has failed
- 2018396: Cannot join ended callYou cannot join a call that has ended
Error 2018390 - quick answers
What does Messenger error 2018390 mean?
Code 2018390 means the call_id in your Messenger calling request does not identify a call the platform recognizes: "The call id provided in the api call is invalid." Meta's guidance is to "confirm that the call ID matches the one received in the incoming call webhook." In the consumer-to-business flow, a person calls the Page, your app receives a connect webhook on the calls field, and you answer by POSTing to /{page
How do I fix Messenger error 2018390?
1. Log the raw connect webhook and the outgoing request side by side and compare the IDs. 2. Store call_id as a string exactly as received. 3. Key in-flight calls by call_id so concurrent calls cannot be swapped. 4. Send the request to the Page ID that received the webhook.
Should I retry after error 2018390?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.