Contribute to the directory

You can improve a directory record whether or not you work at the organization. Before you start, check the company’s website and name so you’re working on the right record.

Suggest a correction

You don’t need to manage the organization, but you do need to be signed in. Corrections are submitted through the API today. Corrections are reviewed, and they never directly edit a profile. See Authentication for tokens.

Find the profile’s listingId in GET /v2/directory/entity/{slug}/profile-experience, then send:

curl -X POST "https://api.sureshake.com/v2/directory/entity/$LISTING_ID/corrections" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "field_correction",
    "field": "websiteUrl",
    "proposedValue": "https://example.com",
    "note": "The company moved to this domain.",
    "evidenceUrl": "https://example.com/about"
  }'

Include a proposedValue, a note, or both. A source in evidenceUrl is optional but helps the reviewer. Send one issue per request.

Common field values are identity.displayName, overview, location, category, websiteUrl, and socialLinks.

Being accepted doesn’t change the page straight away. After acceptance, a profile manager must publish the correction before the public profile changes. If you can’t use the API, contact us with the page and your source.

Report a duplicate

Use the same endpoint, and name the record that should remain:

{
  "kind": "duplicate_report",
  "proposedCanonicalListingId": "LISTING_ID_TO_KEEP",
  "note": "Same company, same domain."
}

If the report is accepted, the duplicate redirects to the record you named, and its source and version history are preserved. You can’t merge records yourself.

How facts earn their labels

Information an organization supplies, public-source research, and classifications inferred by Sureshake have different origins, and profiles keep them distinct. Sending a link doesn’t make a fact verified. See Reference profiles.