---
title: "Contribute to the directory"
description: "Maintain your organization's record, correct a public fact, or report a duplicate."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sureshake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

| Your goal                                  | Where to go                                                                                                         |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| Manage your company's public presence      | [Claim your profile](/directory/claim-your-profile/), then [publish your company](/directory/publish-your-company/) |
| Choose what shows on your firm's portfolio | [Manage your portfolio](/directory/portfolio/)                                                                      |
| Correct a public fact on someone's profile | [Suggest a correction](#suggest-a-correction)                                                                       |
| Report two records for one company         | [Report a duplicate](#report-a-duplicate)                                                                           |

## 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](/developers/authentication/) for tokens.

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

```bash
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](https://www.sureshake.com/contact) with the page and your source.

## Report a duplicate

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

```json
{
  "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.

> **Caution**
>
> Use public information only. Don't include private financial records, personal
> contact details, credentials, or links to confidential documents. Use
> [sharing](/founders/sharing/) for private material.

## 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](/directory/reference-profiles/).

Source: https://docs.sureshake.com/directory/contribute/index.mdx