Team
The people behind Social Fetch
We write the docs, answer the support threads, and keep the fetch layer up. This is the team you will actually hear from.
Luke Askew
Social data APIs
Founder of Social Fetch. Writes about social-data APIs, reliability, and the production incidents that forced better timeouts, envelopes, and billing.
Jade
Developer onboarding
Operations at Social Fetch. Jade writes about developer onboarding, usage, and the stretch between a first API key and a production job that stays up.
Sarah
Customer support
Customer support at Social Fetch. Sarah lives in email threads and `meta.requestId` — billing, credits, 429s, and the failed call an hour before a demo. She writes the replies developers can act on: a corrected curl, the right doc section, or an honest "it's on us."
Michael
Incident communication
Customer support at Social Fetch. Michael writes about platform drift, failed jobs, and the incident notes customers can actually use — request IDs, sample URLs, and a retry path that works.
Emily
SEO content
SEO content at Social Fetch. Emily writes integration guides and tutorials with working curl examples and real endpoint names — the pages developers finish, not just skim.
David
Web scraping
Web scraping specialist at Social Fetch. David writes about schema drift, empty parses, and the Instagram or TikTok change that breaks a fetch overnight.
Jessica
SEO content
SEO content at Social Fetch. Jessica writes comparison pages and platform guides — which endpoint to hit, what a live API actually returns, and how Social Fetch stacks up against tools like Apify.
Company byline
Some posts are published under the Social Fetch organisation rather than an individual. That byline is used for product updates, shipping notes, and anything that speaks for the whole team.
The Social Fetch team publishes shipping notes, API design essays, and production post-mortems for developers who need live social and web data without running scrapers.