Meet Emma.

Emma is the developer advocate at redditapis, and she writes the guides you read here. Her job is simple to describe and not so simple to do well: take the parts of working with Reddit data that trip people up, and write the page she wishes she had found when she hit the same wall.

Most Reddit tutorials assume you are happy to install PRAW, register a Reddit developer app, and wire up an OAuth flow before you can read a single comment. Emma writes for the other path. The guides on this site show how to reach Reddit data over a plain REST API, the same way you would call any other HTTP service: a request, a bearer token where one is needed, and a JSON response you can parse. That covers reading posts, comments, profiles, and search results, and it covers the write side too, where she walks through the authenticated comment, vote, and DM endpoints with the exact request shape each one expects.

A lot of her writing is about the questions that decide whether a project ships or stalls. What are the real rate limits per endpoint, and how does throttling actually show up in your responses? When do you genuinely need OAuth, and when can you skip it for read-only work? What does it cost to read Reddit data at volume when you are billed per call instead of locked into a flat annual contract? She answers those with worked examples and real numbers, not hand-waving, because that is what she would want as the person doing the integration.

Emma also runs developer support for the API. If you email her at emma@redditapis.com with a question about an endpoint, a status code you did not expect, or a pricing edge case, you reach the same person who wrote the guide. That feedback loop is the point: the questions developers ask in support are the topics that turn into the next guide on this page.