What Social Links Search does and who it's for
Social Links Search takes a text query—typically a person's name, a brand name, or any relevant keywords—and returns the matching social profile URLs it finds on the web in real time. Rather than maintaining a static database, the API searches the live web each time a request is made, which means results reflect current profile data rather than cached snapshots.
The nine supported platforms cover the vast majority of where public profiles live: Facebook, TikTok, Instagram, Snapchat, Twitter, LinkedIn, YouTube (channels), Pinterest, and GitHub. That breadth makes the API useful for a wide range of developers: those building CRM enrichment tools, lead research products, influencer discovery platforms, competitor monitoring dashboards, or any application that needs to aggregate a subject's public social presence from a single identifier.
The endpoint in detail
Social Links Search exposes a single endpoint:
GET /search-social-linksRequest parameters
query(required) — the search string, for example a person's full name or a brand keyword.social_networks(optional) — a comma-delimited list that scopes the search to specific platforms. Accepted values arefacebook,tiktok,instagram,snapchat,twitter,youtube,linkedin,github, andpinterest. Omitting this parameter presumably searches across all supported networks.
The social_networks filter is worth paying attention to if you only need results from two or three platforms. Scoping the search could improve relevance and, depending on implementation, may also affect response time.
Response shape
The response contains one field per platform, each holding the profile URL found for that network:
facebook— Facebook page URLinstagram— Instagram profile URLtiktok— TikTok profile URLtwitter— Twitter profile URLlinkedin— LinkedIn profile URLsnapchat— Snapchat profile URLyoutube— YouTube channel URLpinterest— Pinterest profile URLgithub— GitHub profile URL
Fields are absent or null when no match is found for a given platform. Because results come from a live web search rather than a curated index, you should handle partial results gracefully in your integration—not every query will return all nine links.
Latency and reliability
The published average latency is 1,652 ms and the average success rate is 99.00%. The latency figure reflects the real-time nature of the search; this is not a cached lookup. For synchronous user-facing flows that expectation matters, but for background enrichment pipelines running asynchronously it is entirely workable. The 99% success rate indicates the service is stable and rarely returns errors.
Pricing breakdown
The API follows a freemium model with four tiers:
| Plan | Monthly price | Requests included | Rate limit | Overage per request |
|---|---|---|---|---|
| BASIC | $0 | 50 | 1 req/sec | — |
| PRO | $25 | 10,000 | 5 req/sec | $0.0030 |
| ULTRA (recommended) | $75 | 50,000 | 10 req/sec | $0.0020 |
| MEGA | $150 | 200,000 | 20 req/sec | $0.0010 |
BASIC is genuinely free but the 50-request monthly ceiling makes it suitable only for evaluation and proof-of-concept work. At one request per second you will not hit rate limits, but you will exhaust your monthly quota in a single moderate test session.
PRO at $25/month is the entry point for any production use. Ten thousand requests per month works out to roughly 333 per day—enough for a small enrichment pipeline or a lightly trafficked research tool. Overage is billed at $0.003 per request, so exceeding the quota by a few thousand calls in a busy month is affordable.
ULTRA is flagged as recommended and the economics show why: the per-request cost drops from $0.0025 effective on PRO to $0.0015 effective on ULTRA, and the overage rate also falls to $0.002. If your application is making more than roughly 17,000 requests a month, ULTRA becomes cheaper than staying on PRO with overages.
MEGA makes sense for high-volume operations—bulk lead enrichment, large-scale influencer databases, or multi-tenant SaaS products. At 200,000 included requests and a $0.001 overage rate it offers the lowest marginal cost per lookup. Custom plans are available by contacting OpenWeb Ninja directly.
Practical use cases
Lead and contact enrichment — Sales and marketing tools can accept a prospect name or company and return a structured set of social profile links to append to a CRM record, saving hours of manual research per contact.
Influencer discovery and vetting — Marketing platforms can look up a creator's name and immediately retrieve their presence across TikTok, Instagram, YouTube, and other channels, enabling multi-platform reach estimates without scraping each site individually.
Due diligence and research tools — Journalism, HR, and background-check applications can use Social Links Search as part of a broader data assembly step, cross-referencing a subject's claimed profiles against what is actually discoverable on the web.
Developer portfolio and identity aggregation — GitHub and LinkedIn together make the API useful for developer-community applications that want to link a contributor's code repositories to their professional network profile.
Limitations and things to check before integrating
Because the API performs a live web search, results depend on how publicly accessible a profile is and how well indexed it is at the time of the request. Private or restricted accounts are unlikely to surface. Query quality also matters: a common name like "John Smith" will produce ambiguous results, so passing additional context in the query string (company name, location, field of work) is advisable.
The 1,652 ms average latency means you should not call this endpoint in a synchronous request path where sub-second response is expected. Design your integration to call it asynchronously or in a background job and store results.
There is one endpoint and no documented filtering beyond social_networks. There is no pagination, confidence scoring, or deduplication mechanism exposed in the documented response fields. If you need to resolve ambiguity between multiple possible matches for a name, you will need to build that logic in your application layer.
The free BASIC tier's 50-request cap means you should not rely on it for anything beyond initial testing.
Getting started
Social Links Search is available on the RapidAPI marketplace via OpenWeb Ninja. Signing up for the BASIC plan requires no credit card and gives you enough requests to validate the response format and test query strategies before committing to a paid tier. The provider offers support via email at [email protected] and a live Discord community at https://discord.gg/wxJxGsZgha, which is useful if you hit integration questions or want to discuss custom volume needs.
