Solutions / Developers
Build the data feature. Keep the integration simple.
Use one API key and a shared response envelope for public-data requests. Inspect parameters, copy a working request, and handle errors before connecting your application.
COLLECT → REVIEW → BUILD
A server-side data integration
Public source data, documented requests, and a traceable response.
Workflow illustration. Collection, scheduling, and analysis run in your application.
Use cases
Make the data useful to your team.
Profile enrichment
Add public account or project context to an existing record.
Data pipelines
Collect available source data into your own storage and transformation jobs.
Application features
Build public content previews, research interfaces, or agent context retrieval.
- 1
Inspect an endpoint
Check the method, inputs, credit cost, and response contract in the API reference.
- 2
Make a server-side request
Send your API key in the x-api-key header. Keep credentials out of client-side code.
- 3
Handle the response
Read success and error states, store the fields you need, and use the request ID when debugging.
Suggested starting points
Endpoints for this workflow.
GitHub Profile API
Retrieve the public profile details available for a GitHub account.
GitHub Repo API
Look up a public GitHub repository and its project metadata.
Bluesky Profile API
Retrieve the public profile details available for a Bluesky account.
Bluesky Search API
Search Bluesky using the documented query and filters, and return structured results.
YouTube Channel API
Look up a public YouTube channel and inspect its returned details and metrics.
YouTube Video API
Look up a YouTube video by its documented identifier or URL.
Coverage is rolling out during preview. Test the endpoint you need before integrating. Unavailable operations return an explicit error and use no credits.
FAQ
Questions teams ask
Does SocialQuery run this entire workflow for me?
+
SocialQuery provides the documented data endpoints. Your application handles scheduling, storage, analysis, and delivery of the final report or feature.
How do I estimate usage?
+
Each endpoint lists its credit cost and cache window. Start with a small sample, inspect the actual response, and review usage in your dashboard.
Can I add more sources later?
+
Yes. Browse the platform catalog and test the additional endpoints you need. Authentication and response metadata are shared; the data fields depend on the operation.
Next step
Start with one useful request.
Test a source, inspect its response, and build from there.