Menus

Weedmaps supports multiple menus per listing, offering greater flexibility for how retailers manage their product offerings.

📘

Access Scoping

These operations lets the Integrated Partner who is linked to the Bearer Token retrieve all of the Menus that they are authorized to view.

You can use the sort and filter query parameters to refine the results and locate specific Menus.

Understanding Menu IDs

Historically, integrations referenced a WMID (Weedmaps Listing ID). With multiple menu support, this has shifted:

Verifying Menu Access

You can verify access to a menu using the following operation Retrieve a Menu

curl \
  --url 'https://api-g.weedmaps.com/wm/2025-07/partners/menus/{MENU_ID}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}'

• 200 OK = Menu exists and you have access
• 404 Not Found = Menu does not exist or access has not been granted

📘

Paused Integrations

Retailers can pause your integration at any time:

• When paused, you cannot create, update, or delete menu items (returns 423 Locked).
• You can continue reading menu data during pauses.

Working with Organizations

The schema for the response for a Menu operation looks like:

{
  "data": [
    {
      "id": 636708886,
      "name": "Seal Team Spliff Dispensary",
      "items_count": 33,
      "features": [],
      "organization": {
        "id": 89188,
        "name": "Integrations Test Org"
      },
      "updated_at": "2025-07-21T00:14:32Z"
    }
  ],
  "meta": {
    "page": 1,
    "per_page": 20,
    "total": 1
  }
}

You will be able to then leverage the filters[organization_id] with the Organization identifier to get all of the Menus linked to that Organization:

curl \
	--url 'https://api-g.weedmaps.com/wm/2025-07/partners/menus?page_size=20&filters[organization_id]={organization_id}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}'

Key Takeaways

• Always manage by Menu ID.
• Ignore WMIDs when building or updating integrations.
• Validate access via the /menus/{menu_id} endpoint before performing write actions.