Version
GET

Get your partnership

/v1/me/partner in the Partner Program API.

curl https://api.subscriby.net/v1/me/partner \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

Where you stand, whole. status is applied while Subscriby reviews the application, active once approved, rejected with reapply_available_at when it was declined, or suspended. Until approval the computed parts are null: there is no code, no links, no commission_percent, no balance.

Once approved:

  • code is the seven-character partner code and links.web the address to hand out; links.connectors carries one deep link per connector whose bot signs creators up, each opening the sign-up conversation with the code attached.
  • commission_percent is the rate a creator who converts from now on is locked to, as a decimal string with two places. It is a ladder: base_percent plus commitment_points (the verified promotion commitments) plus volume_points (the volume tiers reached at paying_referrals), capped at max_percent; next_tier_at and next_tier_points say what the next tier takes and adds. A referral keeps the rate it was promised at conversion; a raise reaches every referral still inside its commission period, a drop only new conversions.
  • referrals tallies the creators brought in by state, and balance carries the ledger's sums as decimal strings with four places in currency: pending (inside the hold), payable (approved and not yet settled, clawbacks netted), credited, paid and earned (all of them together).
  • commitments lists every promotion commitment with its proof state; a commitment is made and its proof submitted on the dashboard or in the bot, where the rules are explained.
GET
/v1/me/partner

Requires ability

The token must hold this ability, or the call is refused with 403.

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken
AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Responses

200OK

The partner object; 404 RESOURCE_NOT_FOUND until the caller applies.

401Unauthorized

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

403Forbidden

The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.

404Not found

Until the caller applies.

429Too many requests

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

How is this guide?

Last updated on