Blog
Notes from building a social data API
We publish here when we ship an endpoint, change how billing or errors work, or learn something expensive in production. Expect short essays on response envelopes, founder post-mortems with real numbers, and curl-first writeups when a feature is easier to show than summarize.
All posts
22 articles. RSS
Compare
Reddit API pricing in 2026 (what you pay)
Luke AskewPost-mortems
The Scrape Job That Never Timed Out
Luke AskewCompare
X API Pricing: Official vs Public Data
Luke AskewEssays
Why social media APIs should be boring
Luke AskewEngineering
Ask social data questions in plain English
Social FetchEssays
The envelope is the product (API design)
Luke AskewEngineering
Twitter Search API — Keyword Filters on X
Social FetchEngineering
The official TypeScript SDK for Social Fetch
Luke Askew
About the blog
This is not a content calendar. We do not publish on a schedule, and we are not trying to rank for "what is an API." Most posts start as something we had to explain twice in support or a week we wish had ended differently — like the LinkedIn scraper jobs that ran for hours without failing and billed before anyone noticed.
If you are evaluating Social Fetch, start with the reliability post-mortem. If you are integrating, read the envelope and TypeScript SDK posts. Shopping a single network? Use the platform listicles for pricing and coverage side-by-side. Tutorials with runnable code live on the guides index; vendor comparisons live under /compare.
Authors are named on each card. When you email support about something you read, mention the post title — we can usually connect it to the week we wrote it and the endpoint version it references.
Questions about a post? Email support with the requestId from your API response — we can usually trace the thread back to the week we wrote it.