---
title: "Claim your profile"
description: "Take over the reference profile for an organization you represent, and what evidence you need to do it."
---

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

# Claim your profile

If your organization has a [reference profile](/directory/reference-profiles/) you can claim it, so that you control its public facts and can file reports and share them. A claim covers organizations. Reference profiles for people can't be claimed this way.

## What you need

| Evidence                 | What you provide                                                          | What happens                   |
| ------------------------ | ------------------------------------------------------------------------- | ------------------------------ |
| **Work email match**     | Sign in with a verified email on the organization's website domain.       | The claim is approved at once. |
| **Supporting evidence**  | At least one URL, plus at least 20 characters on your role and authority. | A person reviews the claim.    |
| **Review without links** | At least 20 characters on your role and authority.                        | A person reviews the claim.    |

Personal mailbox providers, such as Gmail, never count as a domain match. If your email domain doesn't match, your claim goes to review.

## Make a claim

> **Caution**
>
> The **Claim this profile** link on company pages can't complete a claim at the
> moment, and you may see a page-not-found error. Use one of the routes below.

**Through the API.** Send a signed-in request to the claim endpoint. See [Authentication](/developers/authentication/) for tokens. The company's ID is `entity.id` in `GET /v2/entities/public/{slug}`.

```bash
curl -X POST "https://api.sureshake.com/v2/entities/$ENTITY_ID/claim" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"evidence": {"method": "authenticated_email_domain"}}'
```

For a reviewed claim, use one of these as `evidence`:

```json
{
  "method": "entity_evidence",
  "evidenceUrls": ["https://example.com/team"],
  "notes": "I am the CEO and manage our public information."
}
```

```json
{
  "method": "operator_review",
  "notes": "I am the CEO and manage our public information."
}
```

The response's `status` is `approved` or `pending`.

**Through Sureshake.** If you can't use the API, [contact us](https://www.sureshake.com/contact) with the company's page and your evidence.

> **Don't create a second company**
>
> **Claim and verify profile** on the Directory page opens **Company intake**,
> which creates a new company. It doesn't claim an existing one. If intake shows
> **Possible duplicate** and names your company, stop there. Continue only if
> yours is a different company.

## During review

The profile shows **Claim under review** and the public reference record stays visible. Nothing is hidden or replaced while the decision is pending.

## After approval

The profile becomes a managed profile. You can maintain its public facts, file reports, and configure permissioned sharing. Next, [publish your company](/directory/publish-your-company/) to refresh the page with your own facts.

In **Sources and verification**, **Profile control** then reads **Managed; identity verification not completed**, or **Identity verified by Sureshake** with a date once that's done.

## What a claim doesn't do

A claim changes who controls the profile, and nothing else.

- It doesn't make private financial information public.
- It doesn't certify the facts on the page. Facts the company supplies are still the company's own.
- It doesn't grant access to anyone's restricted reports.

If you later need to give up control, an owner can use **Unclaim or delete this entity** in Company Settings.

Source: https://docs.sureshake.com/directory/claim-your-profile/index.mdx