Skip to main content
POST https://xquik.com/api/v1/x/account-connection-challenges/{id}/submit
Free. This endpoint does not consume credits.
This takes a dashboard session, or a key with the Connect X accounts permission. Turn it on at dashboard.xquik.com/api-keys. Full access doesn’t include it. A key without it gets 403 x_account_connect_permission_required. OAuth tokens and MCP tools get 403 session_required.
Use this endpoint after Connect X Account returns 202 Email Code Required. Submit the one-time code from the account email inbox before expiresAt.
This endpoint cannot reopen an expired, failed, completed, or replaced challenge. After 409, 410, or 422, start Connect X Account again for a new account. For an existing account, use Re-authenticate X Account. Call it with the current password and any required TOTP secret key.

Continue the pending login

Use the returned challenge ID

Keep the id from the 202 response. Submit the inbox code to that challenge. The challenge belongs to the same pending login attempt.

Enter the account email code

Use the one-time code X sent to the account email inbox. Xquik strips spaces before submission. 123 456 and 123456 work the same way.

Handle another code prompt

If X asks for a new email code, this endpoint returns 202 again. Keep the same flow open and submit the next inbox code before expiresAt.

Start over when stale

410 means the code expired. 409 means the challenge already completed, failed, or expired. 409 can also mean a newer challenge replaced it. Start Connect X Account again for a new account. Or use Re-authenticate X Account for an existing account.
The dashboard follows the same flow. It keeps the pending row open and asks for the email code. It accepts a new 202 prompt if X asks again. After the 201 response, it refreshes the account list.

Headers

Path parameters

Body

Response

201 Created

202 Email code required

The connection still needs a valid email code. Submit the new code to the same endpoint.

400 Invalid input

Missing email_code, invalid JSON, or a code outside the accepted length.

401 Unauthenticated

{ "error": "unauthenticated", "message": "Missing or invalid API key" } Missing or invalid API key.

404 Not found

{ "error": "connection_challenge_not_found", "message": "Connection challenge not found." } The challenge ID does not exist or does not belong to the authenticated user.

409 Conflict

The challenge already completed, failed, or expired, or a newer challenge replaced it.

410 Expired

Start a new account connection to receive a fresh challenge.

422 Login failed

X rejected the code or account login state. Start a new connection if the account requires fresh credentials.

429 Rate limit exceeded

{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } Wait for the Retry-After header before retrying.

503 Service unavailable

Retry after a short delay.
Related. Connect X Account starts the challenge. List X Accounts verifies the account after connection.

Response examples

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "not_found", "message": "Resource not found." }
  • 409 { "error": "connection_challenge_inactive", "message": "Connection challenge is no longer active." }
  • 410 { "error": "connection_challenge_expired", "message": "Verification code expired. Start again." }
  • 422 { "error": "login_failed", "message": "Login failed. Check credentials and try again." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Retry later." }
  • 503 { "error": "service_unavailable", "message": "Service temporarily unavailable. Try again later." }