Skip to main content
Superdata offers four focused products through one synchronous REST API: Profile, Profile Posts, Company, and Company Posts. Every endpoint returns structured data directly and does not create background jobs or require polling.

Base URL and authentication

Every request requires an API key in the authorization header:
Create and revoke keys from the Superdata API dashboard. API keys are not accepted in query parameters.

Endpoints

Get a profile

View the complete Profile API reference →
Provide at least one identifier. When several are supplied, precedence is url, person.id, user_id, then profile_id.

Get a company

View the complete Company API reference →
Provide at least one identifier. Precedence is url, company.id, then org_id.

Get profile posts

View the complete Profile Posts API reference →
Provide url, person.id, or profile_id, in that precedence order.

Get company posts

View the complete Company Posts API reference →
Provide url, company.id, or org_id, in that precedence order.

Cache strategies

strict and besteffort are supported by Profile and Company. Post endpoints support cached and fetch.

Responses

A successful profile or company request returns the provider fields under data:
Post responses include data.posts and pagination metadata. Additional provider fields remain under data.
Errors always use one safe envelope:
Every response includes X-Request-Id, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. Include the request ID when contacting support.