Chrome extension routes
The routes the Adapt Leads Chrome extension uses for its build, its heartbeat and arming, and what they return.
The extension signs in with the same token as the app and calls these routes. The download is behind sign-in on purpose.
| Method and path | Purpose |
|---|---|
GET /market/extension/latest |
The current build and whether the caller is behind it. Returns 200 with an empty answer when no build is published yet |
GET /market/extension/download |
The zip. 404 if no build is published, 503 if the file is missing on the server |
POST /market/extension/heartbeat |
The extension says it is alive |
GET /market/extension/status |
Seen in the last 10 minutes? Armed? Which version? |
POST /market/extension/arm |
Arm agent work for a bounded window |
POST /market/extension/disarm |
Stop it |
Heartbeat body
All fields are optional: linkedin_reachable, linkedin_signed_in, mode, panel_open, note_char_limit (200 or 300), note_char_limit_detected_at, linkedin_public_id. The extension's version is read from a request header.
Arming
POST /market/extension/arm takes {"minutes": 60, "campaign_ids": ["..."]}. minutes is 5 to 720 (default 60). campaign_ids is optional, up to 50. While armed, queued work may run without the person at the keyboard. Arming does not start a campaign: a campaign still has to be active. The connector tool linkedin_status reads the same status.