linkedin

Claim the next permitted action

Hands out one action, if and only if the governor allows it: the account is active and not at a checkpoint, no other step is running, the last one was handed out long enough ago, the kind still has daily headroom, the rolling weekly invitation ceiling is not reached, and credit covers it. A step the Oneprofile team fired to test the sender goes first and waits for none of those but the first two; asked with unmetered_only, only such a step is handed out. A step whose browser stopped reporting is resolved first. When nothing is handed out the response says why, which is what lets the panel distinguish an empty queue from a paced one: in_flight, pacing (with when to ask again), daily_cap or weekly_cap (only while claimable work waits behind them), checkpoint, not_connected, insufficient_credits, or null for an empty queue.

post/linkedin/agent/actions/next/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/linkedin/agent/actions/next/
  • Auth: API key in header X-API-Key

Request body

checkpointboolean nullable

True when LinkedIn is challenging the account; no work is handed out while it stands. False clears it; null leaves it untouched.

claim_request_idstring nullable

This browser's name for this ask, kept until the answer is saved. Asked again under the same name, because the first answer never arrived, the browser gets the step it was handed rather than a second one beside it. Older builds leave it out.

extension_versionstring
lease_noncestring required

This browser's lease identity; only the holder is handed work.

member_urnstring nullable

Who the browser is currently signed in as, for the mismatch guard.

running_action_idstring uuid nullable

The step this browser is running right now, sent on the check-ins it makes while it runs; with running_claimed_at it keeps that step's claim from lapsing under a browser still working on it, including one waking from sleep. Null between steps.

running_claimed_atstring date-time nullable

When the running step was claimed, as the claim handed it out.

running_phase'claimed' | 'navigated' | 'dispatched' | 'committing' | 'committed'

How far a build that resumes says a running step got, on each check-in.

claimed: handed over, nothing done. navigated: on the page. dispatched: the step's own work started. committing: a press that changes LinkedIn was granted and is under way. committed: it was made. Information for the team and for the next look; the grant, not the phase, is what says something may have happened.

supported_kindsstring[] nullable

The step kinds this build can run, and the capabilities it has beyond them (such as profile_view:read_relationship). Nothing is handed to a browser that it cannot run. Leave it out (an older build) and the browser runs the kinds that existed before builds said. Sent on every check-in: a check-in without it reads as such a build.

timezonestring nullable

The browser's IANA timezone (Intl.DateTimeFormat().resolvedOptions().timeZone). It fills the sender's timezone when the sender has none: their daily limits reset at its midnight and sequences send in its hours. A timezone the sender has is never moved by it. Taken only from the browser driving the account.

unmetered_onlyboolean

Hand out only a step that waits for no gap between steps (one the Oneprofile team fired to test the sender), or nothing: the ask a build makes inside its own gap when the check-in says one is waiting (unpaced_waiting). Older builds leave it out.

Response

Successful Response

deferred_reasonstring nullable required
earliest_next_action_atstring date-time nullable required
queued_countinteger required

Changes

No recorded changes to this operation across all 1 revision of this API.