Skip to main content
MetaCustomer feedback

A developer building a multi-tenant assistant platform reports encountering Graph API Error 100 subcode 33 when attempting to access partner-shared client WhatsApp Business Accounts (WABAs) via...

What happened

A developer building a multi-tenant assistant platform reports encountering Graph API Error 100 subcode 33 when attempting to access partner-shared client WhatsApp Business Accounts (WABAs) via Meta's WhatsApp Cloud API.

Source

RedditOct 24, 2026By u/aarondiaz92

r/zapier

WhatsApp Cloud API: Error 100, subcode 33 when accessing a partner-shared WABA

upvotes
3
comments
2

Post

Highlighted: the lines this signal was extracted from

Hi everyone! I'm building a multi-tenant WhatsApp assistant platform using Meta's WhatsApp Cloud API, n8n, and PostgreSQL. My goal is to manage multiple clients through one provider-owned app and a shared webhook endpoint. My app works perfectly with my own WABA, but I cannot access a client's WABA, even though it has been shared with my business portfolio. My setup: My Meta app is owned by my business portfolio. The client's WABA belongs to their own business portfolio. The client shared their WABA with my portfolio as a partner, granting full control. I assigned the client's WABA to my System User with full control. My System User also has access to my app. The app has the required permissions: business_management, whatsapp_business_management, and whatsapp_business_messaging. What works: My System User token successfully retrieves the phone numbers from my own WABA. What fails: When I query the client's WABA using the same token, both the WABA lookup and the phone-number listing return Graph API error 100, subcode 33: "Unsupported get request. Object does not exist, cannot be loaded due to missing permissions, or does not support this operation." I generated a new System User token with the same permissions after assigning the client's WABA, but the error persists. I also confirmed that: The client's WABA appears in my System User's assigned assets with...

Keep reading with a free account

The rest of this post, and every signal for Meta, is in your free account.

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/zapier
Event date
Oct 2026

Companies

  • n8nAlso named

The full record

From the Signal API record

Numbers

Mentions
35

Details

Timing
Ongoing state
Category
Integration
Link URL
/r/n8n_ai_agents/comments/1xdw6vr/whatsapp_cloud_api_error_100_subcode_33_when/
Virality
Very low
Post kind
Crosspost
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • integration
  • messaging
  • permissions
  • api

Products named

  • WhatsApp Cloud API
  • Graph API

Extraction

Sentiment
Negative
Detected
Oct 24, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Meta and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Meta this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/3b117910-a38f-5506-a9b4-df84f0d63aef returns this record as JSON. POST /v1/companies/enrich returns every signal for meta.com.

{
  "signal_id": "3b117910-a38f-5506-a9b4-df84f0d63aef",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-24T01:46:45+00:00",
  "company": {
    "name": "Meta",
    "domain": "meta.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "api",
      "integration",
      "messaging",
      "permissions"
    ],
    "post_id": "1xdw6zy",
    "summary": "A developer building a multi-tenant assistant platform reports encountering Graph API Error 100 subcode 33 when attempting to access partner-shared client WhatsApp Business Accounts (WABAs) via Meta's WhatsApp Cloud API.",
    "category": "integration",
    "evidence": [
      "[post] WhatsApp Cloud API: Error 100, subcode 33 when accessing a partner-shared WABA",
      "[post] When I query the client's WABA using the same token, both the WABA lookup and the phone-number listing return Graph API error 100, subcode 33: \"Unsupported get request. Object does not exist, cannot be loaded due to missing permissions, or does not support this operation.\""
    ],
    "link_url": "/r/n8n_ai_agents/comments/1xdw6vr/whatsapp_cloud_api_error_100_subcode_33_when/",
    "virality": "very_low",
    "post_date": "2026-10-24T01:46:45.000Z",
    "post_kind": "crosspost",
    "post_text": "Hi everyone! I'm building a multi-tenant WhatsApp assistant platform using Meta's WhatsApp Cloud API, n8n, and PostgreSQL. My goal is to manage multiple clients through one provider-owned app and a shared webhook endpoint.\n\nMy app works perfectly with my own WABA, but I cannot access a client's WABA, even though it has been shared with my business portfolio.\n\nMy setup:\n\nMy Meta app is owned by my business portfolio.\n\nThe client's WABA belongs to their own business portfolio.\n\nThe client shared their WABA with my portfolio as a partner, granting full control.\n\nI assigned the client's WABA to my System User with full control.\n\nMy System User also has access to my app.\n\nThe app has the required permissions: business_management, whatsapp_business_management, and whatsapp_business_messaging.\n\nWhat works:\n\nMy System User token successfully retrieves the phone numbers from my own WABA.\n\nWhat fails:\n\nWhen I query the client's WABA using the same token, both the WABA lookup and the phone-number listing return Graph API error 100, subcode 33:\n\n\"Unsupported get request. Object does not exist, cannot be loaded due to missing permissions, or does not support this operation.\"\n\nI generated a new System User token with the same permissions after assigning the client's WABA, but the error persists.\n\nI also confirmed that:\n\nThe client's WABA appears in my System User's assigned assets with full...",
    "sentiment": "negative",
    "subreddit": "zapier",
    "event_date": "2026-10",
    "post_title": "WhatsApp Cloud API: Error 100, subcode 33 when accessing a partner-shared WABA",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/zapier/comments/1xdw6zy/whatsapp_cloud_api_error_100_subcode_33_when/",
    "entity_role": "vendor",
    "post_author": "aarondiaz92",
    "upvote_ratio": 1,
    "mention_count": 35,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/zapier/",
    "total_upvotes": 3,
    "comments_total": 2,
    "total_comments": 2,
    "other_companies": [
      {
        "name": "n8n",
        "role": "adopted",
        "domain": "n8n.io"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/aarondiaz92/",
    "signal_category": "feedback",
    "comments_included": 0,
    "products_mentioned": [
      "WhatsApp Cloud API",
      "Graph API"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.