directory

Apply proposed contact-to-company links

Set the company on contacts that have none, from their email domain.

Applies the proposal GET /directory/contact-company-links returns, or the part of it named by contact_ids. Read that first: a company carrying a consumer domain such as gmail.com claims every personal address in the organization, and this endpoint cannot tell that apart from a real firm.

The proposal is recomputed here rather than carried over from the GET, so contact_ids chooses contacts, not companies: if the company that won a contested domain is archived in between, the runner-up wins this call. The applied list names the company each contact actually got, so compare it against what you reviewed.

Keep the applied list the response returns. It names every contact this call gave a company to, and nothing else records which contacts had none beforehand — so it is what a bad run has to be reversed from.

A contact that already has a company is never touched, whether it had one all along or gained one between the read and this call. Safe to repeat — a second call with nothing left to do links nothing.

post/directory/contact-company-links

Request

  • Base URL: https://api.cogram.com/v1
  • URL: https://api.cogram.com/v1/directory/contact-company-links
  • Auth: HTTP bearer

Request body

contact_idsstring[] nullable

Apply only the proposed links for these contacts. Omit to apply every one. Ids that are not currently proposed are ignored, so a list built from an earlier GET cannot link a contact whose company has since been set. The 1000-id ceiling bounds the request body, not the write: omitting the field still applies the whole proposal.

Response

Successful Response

linkedinteger required

Contacts given a company by this call.

skippedinteger required

Proposed links this call did not write, because the contact gained a company between the read and the write. An existing company is never overwritten.

Changes

No recorded changes to this operation across all 2 revisions of this API.