Skip to main content

Integration error codes (mpbx-integrations, mpbx-api-ops)

Raised by /api/v1/integrations/catalogue and /api/v1/integrations/installs.... Messages never contain a secret or a word of the other system's answer. Guide: Integrations.

CodeHTTPMeaningWhat to do
MPBX-INT-UNKNOWN-CONNECTOR404The connector key is not in this server's catalogue.Pick a key from GET /integrations/catalogue.
MPBX-INT-INVALID400A setting, secret, label or tool allow-list entry does not match the connector's fields.Fix the value named in the message.
MPBX-INT-ALREADY-INSTALLED409The company already has an install of this connector.Configure the existing install instead.
MPBX-INT-NOT-FOUND404No such install in this company.List the installs with GET /integrations/installs.
MPBX-INT-VERSION-MISMATCH412The install changed since it was read.Read it again and retry with the new ETag.
MPBX-INT-OAUTH-NOT-CONFIGURED400The server has no OAuth provider for this connector.The operator lists the provider in MPBX_INTEGRATIONS_OAUTH_FILE.
MPBX-INT-OAUTH-STATE400The sign-in's state is unknown, expired (10 minutes), already used or another company's.Press Connect again.
MPBX-INT-OAUTH-EXCHANGE400The provider refused the authorization code (bad, expired or replayed).Press Connect again.
MPBX-INT-OAUTH-NEEDS-RECONNECT409The provider refused the refresh token for good (revoked, expired, app removed).Press Reconnect on the install page.
MPBX-INT-OAUTH-UNAVAILABLE503The provider could not be reached or failed; the refresh is retried with backoff.Wait; check the provider's status.
MPBX-INT-OAUTH-NOT-PER-USER400The connector signs in once for the company; a user cannot connect their own account to it.Use the company sign-in (POST /integrations/installs/{id}/oauth/start, integrations:write).
MPBX-INT-OAUTH-NOT-CONNECTED404The install has no such OAuth connection.Connect it first.
MPBX-INT-CLICK-NOT-INSTALLEDdead letterA CRM click-to-call arrived for a connector the company has not installed.Install the connector, then retry the item in the delivery log.
MPBX-INT-CLICK-INVALIDdead letterThe post is not a usable click-to-call (no number, wrong event, wrong Bitrix24 application token).Check the widget or automation body and the install's application_token.
MPBX-INT-CLICK-UNKNOWN-AGENTdead letterThe CRM's agent maps to no single active PBX user (unknown e-mail, an e-mail shared by two users, or no user_map entry for the Bitrix24 user).Use the PBX user's e-mail in the CRM, or add the user to user_map (12=ann@example.com).
MPBX-INT-CLICK-REFUSEDdead letterThe PBX did not place the call (no extension, number not dialable by the user, call engine unavailable). The engine's code is in the server log.Place the call from the phone to see the reason; clicks are never retried (a late ring is worse than a failure).
MPBX-INT-DELIVERY-NOT-AN-ORDERconflictCall customer was asked for a conversation that is not a delivery order (another channel, or a thread that names no order).Open the order's conversation of the delivery channel.
MPBX-INT-DELIVERY-NO-LINEconflictThe order cannot be called: the platform gave no number (no_phone), its masked number expired (mask_expired), or the order is over and the platform closed the line (order_closed).Contact the customer through the platform's own app.
MPBX-INT-DELIVERY-ORDER-NOT-FOUNDnot_foundThe delivery platform does not know the order (cancelled and removed, or the install's credentials belong to another store).Check the store's credentials in the connector.
MPBX-INT-UPSTREAM503A console action of an install (the Google Chat space list or test message) was refused by the other system or timed out; the message carries its short code (auth_failed, channel_not_found, rate_limited, ...).Check the service account key and that the Chat app was added to the space.