Subscriptions

Reissue a subscription's access

curl -X POST https://api.subscriby.net/v1/subscriptions/$SUBSCRIPTION_ID/grants/reissue \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "resource_id": "c9e21f37-8a4b-4d56-b1e0-2f7c9d3a6e15" }'

The members page's Refresh invite links, for integrations. The grants the member holds are revoked (their personal invite links die) and the job that grants at purchase runs again, issuing fresh grants the bot sends to the member. resource_id is optional: name one resource of the plan to reissue it alone, leave it out to reissue every resource the subscription grants.

Answers 202 once the reissue is queued, where reissued counts the grants revoked; the fresh grants appear on the grants endpoint seconds later. Each revoked grant raises member.resource_reissued and each fresh one member.resource_added.

post/v1/subscriptions/{subscription}/grants/reissue

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/subscriptions/{subscription}/grants/reissue
  • Auth: HTTP bearer

Path parameters

subscriptionstring uuid required

The subscription, resolved by the route binder.

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Request body

resource_idstring uuid nullable

A resource the plan grants, to reissue it alone; omit it to reissue every resource. A resource the plan does not grant answers 404.

Response

202 with subscription_id, reissued and reissue_queued.

Example response

{
  "data": {
    "subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",
    "reissued": 2,
    "status": "reissue_queued"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.