Pillar APIFetch public Pillar page data as structured JSON with one SocialCrawl API key. Same Author schema as every other platform. Reads are priced in credits.
1 active endpoint. Author-shaped page card.
One live read endpoint for public pillar.io pages. Display identity, bio when present, avatar when present, and the link stack when the host exposes it. Data API only. No page editing or private dashboards.
/v1/pillar/pagePublic pillar.io page by full URL. Returns a thin Author card (id, display name when present, location) plus every link as author._links with id, type, title, url, clicks, and order. Username, avatar, bio, and follower counters are often null on this singular page payload.
url
Returns a Pillar page's display name, bio, avatar, and every link on the page with its title and destination URL.
Use it for pillar.io pages; Linktree, lnk.bio, Linkme, and Komi pages each have their own endpoint.
1 credit
url · Full URL of the Pillar page
$ curl https://www.socialcrawl.dev/v1/pillar/page?url=https%3A%2F%2Fpillar.io%2Fexample \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responsePillar is a normal SocialCrawl social surface. You call GET /v1/pillar/page with an API key, spend credits on live misses, and get a single JSON envelope back. No Pillar OAuth. No second SDK.
Send your key in the x-api-key header. No Pillar login cookie, no partner portal. The same key works for TikTok, Instagram, Reddit, and the rest of the catalog.
Pass the full public pillar.io URL in the url query param. We validate the format before charging.
Standard reads cost 1 credit. Cache hits cost 0. Empty or hard failures refund.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. The page lands as a canonical Author object.
Most products resolve one public page URL, then store or compare the Author card and link list.
GET /v1/pillar/page?url=https://pillar.io/…Author-shaped page: location when set, _links[] with clicks and order
One URL in, structured Pillar card out. Useful when click order matters more than a rich profile header.
GET /v1/pillar/page
?url=https://pillar.io/example
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here{
"success": true,
"data": {
"id": "babd63b0-c004-40f3-a47c-2000e36e71fa",
"username": null,
"display_name": null,
"avatar_url": null,
"bio": null,
"location": "",
"url": "https://pillar.io/example",
"_links": [
{
"id": "1",
"type": "LINK",
"title": "Homepage",
"url": "https://example.com",
"clicks": 120,
"order": 0
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl. If you already parse other Author cards, you parse this the same way.
id, display_name, location, url, _links[] (id, type, title, url, clicks, order)
Same request lifecycle as every other /v1 platform endpoint. Link-in-bio hosts are not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds pillar/page. Required url format checks run first. Invalid input returns 400 with no charge. Valid calls debit 1 credit before upstream work.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is fetched live. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
Upstream JSON is mapped to Author (plus _links when the host exposes a public link array), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Pillar is public-read creator page data. We normalize it into the SocialCrawl Author schema so your code does not learn a second host-specific layout.
Public creator pages on pillar.io. Read-only surface for research, monitoring, and product jobs. No page edit or private dashboard access.
GET /v1/pillar/page fetches the public page URL you pass, live on request, and normalizes the payload before it reaches you.
A unified JSON envelope with an Author-shaped data object. Link rows land under author._links with clicks and order when the host exposes them.
No write endpoints. No private analytics. Username, avatar, bio, and aggregates are null when the singular page payload does not expose them.
The jobs this API is most often used for.
Pillar link-stack capture with per-link click signals
Callers pass one pillar.io URL and take the ordered link list. Profile identity fields are thin compared with Linktree or Komi. Public Pillar page as Author JSON for 1 credit, including per-link clicks and order. Same key and envelope as the rest of SocialCrawl.
Page reads are typically a few seconds on live miss. Cache hits return immediately.
Common ways teams put this data to work, and the stack each one tends to run.
Watch fixed pillar.io URLs for title, order, and destination changes. page is the only route.
Store Pillar stacks with per-link clicks as structured Author cards and track ranking changes over time.
Attach a Pillar link card to a creator record. Cache hits keep recurring reads cheap.
Standard tier is one credit per live call. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/pillar/page?url=https://pillar.io/example" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Pillar data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Setup | One GET request with your API key, first page data in minutes | Headless browser, proxy pool, and HTML parser to build and host |
| Authentication | Single x-api-key header, the same key across all 51 platforms | None to manage, but IP blocks and bot detection are your problem |
| Response schema | Unified JSON shared with 50 other platforms: profile, links, products in stable fields | Raw HTML that changes whenever Pillar ships a redesign |
| Pricing | 1 credit per page; 100 free credits on signup, no credit card | Proxy and server costs plus engineering hours, hard to predict |
| Maintenance | Upstream layout changes are absorbed behind the stable schema | Your parser breaks silently on every UI update |
Setup
Authentication
Response schema
Pricing
Maintenance
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl