100 free credits — no credit card required.Start building
Logo
Use case

Cross-platform identity API for public accounts

Check one handle against every network in a single pass. Public profiles only, so you can confirm which accounts are official, find the lookalikes trading on a brand name, and see what each one actually publishes.

/v1/prism

One handle, every network

  • GET /v1/prism/lookup
  • GET /v1/prism/handle-audit
  • GET /v1/prism/profiles
  • GET /v1/google/search

A cross-platform identity API checks one public handle against many networks at once and returns the profiles that exist, so you can tell which accounts are official and which are impersonating a brand. SocialCrawl resolves handles across 46 platforms using public profile data only, with no private-record lookup, no contact resolution and no de-anonymisation.

What teams build with it

Every one of these runs in production today. The endpoint chain under each card is the actual call sequence.

One handle, every network

Send a handle and the networks you care about, and get back the public profile on each one that has it. When a specific network needs to be certain rather than indicative, follow up with that platform's own profile call.

Endpoint chainprism/handle-audit (one handle, every network)

Resolve a set of profiles at once

Ask for several profiles in one composite call, then drill into whichever one looked wrong. Most identity work is a fan-out followed by exactly one deep read.

Endpoint chainprism/profiles -> per-platform profile

Start from the open web

Site-scoped search finds where a brand or public account already appears before you assume the handle is consistent. This is the most common first step in practice, because handles rarely match across networks.

Endpoint chaingoogle/search site: -> platform profile

Turn any URL into a record

Paste a link from any supported network and get a structured profile or post back without knowing which platform endpoint to call. Useful when your input is a list of links from a report rather than clean handles.

Endpoint chainprism/lookup (any URL, structured)

Brand protection sweeps

Run the same brand name across networks on a schedule and diff the result. New accounts using your name, logo or product term are what you are watching for, and they show up as additions between runs.

Endpoint chaininstagram/profile -> tiktok/profile

Check a self-declared link stack

Creator link pages are the one place identity is declared by the person themselves, which makes them a useful cross-check on a partnership claim. Coverage depends on the page resolving, so treat it as corroboration rather than proof.

Endpoint chainlinktree/page -> resolve each link

How the cross-platform identity API works

Four calls take you from one handle to a verified picture of where a public account exists. Fan out first, then confirm the ones that matter.

Reads are priced in credits. Empty result sets are not billed on list endpoints, and failed upstream calls are refunded automatically. Everything returned is public profile data.

  1. GET /v1/prism/handle-audit

    Audit the handle

    Send one handle and a platform list, and get the public profiles that exist under it. This is the fan-out step and the fastest way to see the shape of the problem.

    per call
  2. GET /v1/prism/profiles

    Pull the profiles together

    Request the resolved profiles as one composite record so follower counts, bios and verification state sit side by side rather than in six responses.

    per call
  3. GET /v1/google/search

    Search the open web

    Use site-scoped queries to catch the networks where the handle is spelled differently. Handles drift, brands do not.

    per call
  4. GET /v1/prism/lookup

    Resolve anything left over

    Hand any remaining URL to one endpoint and get a structured record back, whichever platform it belongs to.

    flat rate per call

Compared with the usual setup

Most teams either check handles by hand or buy a tool that only tells them whether a username is taken. Here is what changes.

CapabilitySocialCrawlTypical setup
What you get backFull public profiles with bios, follower counts and recent posts, so you can judge which account is real.A taken or available flag, with no way to tell a brand from a squatter.
CoverageOne key spans 46 platforms, including the newer networks and developer surfaces.A fixed list that stops updating when a network changes its markup.
Data scopePublic profile data only, and the scope is stated plainly rather than implied.Vague sourcing that leaves your compliance team asking where it came from.
Handle driftSite-scoped web search catches the networks where the name is spelled differently.Exact-match only, so the impersonator with one extra character is missed.
Pricing modelNever-expire credit packs, priced per call, so an occasional sweep stays cheap.Monthly seats billed whether you swept anything or not.
Getting startedFree credits on signup and a runnable call in the first minute.Sales call, then onboarding.

Cross-platform identity API questions

What is a cross-platform identity API?

A cross-platform identity API takes one public handle and checks it against many social networks in a single pass, returning the public profiles that exist under it. It answers the practical question of where an account lives, which accounts are official, and which are using a brand name without permission.

What data does it use?

Public profile data only. That means the handle, display name, bio, follower counts, verification state and public posts, exactly as any visitor to that profile would see them. It does not draw on private records, purchased identity data or anything behind a login.

Can I resolve a person from a phone number or email address?

No. There is no lookup from a phone number, an email address or any other personal identifier, and there is no de-anonymisation step anywhere in the product. The input is a public handle, a public URL or a search term, and the output is public profiles.

What is this actually for?

Brand protection and account verification are the main jobs. Confirming your own official accounts across networks, finding impersonators using your name or logo, vetting a creator's accounts before a partnership, and following the public accounts of organisations and public figures for research.

Is this GDPR compliant?

SocialCrawl returns public data only, which is the basis on which customers with a European compliance load use it. You remain the controller of whatever you store and for the lawful basis of your own processing, so keep retention tight and scope the work to the purpose you documented. We can share our data handling position on request.

Do handles match across platforms?

Often, and not reliably. That is why the recommended flow pairs a handle audit with site-scoped web search: the audit catches the exact matches quickly, the search catches the networks where the same brand posts under a different name. Treat a single exact match as a lead, not a conclusion.

How much does a handle check cost?

Reads are priced in credits from never-expire packs, so you pay per call rather than per seat. A composite fan-out costs more than a single profile call and replaces several of them. Signup includes 100 free credits and no card is required.

Resolve your first handle

100 free credits on signup. Public data only, no card, no sales call.

Request
curl -G "https://socialcrawl.dev/v1/prism/handle-audit" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY" \
  --data-urlencode "handle=nasa" \
  --data-urlencode "platforms=instagram,tiktok,youtube,twitter"
curl -G "https://socialcrawl.dev/v1/prism/lookup" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY" \
  --data-urlencode "url=https://www.tiktok.com/@nasa"

Both calls run against live data. Swap the key and the handle and they work as written.