Meet Emma

Emma writes the Twitter and X API guides published on this site. The job is easy to describe and harder to do well: take the parts of working with X data that stop a project, and write the page she wanted to find when she hit the same wall.

Most Twitter API tutorials assume you are willing to apply for a developer account, wait for review, and build an OAuth flow before you can read a single tweet. Emma writes for the other path. The guides here show how to reach X data over a plain REST call, the same way you would call any other HTTP service: a request, a bearer key, and a JSON response you can parse. That covers reading tweets, profiles, followers, timelines and search, and it covers the write side too, where she walks through the post, like, retweet, follow and direct-message endpoints with the exact request shape each one expects.

A lot of the writing is about the questions that decide whether a project ships. What are the real rate limits, and how does throttling actually show up in a response? When is a session cookie genuinely required, and when is a bearer key enough? What does it cost to read X data at volume when you are billed per call at $0.0008 a read instead of committing to an annual contract? Those get answered with worked examples and real numbers rather than hand-waving, because that is what she would want as the person doing the integration.

Emma also runs developer support. Email her about an endpoint, a status code you did not expect, or a billing edge case, and you reach the same person who wrote the guide. That loop is the point: the questions that arrive in support are the topics that become the next guide on this page.