Mentions

Requires account:read. Type-ahead over the platforms whose mentions are plain handles — X, Bluesky and Mastodon. Insert the returned handle after an @ in the post body and the platform resolves it at publish time; no id or markup is needed. The workspace's own directory answers first (its channels, handles remembered from earlier picks, people from the inbox, @handles in its posts), then the network: Bluesky's and Mastodon's own search, or for X an exact lookup of the whole query as a handle — X has no affordable name search, so on X a partial name only matches people the workspace already knows. Mastodon handles are returned qualified (user@instance). A Mastodon search runs against that account's own instance on its token, so two channels can return different results for the same query. Channels on other platforms are a 400 — Threads has no handle search, and LinkedIn mentions are structured nodes (use /mentions/linkedin). A Bluesky or Mastodon search that can't reach the network is a 502; an X lookup that fails or is out of budget just adds nothing.

Requires account:read. Turns the vanity name in a company URL (linkedin.com/company/orbitwrite → orbitwrite) into the urn:li:organization:… a LinkedIn mention node needs, asking LinkedIn with the named channel's token. The lookup is exact-match: a slug LinkedIn has no company for returns { "organization": null }, which is an answer and not an error — fall back to a numeric company URL or a URN the author supplies. A 502 means the lookup itself failed and the slug is still unknown; do not write a mention on the strength of one.

Requires account:read. LinkedIn mentions are structured URN nodes rather than plain handles, so build the mention from the returned id — there is nothing useful to type.

Four directories, distinguished by source. channel results are the workspace's own connected LinkedIn accounts, substring-matched. recent results are people and companies the workspace has already @mentioned in LinkedIn posts written through Orbitwrite (never imported ones), most-used first. follower results are members who follow one of the workspace's Pages, found by LinkedIn's People Typeahead: from a Page channel, that Page's followers; from a personal channel, the followers of up to two of the workspace's Pages. Only Pages whose connection granted r_organization_followers are asked (reconnect a Page connected before Orbitwrite asked for it), and only for queries in LinkedIn's grammar — letters plus at most one space and single ', - or ., at least 3 characters (6 with a space or dot). LinkedIn returns only followers who allow mentions. A lookup result is a company LinkedIn itself returned, and appears only when the whole query is a well-formed vanity name — their keyword company search is restricted to selected developers, so exact match on the vanity name is the only search available to us. Typing orbit will not find orbitwrite; typing orbitwrite will. Queries shorter than 3 characters never reach LinkedIn, and a client should debounce: the quota behind this is per application per day, not per caller, so every prefix you send costs everyone.

A LinkedIn that can't be reached costs you the follower and lookup candidates, not the request. LinkedIn offers no search over a member's connections, so a personal channel finds people only through the workspace's own channels, its earlier mentions and its Pages' followers.

Requires post:create. Adds a handle to the workspace's mention directory, or counts another use of one already there, so GET /mentions/handles offers it to everyone in the workspace from then on without asking the network. accountId is the X, Bluesky or Mastodon channel the mention is written from: it names the network, and a bare Mastodon username is qualified with that channel's instance. The handle must be well-formed for the network (a leading @ is ignored). displayName and avatarUrl are optional, and when omitted the stored ones are kept; avatarUrl must be https.