BMM CONNECT DOCUMENTATION

Revocation

Disconnect a creator and stop authorised data access.

DELETE/api/connect/hosted/me

Authentication and permissions

Send X-BMM-Client-ID and X-BMM-API-Key from your server. The API key authenticates the approved application; creator consent controls access to the account. A key alone does not authorise access to a creator.

Also send X-BMM-User-ID, derived from your authenticated server session. No request body is required. Never accept an arbitrary browser-selected user ID.

Earnings permission is not required. Disconnect is idempotent and also invalidates unfinished attempts for this user/application.

Request

curl -X DELETE "$BMM_ORIGIN/api/connect/hosted/me" \
  -H "X-BMM-Client-ID: $BMM_CLIENT_ID" \
  -H "X-BMM-API-Key: $BMM_API_KEY" \
  -H "X-BMM-User-ID: $AUTHENTICATED_PARTNER_USER_ID"

Success response

json

{
  "disconnected": true
}

After disconnecting

Only show success after BMM confirms it. Revocation immediately prevents subsequent authorised reads and disables the attributed support link. It does not delete accounts, payments or financial history. Creators can also revoke in Share → Connected apps. Reconnecting requires fresh consent. Existing payment checkouts can still settle with their original attribution. Recovery checkouts require an active connection.

Errors

Status	Meaning
400	Invalid request or unavailable application.
401	Missing, invalid or rotated application credentials.
403	Application not approved, or required permission not granted.
429	Rate limited. Honour Retry-After when supplied and back off.
5xx	Temporary failure. Retry reads with backoff.

Errors contain {"error":"message"}. Do not match error text or cache private responses. Full error guide.

← All endpoints