What do the Access, Data, and API reference sections of the OpenAlex Help Center cover?

The OpenAlex Help Center splits its reference material into three sections that map to three stages of working with the catalog: Access covers how to get the data, what it costs, and how to fix errors; Data defines and describes what OpenAlex actually contains; and the API reference documents the REST API you use to query it. If you are deciding where to start, pick the section that matches your current blocker — you cannot retrieve data (Access), you do not understand a field or entity (Data), or you know what you want but not how to request it (API reference).

Access: getting the data, pricing, and error fixes

This section is for the practical question of how data leaves OpenAlex and reaches you. According to the Help Center, Access covers three things:

• Getting the data — the routes available for pulling OpenAlex content.
• Pricing — the cost conditions attached to those routes.
• Fixing errors — what to do when something in your retrieval goes wrong.

Use Access when your problem is logistical rather than conceptual. For example, if you have a working query but need to know whether your usage pattern fits a given access route, or you have hit an error and need the documented remedy, this is the section to read. The Help Center does not state pricing figures on its landing page, so treat cost as something to confirm inside the Access pages themselves rather than assuming any tier is free.

Data: what OpenAlex contains

Data is the definitional layer. It defines and describes OpenAlex's contents — the entities, fields, and structure of the catalog. Reach for it when the question is "what does this thing mean?" rather than "how do I fetch it?"

This matters because API work fails quietly when you misread the model. If you are unsure what a given entity represents, how records relate to each other, or what a field is actually measuring, the answer belongs in Data, not in the API reference. Getting this right first saves you from writing queries against a misunderstood schema.

API reference: the REST API

The API reference documents the REST API — the concrete interface for querying OpenAlex programmatically. It is the section you open once you already know what you want and which entity it lives in, and you now need the request syntax, parameters, and response shape.

A useful division of labor: Data tells you what exists, the API reference tells you how to ask for it, and Access tells you how to get it at scale and what it costs.

How the three fit together

The sequence is usually Access → Data → API reference in terms of dependency, but not in terms of reading order. Most people start with Data to understand the model, move to the API reference to build a query, and consult Access when they scale up or hit a failure.

Finding the right page faster

The Help Center offers several entry points beyond browsing the three sections:

• Search the full help center — described as the fastest way to answer a specific question.
• Quickstart — a five-minute walkthrough if you are just starting.
• How-to guides — short answers to simple questions.
• Tutorials — longer, step-by-step recipes.
• llms.txt — a plain-text index of every page at help.openalex.org/llms.txt, useful for both humans and AI agents.
• Markdown versions — add .md to any page URL to get a markdown copy.

If you prefer asking in natural language, the Help Center notes a free OpenAlex connector for Claude, with a ChatGPT version described as coming soon. It also points to a Google Group for user discussion and a bug-report channel for the team.

Practical takeaway

Match the section to your blocker rather than reading all three front to back. If you cannot get data or need to know what it costs, go to Access. If a term or entity is unclear, go to Data. If you know exactly what you want but not the request, go to the API reference. When you are unsure which applies, search the help center first — or use the llms.txt index to scan every page at once.