Company
Fetch a company profile by URL, slug, or numeric id, and its sub-resources.
Usage
curviate core company <id> [flags]Examples
curviate core company acmecorp
curviate core company https://www.linkedin.com/company/acmecorpArguments
| Argument | Required | Description |
|---|---|---|
id | yes | Company identifier (URL, slug, or native id). |
Flags
| Flag | Type | Required | Description |
|---|---|---|---|
--sections | string | no | Not supported on company commands; a usage error (exit 2) if supplied. |
Also accepts these global flags: --api-key, --profile, --account, --base-url, --timeout, --json, --fields, --verbose, --beta.
Before you start: an API key and a connected LinkedIn account, see the Quickstart.
Commands
| Command | Description |
|---|---|
curviate core company employees | List people who currently work at the company. |
curviate core company posts | List the company's posts. |
curviate core company jobs | List the company's open job postings. |
curviate core company invitable-followers | List the account's 1st-degree connections who are eligible to be invited to follow the company page. This is the read that seeds curviate core company follow-invite. Items carry no name or headline (a wire limitation), so hydrate a candidate via curviate core profile <id> before deciding who to invite. invite_token is always returned as base64 (the raw value can carry binary bytes unsafe to print). |
curviate core company follow-invite | Invite the account's 1st-degree connections to follow the administered company page. Write, admin-gated (the account must administer the page with invite rights). Pass the AC... member ids from curviate core company invitable-followers, one --invitee per invitee. All-or-nothing: for an all-valid request you get one outcome per invitee, in request order (invited/already_invited/ineligible/not_found); if any invitee id is invalid the whole request rejects with a 404, not a partial result. Re-inviting an already-invited member is a safe no-op (the same invitation id, never a duplicate). |
curviate core company reply | Reply to a company-inbox conversation, as the page (write, admin-gated: the account must administer the page). Takes the normal 2-... chat id from curviate core company chats; the endpoint resolves the page mailbox internally from the company id. Reply-only, this cannot start a new conversation on the page's behalf. See also: curviate core company chats (the read that returns the chat id) and curviate core message send (the personal equivalent). |
curviate core company managed | List the company pages the connected account administers. An empty result is valid, the account administers no pages. |
curviate core company followers | List a company page's followers, newest first. Admin-gated: the account must administer the page (see curviate core company managed). |
curviate core company chats | List the conversations in a company page's admin message inbox, newest-activity-first. Admin-gated. Beta. |
curviate core company chat | Retrieve one conversation from a company page's admin inbox. Admin-gated. |
curviate core company messages | List a company-inbox conversation's messages, newest first. Admin-gated. |
curviate core company message | Retrieve one message from a company-inbox conversation. Admin-gated. See also: curviate core company reply (send). |
curviate core company search-chats | Search or filter a company page's admin inbox. Exactly one mode per call: free-text <query>, --topic, or --unread; mutually exclusive, enforced server-side. Admin-gated. Beta. |
Exit codes: the exit code table.