# Check if an e-mail address has an Instagram account

> Find out in real time whether an e-mail address is associated with an Instagram account. Yes, no or unknown; no usernames or profiles; unknowns free.

Canonical: https://mobilevalidate.com/services/instagram-email-check · Last updated: 2026-09-25

![An e-mail envelope routed to mail servers found in DNS; two mailboxes are confirmed and one answer is unknown.](https://mobilevalidate.com/images/email-mailbox-verification.svg)

*E-mail checks look up the domain's mail servers, then whether the mailbox exists.*


The Instagram e-mail check answers whether an e-mail address is associated with an Instagram account. It runs in real time and in bulk jobs, and returns `registered: true`, `false` or `null` (unknown), with the time we checked. Nothing is sent to the address, and no username, photo or profile is returned.

## What does the Instagram e-mail check tell you?

It tells you whether Instagram has an account that uses this e-mail address. Instagram accounts can be registered with an e-mail address or a mobile number. For numbers, use the [Instagram number check](/services/instagram-number-check). Instagram is owned by Meta but keeps its own accounts. Linking an Instagram account to a Facebook account in Meta's Accounts Center does not merge them, so the [Facebook e-mail check](/services/facebook-email-check) can give a different answer for the same address.

- `registered: true`: an Instagram account is associated with the address.
- `registered: false`: a conclusive "no account".
- `registered: null`: no conclusive answer, with `status` and `reason` explaining why. Not charged.

## Who uses it, and why?

- **Creator and community platforms.** Services whose users are active on Instagram use a "yes" as one signal that a new sign-up is a real person rather than a script. See [OTP and sign-up fraud](/use-cases/otp-and-signup-fraud).
- **Lead verification.** Combined with the [mailbox check](/services/email-verification), it helps separate real consumer leads from invented addresses. See [lead verification](/use-cases/lead-verification).

## What do you get back?

| Field | Type | Meaning |
|---|---|---|
| `email`, `email_status` | string, enum | Normalized address; `valid`, `invalid_email`, `duplicate` or `suppressed` |
| `checks["instagram.email"].registered` | boolean or null | `true` account exists, `false` none, `null` unknown |
| `…status`, `…reason` | enum, string | Outcome, and why an answer is not conclusive |
| `…confidence`, `…checked_at` | enum, timestamp | How sure the answer is, and when it was obtained |
| `…cached`, `…billed` | boolean | Cache hit, and whether it was charged |

## How is it billed?

You pay per address with a conclusive answer. Real-time and bulk have separate prices, shown on [pricing](/pricing). You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate). Cache hits inside the freshness window are free.

## What are the limits?

The check runs in real time (`POST /v1/lookup`, up to 100 numbers and e-mails) and in bulk jobs (`POST /v1/jobs`, up to 50,000). Use the code `instagram.email`. The alias `instagram` means the phone-number check. A request can hold up to 20 checks. Requests that look like sequential number ranges or generated e-mail lists are rejected: 20 or more addresses in one request on one domain that differ only by digits or separators, or, with live keys, 50 or more of one such pattern per account per UTC day.

## How do I use it responsibly?

Use the check on addresses your users gave you, for fraud prevention and data quality. We never read mailboxes or send e-mail to the address, and the answer is only yes, no or unknown. Don't use it to look up someone's social media presence or to build audiences for unsolicited messages. The [acceptable use policy](/legal/acceptable-use) forbids both. People can object through the [opt-out form](/opt-out).

## Example request

```bash
curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["registered@test.mobilevalidate.com"], "checks": ["instagram.email"]}'
```

Response (excerpt, test mode: the first item of `results`):

```json
{
  "kind": "email",
  "input": "registered@test.mobilevalidate.com",
  "email": "registered@test.mobilevalidate.com",
  "email_status": "valid",
  "e164": null,
  "country": null,
  "checks": {
    "instagram.email": {
      "service": "instagram.email",
      "status": "completed",
      "registered": true,
      "attributes": null,
      "confidence": "high",
      "confidence_score": 0.99,
      "checked_at": "2026-09-25T14:25:32.298Z",
      "cached": false,
      "age_seconds": 0,
      "billed": false,
      "reason": null,
      "poll_after_ms": null
    }
  },
  "test": true
}
```

## Frequently asked questions

### Does the check return the Instagram username or profile?

No. It only answers whether an Instagram account is associated with the address: yes, no or unknown. No username, photo or profile is returned.

### Is this the same as the Facebook check?

No. Instagram accounts are separate from Facebook accounts, even when they are linked in Meta's Accounts Center. Use both checks if you need both answers.

### Does the person find out?

No. Nothing is sent to the address and nothing happens on the account.

### What does an unknown answer cost?

Nothing. Inconclusive answers are never charged.

## Service code and modes

- Code: `instagram.email` (input: e-mail address)
- Modes: realtime and bulk · worldwide

## Price (live)

- Realtime (POST /v1/lookup): $0.003 per check ($3.00 per 1,000)
- Bulk (POST /v1/jobs): $0.0015 per check ($1.50 per 1,000)
- You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate).

## Response fields (from the public catalog)

| Field | Type | Meaning |
|---|---|---|
| registered | boolean or null | true = found, false = not found, null = unknown (not charged) |
| status | enum | completed, pending, unknown, unsupported_country, failed |
| checked_at | timestamp | When the answer was obtained |

_Platform and brand names are used only to describe which service a check refers to. MobileValidate is not affiliated with, endorsed by or sponsored by any of these companies; all trademarks belong to their owners._
