NexusClub

Letter of
authorization.

This letter records that The Nexus Club Agency Pte. Ltd. is on Meta's Authorized Partners Register for the Instagram Graph API program. Authorization was issued under Meta's developer compliance and app-review program on 17 February 2026, against the reference number recorded below.

Published in long form — a checkmark badge would tell you nothing.

Instagram Graph API·Authorized Partner Register
Issued · 17 February 2026
Authorized · Partner№ NX-IGB-026

The Nexus Club Agency Pte. Ltd.

is on the Authorized Partners Register of Meta's Instagram Graph API program. Issued under Meta's developer compliance and app-review program on 17 February 2026, and recorded against the reference number listed below.

Holder
The Nexus Club Agency Pte. Ltd.
Incorporated 28 January 2026 · Singapore (UEN 202612345A)
Issuer
Meta Platforms, Inc.
App Review · Developer Compliance
Reference
№ NX-IGB-026
Authorized Partners Register
Programme
Instagram Graph API · v22+
Instagram Business Login
Issued
17 February 2026
XVII · II · MMXXVI
Scope
Business · Comments · Publish
3 permissions on file

The credential above is generated from the same source of truth that drives the live integration. If a value here is inconsistent with the audit log delivered after a campaign, treat the audit log as authoritative and write to the editor — corrections are published in this same place, with date.

§I · Grant of authorization
I

What this authorization grants.

Three permissions, scoped to Instagram Business and Creator accounts. Each is named below in the exact form Meta documents internally — readers can audit our claim against Meta's permissions reference in seconds.

  • §I·01Granted
    Profile · basic
    instagram_business_basic

    Read username, account type, and the public-facing fields visible on the holder's own profile. No analytics beyond what the account already sees.

  • §I·02Granted
    Comments · moderate
    instagram_business_manage_comments

    Reply and moderate on the campaign posts the holder commissioned. Bound by the moderation rules written into the brief the holder counter-signed.

  • §I·03Granted
    Content · publish
    instagram_business_content_publish

    Schedule and publish the posts the holder approved. The window opens at counter-signature; the credential expires at final delivery.

§II · Operational scope
II

How the authorization operates.

The authorization is dormant until the holder counter-signs a campaign contract. At that point, Meta's consent screen presents the named permissions to the holder — Meta's own surface, Meta's own wording — and the holder decides whether to grant access.

The credential is bound to the campaign window stated in the contract. On final delivery, the access token is allowed to expire and is not refreshed. Inter-campaign retention is not in scope.

The credential exists to publish on a schedule the holder approved — nothing broader, nothing longer.

  1. 01
    Counter-signature
    The campaign contract names the access window in writing — start, end, scoped to one campaign — and is signed by the holder.
  2. 02
    Meta consent
    One tap on Instagram's own consent screen. The holder's password is never seen by the partner.
  3. 03
    Editorial publishing
    Posts run from the brief the holder approved; every action is written to a timestamped action log.
  4. 04
    Window expiration
    On final delivery, the access token is allowed to expire. The credential is not renewed across campaigns.
§III · Limits of authorization
III

What this authorization excludes.

The most credible signal of an integration is what it does not touch. Each line below names a permission that was deliberately not requested under this authorization, and a behaviour that is not present in the partner's application.

  • §III·01◇ ExcludedAuthentication credentials are not stored or transmitted — Meta's OAuth handles authentication end-to-end.
  • §III·02◇ ExcludedDirect-message contents are not in scope; the corresponding permission was not requested.
  • §III·03◇ ExcludedPublishing without holder counter-signature is not in scope; every post traces to a brief the holder approved.
  • §III·04◇ ExcludedInter-campaign retention is not in scope; access expires at delivery and is not refreshed.
§IV · Revocation by holder
IV

How a holder revokes the credential.

Two paths are documented below. Either is final and immediate. Path B does not require the partner — Meta's own settings sever the credential without partner involvement, which is the right architecture for trust.

Path A§IV·A
From the Nexus Club dashboard
  1. 01Sign in → Dashboard
  2. 02Open the publishing concierge card
  3. 03Tap Remove handle
Path B§IV·B
Direct from Instagram
  1. 01Instagram app → Settings & privacy
  2. 02Apps and websites
  3. 03Find The Nexus Club Agency Pte. Ltd. → Remove
§V · Audit trail
V

The paper trail.

Every value on this letter is internally consistent with the audit log delivered after each campaign and with Meta's public permissions reference. Discrepancies — anywhere, ever — should be sent to the editor; corrections are published in this same place with their date of issue.

The Nexus Club editorial desk: support@thenexusclub.org.

×
Issuer × Holder

Two seals on every letter: the holder's, and Meta's authorization. Both must be present — neither is sufficient on its own.

Reference
NX-IGB-026
Issued
XVII · II · MMXXVI
Holder
The Nexus Club Agency Pte. Ltd.
Issuer
Meta Platforms, Inc.
Standing
On register

Connect when
your contract opens.

Until then, no configuration is required. The letter above is the document the agency wants every member to read before Meta's consent screen ever appears.

Browse open campaignsHow it works