Social links in. Structured content out.
By ExportDat · Updated 23 October 2026
ExportDat is a content extraction API for developers who need available text, images, captions, transcripts and metadata from supported social posts, videos and podcasts. Submit a URL, process an asynchronous extraction job, and use the returned structured content in your application.
Looking for a social media scraper?
If your goal is to turn a specific post URL into source content for an AI workflow, ExportDat provides a consistent REST API instead of a separate extraction integration for each platform. It is designed for individual content links; it is not a promise of unrestricted scraping, profile harvesting or access to private content.
What can it extract?
| Source | Available content | Keep in mind |
|---|---|---|
| Post text, author information, images and accessible video or document content. | Documents and native media may be incomplete. | |
| Captions, carousel slides, image text and accessible video material. | Media acquisition varies by post and format. | |
| YouTube | Titles, descriptions, captions and transcripts for videos and Shorts. | A transcript may be unavailable or imperfect. |
| TikTok & Facebook | Available captions, descriptions, metadata and accessible source content. | Access and original media can be restricted; coverage may be partial. |
| Spotify & podcasts | Episode metadata and available authorised publisher-linked transcripts or captions. | An episode URL does not guarantee access to its original audio. |
See format-level details. The same API interface does not mean identical content is available from every platform.
How does URL-to-JSON extraction work?
- Submit: your application sends a supported post, video or episode URL to the API.
- Wait for the job: extraction runs asynchronously; check the job state rather than treating submission as a completed result.
- Read the result: inspect source content, attribution and completeness information.
- Use the content: pass suitable material to your research agent, enrichment workflow or other AI application.
A compact response excerpt
This shortened illustration uses fields from an example extraction result. It omits other fields and is not a complete API contract or a verified live extraction.
{
"platform": "linkedin",
"content": {
"text": "We spent 6 months building features nobody wanted.",
"transcript": null
},
"extraction": {
"coverage": "partial",
"missing": ["Image visual context not independently verified"]
},
"ai_ready": true
}An empty transcript means no transcript was returned. ai_ready does not establish completeness or accuracy: applications should still inspect coverage and missing-content fields. Confirm current endpoints, authentication and schemas with ExportDat before building a production integration.
Can I use it for podcast transcripts or video content?
Yes, where available: ExportDat can retrieve accessible transcripts, captions, video frames and metadata. It is not a universal podcast downloader or guaranteed transcription service for inaccessible audio. Your application should distinguish the original episode from an authorised alternative publisher edition.
Can it power research or outreach tools?
Research agents can compare retrieved source material. Enrichment tools can use available post content as context for prospect research. ExportDat retrieves content; your app handles analysis or outreach. Commercial use still depends on appropriate source permissions, and outputs need accuracy checks.
API or MCP: which should I use?
Use the REST API when your application needs structured content and control over the extraction workflow. Use MCP when a compatible AI assistant should retrieve content within a conversation. Both are included in the pricing options: start with 10 free links; top-ups start at $5 USD for 100 links.
Ask about API access or read how to use a link in an AI chat.
