Skip to main content
The Meta developer documentation has two distinct page types — Guides and Reference pages — that serve completely different purposes. Knowing which one to open and how to read it prevents confusion and saves time.

The two page types

Guidesdevelopers.facebook.com/docs/whatsapp/cloud-api/guides/... Step-by-step instructions that explain how to do something. Written for humans who are learning. Examples: “Send Messages”, “Upload Media”, “Set up webhooks”. Use guides when you are learning a topic or following a setup flow. Reference pagesdevelopers.facebook.com/docs/whatsapp/cloud-api/reference/... Complete technical listings of every endpoint, parameter, field, and error code. They do not explain why — they just document what exists. Use reference pages when you are building and need to know the exact field name, allowed values, or what is required vs optional.

How to read a Reference page

Every reference page follows the same structure:
SectionWhat it tells you
Method + endpointPOST /{phone-number-id}/messages — the URL to call
Parameters tableEvery field: name, type, required/optional, description
Sample requestA ready-to-copy example body
Sample responseWhat success looks like
Error codesWhat can go wrong and what the code means
The Parameters table is the most important section. Always check the Required column — a missing required field causes the call to fail immediately.

The changelog — your most important bookmark

developers.facebook.com/docs/graph-api/changelog Meta releases new API versions several times a year. The changelog lists every version with what changed, what was added, and what was deprecated. Check the changelog when:
  • You are upgrading from one API version to a newer one
  • Something that was working suddenly breaks after a Meta update
  • You want to know if a new feature is available in the latest version
See Request anatomy & versioning for how versions appear in the URL.

How to find anything fast

  1. Start at developers.facebook.com/docs/whatsapp — the main landing page with the full left-sidebar navigation.
  2. Use the left sidebar to navigate between Guides and Reference sections.
  3. Use Ctrl+F inside a long reference page to jump to a specific field name.
  4. Use the search bar at the top of any page for cross-section searches.

Frequently asked

A Guide is step-by-step instructions for how to do something — written for learning. A Reference page is a complete technical listing of every parameter and field — written for building. Use Guides to learn, use Reference pages to look up exact details while coding.
In the Reference section: developers.facebook.com/docs/whatsapp/cloud-api/reference/messages. The Parameters table lists every field, whether it is required, its type, and what it does.
Check the changelog at developers.facebook.com/docs/graph-api/changelog. It lists every version release with what changed. Bookmark it and check it before upgrading your API version number.
Go to developers.facebook.com/docs/whatsapp/cloud-api. The left sidebar shows all sections — start with Guides for learning, then use Reference pages when you need exact field details.
Use Ctrl+F in your browser to search the page. Reference pages are long but well-structured — the field you need is always in the Parameters table.

Gotchas & common mistakes

  • Reading reference instead of guide — beginners often land on a reference page and get overwhelmed. If you are learning, find the Guide for that topic first.
  • Missing the Required column — skipping it is the most common reason an API call fails with a missing-field error.
  • Not checking the changelog before upgrading — changing your version number without reading the changelog can break things if a field was renamed or removed.
  • Searching on Google instead of the docs — Google results often link to outdated tutorials using old API versions. Always verify against the official docs.