linkedin

Set the sender's approval setting from the extension

Writes the sender's LinkedIn approval setting (run_mode), the same setting the sender's LinkedIn page writes, so the two surfaces have one source of truth rather than two that drift. An empty body reads the state without changing it. With a lease nonce, the answer also says whether this browser holds the lease, and which browser does when it does not.

post/linkedin/agent/state/

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/state/
  • Auth: API key in header X-API-Key

Request body

lease_noncestring nullable

This browser's lease identity. When given, lease_granted in the answer says whether this browser holds the lease; when absent it is always true.

Response

Successful Response

account_mismatchboolean required
approvals_waitinginteger

How many of this sender's LinkedIn steps wait for a person on Oneprofile's Tasks page, less those a paused sequence or paused contact holds; the side panel offers Approve tasks while any do.

attempts_enabledboolean

Whether a build that reports attempts (attempts:v1) reports a run cut off without an error from LinkedIn to /actions/{id}/attempts/ and runs the step again only on the answer. The same switch as resume_enabled.

checkpointboolean required
config_versioninteger required

The version of the selector and pacing config this server serves. A browser running any other version, older or newer, fetches the config again.

lease_grantedboolean required
lease_holder_labelstring nullable

When lease_granted is false, what the browser holding the lease calls itself (for example 'Chrome on macOS'); null when that is not known.

poll_after_secondsinteger required

How long to wait before the next check-in: the account's own time between steps, never more, and never so long the browser stops reading as active. At most 15 seconds while work is about to run (the time between steps is running out, a step may start now, or one is running with more behind it), so a missed wake-up costs seconds rather than a whole interval.

queued_countinteger required
resume_enabledboolean

Whether a build that resumes steps (resume:v1) may resume one that stopped without an error from LinkedIn. Off, a stopped step fails for a person to retry, as it did before; the grant and the saved results stay on either way.

run_mode'manual' | 'auto' required

Whether a person approves a sender's LinkedIn steps before they run, or they run on their own.

The sender's own LinkedIn setting, kept on the sender beside their email modes so the approval queue reads one home for both. The absence of one (SenderProfileDTO.linkedin_approval_mode is None) reads as MANUAL: nothing runs on somebody's LinkedIn unattended until they have said so. The approval queue still tells "never set" apart from "chose manual", which is the level its settings surfaces name.

running_claim'renewed' | 'lost' nullable

For a check-in that named a running step: renewed while that claim is still this browser's, lost once it is not (settled, rejected, lapsed while the browser was gone, or taken back from a step whose running_wait outlasted every ceiling), and the browser then stops the step before it changes anything more. Null for a check-in that named none.

unpaced_waitingboolean

A step that waits for no gap between steps (one the Oneprofile team fired to test the sender) could be handed out now: ask for it alone (unmetered_only) without waiting out this browser's own gap.

usage_resets_atstring date-time nullable

When today's counts in usage start over: 00:00 in the sender's timezone. Older servers leave it out, and a client then reads the next UTC midnight.

Changes

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