--- title: "Solve a checkpoint verification challenge" method: POST path: "/v1/auth/checkpoint/solve" tags: ["Auth"] --- # Solve a checkpoint verification challenge `POST /v1/auth/checkpoint/solve` ## Request - Base URL: `https://api.curviate.com` - URL: `https://api.curviate.com/v1/auth/checkpoint/solve` - Auth: HTTP bearer Resolves the pending verification challenge for account_id: a code, OTP/2FA, a contract_selection id, or TRY_ANOTHER_WAY to switch method. A chained challenge returns another 202. ## Request body - object - `account_id` string, required: The account whose connect/reconnect is mid-flight (returned with the 202 checkpoint_required response). - `code` string, required: The OTP / 2FA verification code. Special value TRY_ANOTHER_WAY switches the challenge type (e.g. in-app -> 2FA). ## Response `201` The challenge was resolved; the account is now connected. - object - `object` 'account': Response type discriminator. - `account_id` string - `status` 'active' | 'reconnect_needed' | 'restricted' | 'disconnected' - `seat_id` string, nullable: The seat this account occupies (canonical, supersedes the deprecated attached_seat_id). - `attached_seat_id` string, nullable: Deprecated, use seat_id (same value). Removed at the GA /v1 cutover. - `external_id` string, nullable: Your own id for this account's end user, as set on connect or PATCH. Null when none. Not unique. - `recovered` boolean: Present and true only when this connect reactivated an account you had previously disconnected, instead of opening a brand-new one. Absent on a normal connect. The account keeps its original id, and its status reflects its real observed state, which may need a reconnect. - `connection_location` object: Where LinkedIn sees this account connecting from. country: the configured country (ISO 3166-1 alpha-2), the one the account is set to use. current_country: the country of the connection in use right now; it differs from country only after a fallback, which can happen only when strict is false. mode: auto (a managed connection in country) or custom (your own proxy). strict: true when the account never connects from another country, null when unknown. Each field is null until known; an account connected through ip or your own proxy may show null until the next background refresh. Change it with PATCH /v1/accounts/{account_id} (country), or by reconnecting with country. - `country` string, nullable: Configured country (ISO 3166-1 alpha-2). - `current_country` string, nullable: Country of the connection in use right now. - `mode` 'auto' | 'custom' | 'null', nullable: auto: managed connection. custom: your own proxy. - `strict` boolean, nullable: true: never connects from another country. - `previous_country` string: Present only when this connect landed on an account you already had and changed its configured country (to another one, to unknown with ip, or to your own proxy). It names the country before. - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite. - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture. - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail). - `hint` object, required - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy. - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text. - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each. - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload. ## Other responses - `202`: A chained challenge follows (e.g. OTP -> 2FA). Solve the next code at the same account's checkpoint/solve. - `403`: ACCOUNT_RESTRICTED. LinkedIn has restricted this account (not a wrong code and not our subscription gate). Sign in to LinkedIn to see what it needs, resolve it there, then reconnect. - `404`: No pending checkpoint for this account. - `409`: CHECKPOINT_EXPIRED or CHECKPOINT_ALREADY_RESOLVED: restart the connection. ACCOUNT_ALREADY_LINKED: the LinkedIn identity is already connected; it names your own account_id when you own it, otherwise it is not one you can manage here. CONNECTION_IN_PROGRESS: another connection attempt for this identity is open; wait for it to finish or expire. - `413`: Payload too large, the request body exceeds the size limit. - `422`: The submitted code was incorrect, or the challenge type is unsupported. CONNECTION_LOCATION_UNAVAILABLE: the connect completed onto an account you already had, and the location you sent could not be applied (no connection free in that country, or it was an ip); the account stays connected, the body carries its actual connection_location, and PATCH /v1/accounts/{account_id} with country moves it. - `429`: Too many failed attempts, restart the connection. - `500`: Internal error. - `502`: A temporary error occurred. Please try again. - `503`: Service unavailable. - `504`: Gateway timeout. --- [API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)