# Subscriby Documentation > Machine-readable index of the Subscriby documentation site. > Base URL: https://docs.subscriby.net ## (root) - [Platform Introduction](https://docs.subscriby.net) — The complete guide to Subscriby — launching, running, and growing subscription-based communities on the platforms your members already use, with automated member management. ## account - [If You Can't Sign In](https://docs.subscriby.net/account/account-recovery) — Password reset, two-factor recovery codes, a connected platform as the fallback and support escalation, in the order to try them. - [Appearance](https://docs.subscriby.net/account/appearance) — Pick light mode, dark mode or your device's system preference for the creator dashboard. - [Deleting Your Account](https://docs.subscriby.net/account/delete-account) — What is removed and what stays when you close your account permanently, how to do it, and the safer alternatives to consider first. - [Your Creator Account](https://docs.subscriby.net/account) — Everything on your account: sign-in methods, two-factor authentication, passkeys, recovery options, notifications, language and sessions. - [Language & Region](https://docs.subscriby.net/account/language-region) — Choose the language Subscriby displays in and the timezone every dashboard, schedule and billing date is shown in. - [Email & Notifications](https://docs.subscriby.net/account/notifications) — Toggle communications, marketing, promotional and advertising emails and the weekly digest, while critical notices keep flowing. - [Passkeys](https://docs.subscriby.net/account/passkeys) — Register FIDO2 passkeys to sign in with a fingerprint, Face ID or a hardware key, then add, name and remove them. - [Profile](https://docs.subscriby.net/account/profile) — Keep the details on your creator account accurate for invoices, support and how your name appears to members. - [Browser Sessions](https://docs.subscriby.net/account/sessions) — See every device signed in to your account and sign out the ones you do not recognise. - [Signing In](https://docs.subscriby.net/account/sign-in) — Three ways in: email and password, a passkey, or an account on a connected platform, and how they combine on one account. - [Creating an Account](https://docs.subscriby.net/account/sign-up) — Register with an email address and a password, and optionally link the account you use on your community's platform from the first day. - [Signing In with a Connected Platform](https://docs.subscriby.net/account/social-login) — Link the account you hold on your community's platform to your email-first creator account, then use it to sign in and receive alerts. - [Two-Factor Authentication](https://docs.subscriby.net/account/two-factor-auth) — Add a six-digit code from Google Authenticator or any TOTP app to your sign-in, save your recovery codes, and recover if you lose the device. ## addons - [Coupons Addon](https://docs.subscriby.net/addons/coupons) — Unlock coupon codes for $5 a month or $50 a year: prices, worked examples, which payment methods can discount, and what removal does. - [Addons](https://docs.subscriby.net/addons) — How addons are billed, when you are charged, and what happens when you add, remove, upgrade or change billing cycle. - [Passes Addon](https://docs.subscriby.net/addons/passes) — Unlock Time-Limited Passes and Pass Series for $19 a month or $190 a year, with worked examples and what happens when you add or remove it. ## api - [Ability Catalog](https://docs.subscriby.net/api/v1/abilities) — Every ability string a token can carry, what enforces it on the API and the MCP server, and how to pick the right ones when minting. - [Authentication](https://docs.subscriby.net/api/v1/authentication) — Personal access tokens, ability scopes and tenant resolution for the REST API and the MCP server, and what the API will not accept. - [Error Codes](https://docs.subscriby.net/api/v1/errors) — The complete catalogue of error codes from api.subscriby.net and mcp.subscriby.net, their HTTP statuses and what to do about each. - [Idempotency](https://docs.subscriby.net/api/v1/idempotency) — Every POST, PATCH, PUT and DELETE takes an Idempotency-Key header so a retry never double-creates, double-mutates or double-charges. - [REST API](https://docs.subscriby.net/api/v1) — The versioned API at api.subscriby.net: every mutation the dashboard can make, scoped by a personal access token, for agents, Zapier, n8n and more. - [OpenAPI Specification](https://docs.subscriby.net/api/v1/openapi) — Where the machine-readable OpenAPI document lives, what it carries beyond paths, and how to load it into your tooling. - [Pagination](https://docs.subscriby.net/api/v1/pagination) — How list endpoints wrap data in a meta and links envelope, the 100-row page cap, and how to iterate a large result set. - [REST API Quickstart](https://docs.subscriby.net/api/v1/quickstart) — Mint a personal access token, call your first endpoint and receive your first signed webhook, end to end in under five minutes. - [Rate Limiting](https://docs.subscriby.net/api/v1/rate-limiting) — The named rate-limit buckets applied per token to the REST API, the MCP server and the webhook surface, and the headers that report them. - [Access Codes API](https://docs.subscriby.net/api/v1/reference/access-codes) — Access codes are pre-generated single-use subscription activations - [Activity API](https://docs.subscriby.net/api/v1/reference/activity) — Every mutation Subscriby performs, whether from the dashboard, the - [Alert Destinations API](https://docs.subscriby.net/api/v1/reference/alert-destinations) — An alert destination is a place your creator alerts go: one of the - [Analytics API](https://docs.subscriby.net/api/v1/reference/analytics) — Read-only analytics under /v1/analytics/ surface the same figures - [Billing API](https://docs.subscriby.net/api/v1/reference/billing) — Manage the creator's own Subscriby tier. Webhook-observable today; REST deferred. - [Broadcasts API](https://docs.subscriby.net/api/v1/reference/broadcasts) — A broadcast sends one message, through the project's connector, to - [Connectors API](https://docs.subscriby.net/api/v1/reference/connectors) — A Subscriby project runs on connectors: the platforms it gates - [Coupons API](https://docs.subscriby.net/api/v1/reference/coupons) — A coupon is one code many subscribers can redeem for money off at - [Creator Tasks API](https://docs.subscriby.net/api/v1/reference/creator-tasks) — A creator task is a grant no connector can give. - [Disaster Recovery API](https://docs.subscriby.net/api/v1/reference/disaster-recovery) — Everything the Disaster Recovery pages show a creator is readable - [Distribution API](https://docs.subscriby.net/api/v1/reference/distribution) — Every project exposes two public URLs: the subscriber portal and - [Groups API](https://docs.subscriby.net/api/v1/reference/groups) — A group is a named bundle of permissions on a team that several - [Identities API](https://docs.subscriby.net/api/v1/reference/identities) — A linked identity is an account you hold on a connector, tied to - [API Reference](https://docs.subscriby.net/api/v1/reference) — Every operation of the REST API, generated from the OpenAPI document and grouped by resource. - [Me API](https://docs.subscriby.net/api/v1/reference/me) — GET /v1/me is the first call a client makes. - [Members API](https://docs.subscriby.net/api/v1/reference/members) — Members are the project-scoped subscribers. - [Notifications API](https://docs.subscriby.net/api/v1/reference/notifications) — Every alert Subscriby sends a creator (a sale, a support backlog, - [Pass Windows API](https://docs.subscriby.net/api/v1/reference/pass-windows) — A pass window is one dated stretch of access on a kind: pass plan: - [Payment Methods API](https://docs.subscriby.net/api/v1/reference/payment-methods) — Every project configures one or more payment providers so - [Ping API](https://docs.subscriby.net/api/v1/reference/ping) — The one endpoint that needs no token. - [Plans API](https://docs.subscriby.net/api/v1/reference/plans) — A plan is what a project sells: the price, the currency, the - [Projects API](https://docs.subscriby.net/api/v1/reference/projects) — A project is the container for one membership business: its plans, - [Resources API](https://docs.subscriby.net/api/v1/reference/resources) — Resources are what a plan unlocks: a place a connector gates (a - [Roles API](https://docs.subscriby.net/api/v1/reference/roles) — A role is the permission set a collaborator holds on a team. - [Subscriptions API](https://docs.subscriby.net/api/v1/reference/subscriptions) — A subscription is one member's purchase of one plan: the row that - [Support Inbox API](https://docs.subscriby.net/api/v1/reference/support-inbox) — The support inbox is where a member who writes to your project bot - [Team Members API](https://docs.subscriby.net/api/v1/reference/team-members) — Team members are the humans who collaborate inside a team: the - [Teams API](https://docs.subscriby.net/api/v1/reference/teams) — Teams group creators, roles, and projects. - [Tokens API](https://docs.subscriby.net/api/v1/reference/tokens) — Personal access tokens are what authorize every REST and MCP call. - [Webhook Deliveries API](https://docs.subscriby.net/api/v1/reference/webhook-deliveries) — Every event Subscriby posts to one of your webhook endpoints is a - [Webhook Endpoints API](https://docs.subscriby.net/api/v1/reference/webhook-endpoints) — A webhook endpoint is a URL of yours that Subscriby posts events - [Webhook Events API](https://docs.subscriby.net/api/v1/reference/webhook-events) — A read-only polling endpoint that surfaces the most recent webhook - [Tenancy & Scopes](https://docs.subscriby.net/api/v1/tenancy-and-scopes) — Every read and write is scoped to one team, and scope entries on a token narrow it further to chosen projects. - [Versioning & Deprecation](https://docs.subscriby.net/api/v1/versioning-and-deprecation) — How the API is versioned under /v1, how new functionality is added, and how breaking changes are announced and retired. ## connectors - [Connectors](https://docs.subscriby.net/connectors) — How connectors work, which platforms are live today, what is on the roadmap and how to build a connector of your own. - [Connectors Marketplace](https://docs.subscriby.net/connectors/marketplace) — What the lanes and badges mean, how Notify me works, what a reserved connector's plan chip says and where the same list appears in the app. - [Connector Roadmap](https://docs.subscriby.net/connectors/roadmap) — Which connectors are live, which are on the way, which plans they will need, and what coming soon commits us to. - [Admin Commands](https://docs.subscriby.net/connectors/telegram/admin-commands) — Owner-only commands in your bot's chat, hidden from members: inspect a subscriber with /check or remove one with /ban, by Telegram ID or member UUID. - [Why Telegram](https://docs.subscriby.net/connectors/telegram/advantages) — Free hosting and unlimited bandwidth, reliable uptime, your choice of payment methods with direct settlement, and members who never leave Telegram. - [What Your Bot Can Do](https://docs.subscriby.net/connectors/telegram/bot-features) — Every feature the bot exposes to subscribers and to you: plans and checkout in chat, access codes, invite links, reminders, support and admin tools. - [Connect Your Telegram Bot](https://docs.subscriby.net/connectors/telegram/connecting) — Create a bot with @BotFather, paste its token into your project, and activate the connection that admits, removes and bills your members. - [Joining Through the Bot](https://docs.subscriby.net/connectors/telegram/for-members) — For subscribers: start the bot, pick a plan, pay, receive your invite links, manage renewals and set up account recovery without leaving Telegram. - [Create a Paid Channel](https://docs.subscriby.net/connectors/telegram/how-to-create-a-paid-channel) — Turn a private Telegram channel into a subscription: your own bot from @BotFather, two admin rights, a connected project, payment methods, a plan and a test purchase. - [Create a Paid Group](https://docs.subscriby.net/connectors/telegram/how-to-create-a-paid-group) — Set up a paid Telegram group with automated access: a private supergroup, your own bot with two admin rights, single-use invite links, plans, trials and the mistakes that leak access. - [Telegram Membership Bot](https://docs.subscriby.net/connectors/telegram) — How Subscriby runs a paid Telegram channel or group: connect your bot, link channels, admin commands, deep links and the webhook behind it all. - [How the Integration Works](https://docs.subscriby.net/connectors/telegram/integration) — What the Telegram Bot API integration gives you: automatic invites and removals, in-chat payments, renewal reminders and support, with no code. - [Create Your Account with Telegram](https://docs.subscriby.net/connectors/telegram/onboarding) — Sign up with Continue with Telegram or by email, link your Telegram account, and connect your first bot in a few minutes. - [Deep Links](https://docs.subscriby.net/connectors/telegram/operations) — Share your bot, open a plan, redeem an access code or run a command from one t.me link: every start parameter the bot accepts and how to build it. - [Recovering Your Telegram Account](https://docs.subscriby.net/connectors/telegram/recovering-your-account) — When Telegram bans the account you sign in with: switch to your backup account in one click or prove a new one through the bot, with a 24-hour undo. - [Replacing a Banned Bot](https://docs.subscriby.net/connectors/telegram/replacing-a-banned-bot) — Put a new bot or your standby bot in place without losing a single member chat, then tell members by Telegram, by email or with a CSV. - [Replacing Channels and Groups](https://docs.subscriby.net/connectors/telegram/replacing-channels-and-groups) — Hand the bot a replacement chat, re-admit every member automatically, remind the ones still outside, and undo within 24 hours. - [Sign in with Telegram](https://docs.subscriby.net/connectors/telegram/sign-in) — How Continue with Telegram works, what Telegram shares, how to link or unlink an account, and why email and passkeys stay available. - [Telegram Stars](https://docs.subscriby.net/connectors/telegram/stars) — Sell Telegram channel and group access for Stars (XTR): one-time in-chat payments that meet Apple and Google in-app rules, live only, no credentials. - [How the Bot Stays Connected](https://docs.subscriby.net/connectors/telegram/webhooks) — The webhook Subscriby registers on your bot, what it does for you automatically, and what to check when the bot goes silent. ## creators - [Broadcasts](https://docs.subscriby.net/creators/broadcasts) — Send one message through your project's bot to a chosen audience segment, including the holders of a single time-limited pass window. - [Generate Access Codes](https://docs.subscriby.net/creators/codes) — Create redeemable codes for free memberships, offline sales, giveaways, team access or influencer campaigns, with expiry rules, export and a quota. - [Connectors](https://docs.subscriby.net/creators/connectors) — Install the platforms your project runs on, connect and verify them, read their health, and uninstall one without losing your members' history. - [Coupon Codes](https://docs.subscriby.net/creators/coupon-codes) — Issue one code any number of subscribers can redeem for a percentage or fixed discount: capped, plan-restricted, scheduled, with an impact card. - [Dashboard & Analytics](https://docs.subscriby.net/creators/dashboard-analytics) — KPIs, charts, gauges and tables for your portfolio or one project, sliced by period, plan, status and payment method, exported as PDF, Excel or CSV. - [Exporting Data](https://docs.subscriby.net/creators/exporting-data) — Pull your access codes into Excel, Google Sheets, Airtable or a BI tool as CSV, on generation or later from the Access Codes page. - [Go-Live Checklist](https://docs.subscriby.net/creators/go-live-checklist) — Everything to check before you announce a paid community on Subscriby: account, project, connector rights, plans, live payments, portal, support and recovery. - [Creator Guide](https://docs.subscriby.net/creators) — Activate a plan, create a project, connect a platform, define what members unlock, take payments, sell plans and run your members day to day. - [Managing Members](https://docs.subscriby.net/creators/managing-members) — Browse, filter and inspect everyone who touched your project: leads, trialing members, customers and churned members, with their details. - [Managing Subscriptions](https://docs.subscriby.net/creators/managing-subscriptions) — Every subscription in your project with its status and payment history, filtered any way you need, with cancellation for active or trialing ones. - [Payment Methods](https://docs.subscriby.net/creators/methods) — Connect Stripe, PayPal, Razorpay, Paystack, Skrill, CoinPayments, CeyPay, access codes or a native method so your project can take subscriptions. - [Migrating From Another Tool](https://docs.subscriby.net/creators/migrating-from-another-tool) — Bring a paid community over from another membership tool: keep the same place, cover every paid period with an access code and let the old subscriptions run out. - [Pass Series](https://docs.subscriby.net/creators/pass-series) — One payment for a whole slate of dated passes drawn from your pass plans: ten match days, an eight-week course or a cohort, bought once. - [Subscription Plans](https://docs.subscriby.net/creators/plans) — Build the tiers members buy: price, billing cycle, trial days, the resources a plan unlocks and who is eligible to buy it. - [Creating a Project](https://docs.subscriby.net/creators/projects) — Set up the container for your plans, members, connectors and resources, and configure it before you connect a platform and start selling. - [Resources](https://docs.subscriby.net/creators/resources) — Add the places your connectors gate and the manual perks a plan grants, and decide what a subscriber actually gets when they pay. - [Share Your Project](https://docs.subscriby.net/creators/share) — Put your project in front of subscribers through your bot link, the hosted portal page, QR codes and embedded buttons. - [Activate Your Subscriby Subscription](https://docs.subscriby.net/creators/subscription) — Compare the three creator plans on projects, memberships, access codes, passes, teams and fees, then activate the one that fits your scale. - [Support Inbox](https://docs.subscriby.net/creators/support-inbox) — Members who write to your project bot land in one inbox; answer from the dashboard or straight from the platform's chat. - [Time-Limited Passes](https://docs.subscriby.net/creators/time-limited-passes) — Sell access to a window you schedule: buyers pay in advance, are admitted when it opens and removed when it closes, with no work on the day. - [All Transactions](https://docs.subscriby.net/creators/transactions) — The complete payment ledger: search, sort and filter every purchase, renewal, refund and failed charge, and open any payment for its full detail. ## disaster-recovery - [Active Disaster Prevention](https://docs.subscriby.net/disaster-recovery/active-disaster-prevention) — The Growth safeguards set up before anything happens: a backup account, a standby bot, standby places with a live mirror and automatic failover. - [Allowances and Support Review](https://docs.subscriby.net/disaster-recovery/allowances-and-support-review) — How the once-per-kind-per-90-days allowance is counted, what does and does not spend it, and what support audits before granting more. - [Connector Outages](https://docs.subscriby.net/disaster-recovery/connector-outages) — When a platform refuses your project's bot: sales freeze, access is protected, and members are compensated when the connector answers again. - [History and Undo](https://docs.subscriby.net/disaster-recovery/history-and-undo) — Every incident and recovery ever run, the roll call and reminder on each swap, and the undo buttons while their 24-hour window is open. - [How Detection Works](https://docs.subscriby.net/disaster-recovery/how-detection-works) — The probes that watch your bots, places and connected account, the failures that trigger an instant check, what opens an incident and how you hear. - [Disaster Recovery Program](https://docs.subscriby.net/disaster-recovery) — What happens when a platform bans the account you sign in with, the bot that serves a project or a place your plans grant, and how it comes back. - [Recovering Your Connected Account](https://docs.subscriby.net/disaster-recovery/recovering-your-account) — Move your sign-in, your alerts and your creator bot to a new account on the same platform, with the one-click backup switch on Growth. - [Replacing a Lost Place](https://docs.subscriby.net/disaster-recovery/replacing-places) — Hand the connector a replacement place, watch every member be re-admitted, remind the ones still outside and undo within 24 hours. - [Replacing a Lost Connection](https://docs.subscriby.net/disaster-recovery/replacing-your-connection) — Put a new bot in place without losing a single member chat, or switch to your standby bot, and tell members what happened. - [Swap & Grant Resource](https://docs.subscriby.net/disaster-recovery/swap-and-grant-resource) — Swap a channel or group for a new one from the Resources table with every member re-admitted, without spending a recovery allowance. - [What Your Members See](https://docs.subscriby.net/disaster-recovery/what-members-see) — Every message, notice and email a subscriber can receive while a recovery is open or after it completes, and what they are asked to do. ## fees - [Transaction Fees](https://docs.subscriby.net/fees) — Understanding Subscriby transaction fees and billing logic ## how-it-works - [How Subscriby Works](https://docs.subscriby.net/how-it-works) — End-to-end walkthrough of the Subscriby flow — creator setup, subscriber signup, automated member management, and the money path. ## integrations - [Building Custom Agents](https://docs.subscriby.net/integrations/custom-agents) — Build your own agent on the OpenAPI spec, a personal access token with narrow abilities, and outbound webhooks. - [Automations & Integrations](https://docs.subscriby.net/integrations) — Ship Subscriby into Zapier, n8n, Make, LangChain, Postman, Insomnia and any OpenAPI-aware toolkit, all on the same REST API and webhooks. - [LangChain](https://docs.subscriby.net/integrations/langchain) — Expose the REST API to LangChain agents in Python or TypeScript through the OpenAPI toolkit, with a personal access token. - [Make (Integromat)](https://docs.subscriby.net/integrations/make) — Drive Subscriby from Make scenarios with HTTP modules against the OpenAPI spec and webhook listeners for outbound events. - [n8n](https://docs.subscriby.net/integrations/n8n) — A verified n8n node with a trigger for every webhook event and an action node covering every REST endpoint, on Cloud and self-hosted. - [Postman / Insomnia](https://docs.subscriby.net/integrations/postman-insomnia) — Import the OpenAPI spec into Postman or Insomnia to explore every endpoint interactively with a personal access token. - [Zapier](https://docs.subscriby.net/integrations/zapier) — An instant trigger for every webhook event, an action for every write and a search for every read, on the Subscriby Zapier app. ## introduction - [What is Subscriby?](https://docs.subscriby.net/introduction) — A plain-English overview of the platform — who builds it, who uses it, what it does, and why it exists. ## mcp - [Async Jobs](https://docs.subscriby.net/mcp/v1/async-jobs) — How a long-running MCP tool returns at once with a job to poll, and how a client follows it to completion. - [MCP Authentication](https://docs.subscriby.net/mcp/v1/authentication) — How a client connects to the MCP server, by signing in with OAuth 2.1 or with a personal access token, and how every tool enforces its ability. - [Connecting ChatGPT Desktop](https://docs.subscriby.net/mcp/v1/connecting-chatgpt-desktop) — Configure ChatGPT's developer-mode connectors to work with Subscriby, by signing in or with a personal access token. - [Connecting Claude](https://docs.subscriby.net/mcp/v1/connecting-claude-desktop) — Add the Subscriby MCP server to claude.ai, Claude Desktop and Claude Code as a connector, by signing in or with a personal access token. - [Connecting Cursor](https://docs.subscriby.net/mcp/v1/connecting-cursor) — Configure Cursor's MCP support to use the Subscriby server, by signing in or with a personal access token. - [Connecting VS Code](https://docs.subscriby.net/mcp/v1/connecting-vscode-claude) — Add the Subscriby MCP server to VS Code or the Claude Code extension, by signing in or with a personal access token. - [MCP Server for AI Agents](https://docs.subscriby.net/mcp/v1) — Connect Claude, Cursor, ChatGPT or VS Code to mcp.subscriby.net over the Model Context Protocol and run your creator workflow in natural language. - [Prompting Guide](https://docs.subscriby.net/mcp/v1/prompting-guide) — Prompt patterns that respect rate limits, keep the blast radius small and keep the human in view when an LLM drives the MCP server. - [MCP Quickstart](https://docs.subscriby.net/mcp/v1/quickstart) — Add the Subscriby MCP server as a Claude connector, sign in, approve the connection and run your first tool call. - [Resources Reference](https://docs.subscriby.net/mcp/v1/resources-reference) — The seven read-only JSON resources the MCP server publishes so an agent can ground itself before it calls a tool. - [MCP Security](https://docs.subscriby.net/mcp/v1/security) — How OAuth connections and personal access tokens are scoped, revoked and audited, and what to do the moment a credential leaks. - [Tools Reference](https://docs.subscriby.net/mcp/v1/tools-reference) — Every MCP tool the Subscriby server exposes today, grouped by what it works on, with the ability each one enforces. - [Access Code Tools](https://docs.subscriby.net/mcp/v1/tools/access-code) — An access code is a pre-generated, single-use activation a creator hands out; redeeming it claims a pending subscription. - [Account Tools](https://docs.subscriby.net/mcp/v1/tools/account) — The account behind the token: who is acting, which team the session is scoped to and what it may do. - [Analytics & Reports Tools](https://docs.subscriby.net/mcp/v1/tools/analytics-and-reports) — Every figure the creator dashboard renders is readable here, from revenue and churn to the transaction list, computed by the same service layer, so an agent and the dashboard never disagree. - [Connector Tools](https://docs.subscriby.net/mcp/v1/tools/connectors) — A project runs on connectors: the platforms it gates access on, messages through and takes payments from. - [Coupon Tools](https://docs.subscriby.net/mcp/v1/tools/coupon) — A coupon is one code many buyers can redeem for money off at checkout, the multi-use counterpart of an access code. - [Creator Task Tools](https://docs.subscriby.net/mcp/v1/tools/creator-task) — A creator task is a grant no connector can hand over: a perk the creator delivers by hand once a purchase entitles a member to it. - [Disaster Recovery Tools](https://docs.subscriby.net/mcp/v1/tools/disaster-recovery) — Disaster Recovery is Subscriby's answer to a connector outage or a lost channel: what the probes found, what was recovered and whether it can still be undone. - [Member Tools](https://docs.subscriby.net/mcp/v1/tools/member) — Members are a project's subscribers, the people every payment is made for and every access grant resolves to. - [Observability Tools](https://docs.subscriby.net/mcp/v1/tools/observability) — Where to look when something did not happen: webhook endpoints and their deliveries, the activity log of every mutation, and the status of a job another tool queued. - [Payment Tools](https://docs.subscriby.net/mcp/v1/tools/payment) — A project sells through one or more payment providers, each connected in test or live mode. - [Plan Tools](https://docs.subscriby.net/mcp/v1/tools/plan) — Plans are what a project sells, and every plan has a kind that decides its shape: a subscription that renews on a cycle, a pass that sells dated windows, or a series that sells a slate of windows at once. - [Project Tools](https://docs.subscriby.net/mcp/v1/tools/project) — A project is the container for one membership business: its plans, members, payment methods, resources and connectors. - [Resource Tools](https://docs.subscriby.net/mcp/v1/tools/resource) — A resource is what a plan unlocks: a place a connector gates, or a perk tracked by hand. - [Role & Group Tools](https://docs.subscriby.net/mcp/v1/tools/roles-and-groups) — A role is the permission set one collaborator holds; a group is a bundle several collaborators share. - [Subscription Tools](https://docs.subscriby.net/mcp/v1/tools/subscription) — A subscription is one member's purchase of one plan, and it is never created through a tool: checkout and access codes do that. - [Support Tools](https://docs.subscriby.net/mcp/v1/tools/support) — The support inbox holds one durable conversation per member and channel, the saved replies a team answers with, and the project's support settings. - [Team Member Tools](https://docs.subscriby.net/mcp/v1/tools/team-members) — Team members are the people who collaborate inside a team, distinct from a project's members. - [Team Tools](https://docs.subscriby.net/mcp/v1/tools/team) — A team groups creators, roles and projects, and every token is scoped to exactly one. - [Token Tools](https://docs.subscriby.net/mcp/v1/tools/tokens) — Personal access tokens authorise every REST and MCP call, and the plaintext value exists exactly once. - [MCP Troubleshooting](https://docs.subscriby.net/mcp/v1/troubleshooting) — Common MCP failure modes, from a client that cannot connect to a tool that refuses an ability, and how to resolve each. ## payments - [Access Codes](https://docs.subscriby.net/payments/access-codes) — Generate redeemable codes that unlock a plan without a gateway: offline sales, giveaways, migrations. One-time activation, with a quota per plan. - [CeyPay](https://docs.subscriby.net/payments/ceypay) — Connect CeyPay to take USDT on five chains with LKR settlement for Sri Lankan creators; one-time charges only, live and test modes. - [Choosing a Payment Provider](https://docs.subscriby.net/payments/choosing-a-provider) — Two questions decide it: do you need automatic recurring billing, and where do your subscribers live? A short decision tree across all nine providers. - [CoinPayments](https://docs.subscriby.net/payments/coinpayments) — Take Bitcoin, Ethereum, Litecoin and USD stablecoins across 18 coins and chains through CoinPayments: one-time, irreversible, live and test modes. - [Currency Conversion](https://docs.subscriby.net/payments/currency-conversion) — Every price converts through USD as the pivot with cached exchange rates: what subscribers actually pay, when rates refresh and how crypto is handled. - [Payment Methods](https://docs.subscriby.net/payments) — Stripe, PayPal, Skrill, CoinPayments, Paystack, Razorpay, CeyPay, native payments and access codes compared: regions, currencies, recurring, crypto. - [Native Payment Methods](https://docs.subscriby.net/payments/native-payments) — A connector can sell your plans with its platform's own in-app payment: no redirect, no card entry, one-time, priced in the platform's currency. - [PayPal](https://docs.subscriby.net/payments/paypal) — Connect a PayPal Business account to take payments in 24 currencies across 200+ countries, with automatic recurring billing for subscriptions. - [Paystack](https://docs.subscriby.net/payments/paystack) — Connect Paystack for card, bank transfer, USSD and mobile money in Nigeria, Ghana, Kenya, South Africa and more, with recurring billing. - [Razorpay](https://docs.subscriby.net/payments/razorpay) — Connect Razorpay to take UPI, netbanking, wallets and Indian cards, plus 100+ currencies abroad, with recurring billing through UPI AutoPay. - [Skrill](https://docs.subscriby.net/payments/skrill) — Connect Skrill to take one-time card and wallet payments from 131 countries in 42 currencies; recurring plans stay on another provider. - [Stripe](https://docs.subscriby.net/payments/stripe) — Connect Stripe through Stripe Connect for cards in 138+ currencies, automatic renewals, direct charges and plans that sync as products and prices. ## questions - [Common Questions](https://docs.subscriby.net/questions) — Frequently asked questions about Subscriby ## quickstart - [Quickstart Guide](https://docs.subscriby.net/quickstart) — From a fresh Subscriby account to your first paid membership, in about 10 minutes. ## reference - [Glossary](https://docs.subscriby.net/reference/glossary) — Plain-English definitions for every Subscriby term: project, plan, resource, handle, pass, connector and many more. - [Status Reference](https://docs.subscriby.net/reference/status-codes) — What each colour-coded status pill means: subscription statuses, member statuses and payment statuses, in plain language. - [Troubleshooting](https://docs.subscriby.net/reference/troubleshooting) — Quick fixes for the cross-cutting issues creators and subscribers hit most, with links to the topic-specific pages. ## sdk - [Data Rules](https://docs.subscriby.net/sdk/v1/building/data) — Which tables a connector may create, which it may never touch, and how the core points at a connector's own rows. - [Getting Started](https://docs.subscriby.net/sdk/v1/building) — The layout of a connector package, the service provider that wires it in, and the ports every connector binds. - [Listing and Review](https://docs.subscriby.net/sdk/v1/building/listing) — The listing block the marketplace renders, the marketing words the public site borrows, the badges Subscriby stamps and the review checklist. - [Publishing a Connector](https://docs.subscriby.net/sdk/v1/building/publishing) — Versioning the package and the manifest, the SDK constraint, translations, the review, how Subscriby installs a connector and how it moves lanes. - [Testing a Connector](https://docs.subscriby.net/sdk/v1/building/testing) — The fakes the SDK ships, their assertions, what a connector's suite covers port by port, and how the conformance kit runs against a package. - [Beyond the kit](https://docs.subscriby.net/sdk/v1/conformance/beyond-the-kit) — What Subscriby's own suite checks that the kit cannot from outside a package — isolation in both directions, translation parity, skeleton parity — and what review reads for. - [Capability rules](https://docs.subscriby.net/sdk/v1/conformance/capability-rules) — The seven rules that run only when a port is bound — resource kinds for access control, commands and relay modes against the manifest, recovery vocabulary and readiness, the portal button, native provider keys, the migrator's reports. - [Inbound, identity and slots](https://docs.subscriby.net/sdk/v1/conformance/inbound-identity-slots) — The three rules that hand the connector something empty and expect it to cope — an empty JSON request, an envelope with nothing in it, and a well-formed slot list. - [Conformance Kit](https://docs.subscriby.net/sdk/v1/conformance) — The suite every connector passes before review — what "passes the kit" means, how it runs, how a rule fails, the report it returns, and the twenty-three rules grouped by what they check. - [Manifest rules](https://docs.subscriby.net/sdk/v1/conformance/manifest-rules) — The five rules about connector.json — the key, the SDK constraint, the listing links, the resource kinds, and that the registered manifest is what the file on disk says. - [Migration rules](https://docs.subscriby.net/sdk/v1/conformance/migration-rules) — The one rule that reads a package's migrations — every table created carries the connector's prefix and no core table is touched — and exactly how the sources are scanned. - [Ports and forms](https://docs.subscriby.net/sdk/v1/conformance/ports-and-forms) — The three rules about what is bound and what the forms declare — the seven required ports, the install form, the settings form. - [Rendering and failures](https://docs.subscriby.net/sdk/v1/conformance/rendering-and-failures) — The three rules that exercise the TextRenderer and the FailureClassifier with real inputs — plain text, the canonical sample, an arbitrary throwable and an arbitrary value. - [Alerts](https://docs.subscriby.net/sdk/v1/core-api/alerts) — Where a creator's alerts go, as far as a connector may ask or change it — the one switch for the account in front of the connector, and what the core keeps to itself. - [Creators](https://docs.subscriby.net/sdk/v1/core-api/creators) — Creator accounts as a connector may create them — the one call that turns a connector's sign-up form into an email-first account with a linked identity, and the two ways it is refused. - [Grants](https://docs.subscriby.net/sdk/v1/core-api/grants) — The access ledger as a connector may read and write it — finding a grant by id or by the reference you issued, what a summary tells you, and when a connector records a grant itself. - [Identities](https://docs.subscriby.net/sdk/v1/core-api/identities) — The identity rows and who holds them — finding an account, recording it, linking it to a creator or a member, the handshake that proves possession, and the two lookups that turn an account into a person. - [Core API](https://docs.subscriby.net/sdk/v1/core-api) — The contracts a connector calls into the core — how they are bound, the records and refs that cross them, the idempotency every write keeps, the exceptions, and what the nine contracts cover. - [Installations](https://docs.subscriby.net/sdk/v1/core-api/installations) — The installation rows as a connector may read and write them — finding by id, platform id or storage ref, listing a project's or the platform's, recording one, recording a health verdict, forgetting one. - [Recovery](https://docs.subscriby.net/sdk/v1/core-api/recovery) — What the application keeps ready for a project's recovery, as a connector may read it — the coverage object behind the readiness checklist — and the two places a connector files, a standby and a replacement, through the actions the dashboard runs. - [Resources](https://docs.subscriby.net/sdk/v1/core-api/resources) — The resource rows as a connector may read them, and the one write — selling access to a place a creator picked — with its idempotency, its authorisation, its refusals and what the core announces. - [Spaces](https://docs.subscriby.net/sdk/v1/core-api/spaces) — The space rows as a connector may read and write them — finding a place, recording every place the installation learns about, and pointing a resource at one. - [Support](https://docs.subscriby.net/sdk/v1/core-api/support) — The support inbox as a connector feeds it and answers from it — filing a member's message, sending the acknowledgement the core says is due, handing the core a creator's answer written on the platform, finding the thread a relay message or a relay-space thread belongs to, and recording the space a project relays into. - [Connectors for Developers](https://docs.subscriby.net/sdk/v1) — What a connector is, what the core provides, and how a Composer package on the connector SDK becomes a connector on the marketplace. - [capabilities](https://docs.subscriby.net/sdk/v1/manifest/capabilities) — What a connector can do — the fourteen capabilities, the port each one binds, the group it is shelved under, which are official-only, and which a creator may switch off per installation. - [Identity](https://docs.subscriby.net/sdk/v1/manifest/identity) — key, name, version, sdk and vendor — what each is used for, the patterns they must match, and the SDK constraint syntax the registry understands. - [connector.json](https://docs.subscriby.net/sdk/v1/manifest) — The one file that says what a connector is, what it can do, how it talks and how the marketplace presents it — where it lives, how it is read, and a complete example. - [install](https://docs.subscriby.net/sdk/v1/manifest/install) — How a creator connects the connector — the install mode, the scopes, and the field specification the install and settings forms are declared with. - [listing](https://docs.subscriby.net/sdk/v1/manifest/listing) — What the marketplace shows — category, tagline, overview, screenshots, links, dates — plus the words the marketing site borrows, the button the member portal shows and the copy that makes the connector's page a search landing page. - [management_commands](https://docs.subscriby.net/sdk/v1/manifest/management-commands) — The core's in-chat admin command catalogue — every command, what it lets a creator do, and how a connector declares the subset its surface renders. - [messaging](https://docs.subscriby.net/sdk/v1/manifest/messaging) — The platform's message limits — length, buttons, callback data and formatting — and exactly where the core enforces each before a message reaches the connector. - [pacing](https://docs.subscriby.net/sdk/v1/manifest/pacing) — How fast the platform lets an installation send — the three intervals, the rate limiter the core registers from them, and which jobs read each value. - [recovery](https://docs.subscriby.net/sdk/v1/manifest/recovery) — Which Disaster Recovery facets a connector performs — the five flags, the RecoverySupport methods behind each, and how the block and the recovery capabilities work together. - [relay_modes](https://docs.subscriby.net/sdk/v1/manifest/relay-modes) — The support relay modes a connector offers — what a mode is, the two the core knows today, and how the manifest and the SupportRelay port must agree. - [resource_kinds](https://docs.subscriby.net/sdk/v1/manifest/resource-kinds) — Each kind of place a connector can gate — its labels, its icon, how access to it is granted, which plan shapes it sells, and whether it supports early admission, mirroring and in-place upgrades. - [AccessController](https://docs.subscriby.net/sdk/v1/ports/access-controller) — Giving and taking away access to a place — grant, revoke, revokeReference, admit, membership, announce and reconcile, the idempotency each must keep, and every core path that calls them. - [FailureClassifier](https://docs.subscriby.net/sdk/v1/ports/failure-classifier) — Reading why the platform refused a call — the seven kinds the core acts on, what each makes the core do, and how to map a platform's error vocabulary onto them. - [IdentityResolver](https://docs.subscriby.net/sdk/v1/ports/identity-resolver) — Who an inbound event is from, what the platform knows about an account and whether an installation can reach it — resolving, describing, adopting and reaching identities, and the line between what the connector says and what the core decides. - [InboundGateway](https://docs.subscriby.net/sdk/v1/ports/inbound-gateway) — Turning what the platform sends into authenticated, deduplicated events — the four methods, the InboundEnvelope, and exactly what the core's inbound gate does before and after your route runs. - [Ports](https://docs.subscriby.net/sdk/v1/ports) — The sixteen interfaces the core calls on a connector — which are required, which a capability binds, which are optional, the value objects that cross them, and the rules every implementation shares. - [InstallationLifecycle](https://docs.subscriby.net/sdk/v1/ports/installation-lifecycle) — Connecting, verifying, describing and disconnecting an installation on the platform — the eight methods, the value objects they exchange, and how the Connect dialog, the Verify button and the deep links drive them. - [ManagementSurface](https://docs.subscriby.net/sdk/v1/ports/management-surface) — The creator's in-chat admin surface over the core's command catalogue — declaring the commands, handling events, rendering command buttons, and calling the same actions the dashboard calls. - [Messenger](https://docs.subscriby.net/sdk/v1/ports/messenger) — Sending the core's messages through a connector — send, edit, delete and sendFile, the Message and Recipient objects, and everything the core checks before your port is called. - [PortalLoginMethod](https://docs.subscriby.net/sdk/v1/ports/portal-login-method) — Signing a member into the portal through the platform — the button, the handshake the core mints, how the connector completes it from its inbound side, and what the member sees. - [ProvidesPaymentMethods](https://docs.subscriby.net/sdk/v1/ports/provides-payment-methods) — Payment methods that exist only because of a platform — the NativePaymentProvider contract, why the capability is official-only, and how the core shows, sets up and rates a native currency. - [RecoverySupport](https://docs.subscriby.net/sdk/v1/ports/recovery-support) — What the Disaster Recovery Program needs a connector to witness and do — vocabulary, readiness, the three probes, standby installations, failover, mirroring and identity relinks, facet by facet. - [RegistersCreators](https://docs.subscriby.net/sdk/v1/ports/registers-creators) — Creating a creator account from inside the platform — where the sign-up starts, the conversation the connector runs, and the Core API call that creates the email-first account. - [SettingsSchema](https://docs.subscriby.net/sdk/v1/ports/settings-schema) — The install and settings forms as data — when the manifest binds the port for you, when to write your own, and how the Field objects reach the dashboard, the API and the apps. - [SpaceCatalog](https://docs.subscriby.net/sdk/v1/ports/space-catalog) — How a creator picks a place to gate and whether the installation controls it — link requests by purpose, instructions, diagnosis, and what the SDK does not yet let a third party complete. - [SupportRelay](https://docs.subscriby.net/sdk/v1/ports/support-relay) — Carrying a support conversation between a member and a creator over the platform — relay modes, replies, group threads and attachments, and where the inbox stays. - [TextRenderer](https://docs.subscriby.net/sdk/v1/ports/text-renderer) — Turning the core's canonical HTML into what one platform accepts — the eight tags, what a renderer must keep, and how HTML, Markdown and plain-text platforms each do it. - [UiSlots](https://docs.subscriby.net/sdk/v1/ports/ui-slots) — The connector's contributions to the core's UI slots — the eighteen slots and what each renders, the SlotContribution and SlotContext objects, the placeholder rule, and what a contribution may read. - [1. The package](https://docs.subscriby.net/sdk/v1/tutorial/01-package) — Start the Agora connector — composer.json, the service provider, a Connector class that binds nothing yet, configuration, and the HTTP client every port will share. - [2. The manifest](https://docs.subscriby.net/sdk/v1/tutorial/02-manifest) — Write connector.json for Agora — every block with the decision behind it, and a first test that validates the file exactly as the application will at boot. - [3. Installation](https://docs.subscriby.net/sdk/v1/tutorial/03-installation) — Implement InstallationLifecycle for Agora — validate the key with /me, register the webhook, keep the forum row, verify, disconnect, and build the links a member opens. - [4. Webhooks and identities](https://docs.subscriby.net/sdk/v1/tutorial/04-inbound) — Implement InboundGateway and IdentityResolver for Agora — verify the HMAC signature, decode events into envelopes with stable idempotency keys, resolve the actor, and write the route the core's gate protects. - [5. Messages](https://docs.subscriby.net/sdk/v1/tutorial/05-messages) — Implement TextRenderer, Messenger and FailureClassifier for Agora — canonical HTML to BBCode, private messages without buttons, reply keywords for actions, and a classifier table for the forum's refusals. - [6. Boards and access](https://docs.subscriby.net/sdk/v1/tutorial/06-boards) — Implement SpaceCatalog and AccessController for Agora — let a creator pick a board, record it as a space, add and remove members as grants, announce access, reconcile, and mark the one step the SDK cannot finish yet. - [7. Portal sign-in and probes](https://docs.subscriby.net/sdk/v1/tutorial/07-portal-login) — Implement PortalLoginMethod and RecoverySupport for Agora — the sign-in button, the handshake a member completes by private message, and the three probes behind the health badges. - [8. Slots and translations](https://docs.subscriby.net/sdk/v1/tutorial/08-slots-and-translations) — Fill the install slot with a walkthrough beside the form, ship its placeholder, and give every string the connector shows its ten translations. - [9. Tests and the kit](https://docs.subscriby.net/sdk/v1/tutorial/09-tests) — Assemble the Agora connector's test suite — the three checks that need no application, the port tests against a faked forum, characterisation snapshots, the core paths through the fakes, and running the conformance kit. - [10. Ship it](https://docs.subscriby.net/sdk/v1/tutorial/10-ship) — Take the Agora connector from green tests to a reviewed connector — the listing as creators will read it, the review checklist item by item, versioning, and what happens after Subscriby installs it. - [From Zero to a Forum Connector](https://docs.subscriby.net/sdk/v1/tutorial) — Build a complete Subscriby connector for an imaginary forum with private boards, chapter by chapter — package, manifest, installation, webhooks, messages, boards, portal sign-in, slots, tests, and shipping. ## subscribers - [Billing History](https://docs.subscriby.net/subscribers/billing-history) — Where every payment you made on a creator's project is listed, what each source shows, and where to get a formal receipt. - [Cancel Your Subscription](https://docs.subscriby.net/subscribers/cancel-subscription) — Cancel from the portal or the bot at any time, keep your access until the period ends, and resubscribe later if you change your mind. - [Choosing a Plan](https://docs.subscriby.net/subscribers/choosing-a-plan) — What each plan type means before you sign up: recurring, one-time, time-limited pass, pass series, lifetime and trial, and what each gives you. - [Contacting Support](https://docs.subscriby.net/subscribers/contacting-support) — Message the creator of a membership from the same bot you subscribed through; your message lands in their support inbox. - [Member Guide](https://docs.subscriby.net/subscribers) — Subscribe to a community that runs on Subscriby, manage your membership from the bot or the portal, and get help when something goes wrong. - [Making Payments](https://docs.subscriby.net/subscribers/making-payments) — What to expect when you pay for a plan, provider by provider: cards, PayPal, Skrill, crypto, Paystack, Razorpay, CeyPay and in-app payments. - [Manage Your Subscription](https://docs.subscriby.net/subscribers/manage-subscription) — Find your active subscription in the portal or the bot, verify your access, review payments and see which actions you can take. - [On Your Community's Platform](https://docs.subscriby.net/subscribers/on-the-platform) — Start the community's bot, pick a plan, pay, receive your access, manage your membership and set up recovery without leaving the platform. - [On the Web Portal](https://docs.subscriby.net/subscribers/portal) — Every project has a hosted portal: browse plan benefits, sign in, subscribe, protect your subscriptions and review your payments in a browser. - [Redeem an Access Code](https://docs.subscriby.net/subscribers/redeem-access-code) — Turn a code a creator gave you into an active subscription without paying, from the bot or the web portal, and see what the code unlocks. - [Redeem a Coupon Code](https://docs.subscriby.net/subscribers/redeem-coupon-code) — Type a creator's discount code at checkout in the portal or the bot and see the new total before you pay. - [Trial Memberships](https://docs.subscriby.net/subscribers/trial-memberships) — The two kinds of trial, when you are eligible, when a trial ends and what happens to your access and billing afterwards. - [Troubleshooting](https://docs.subscriby.net/subscribers/troubleshooting) — Fixes for the problems members hit most: failed payments, a bot that does not answer, missing group access and sign-in trouble. - [Using a Pass Series](https://docs.subscriby.net/subscribers/using-a-pass-series) — Your season-ticket timetable, how each date lets you in and out on its own, and what happens when one date is cancelled. - [Using a Pass](https://docs.subscriby.net/subscribers/using-a-pass) — Joining the queue, when access opens and ends, how you are admitted and removed automatically, and what to do if the window changes. ## subscriptions - [Subscriptions](https://docs.subscriby.net/subscriptions) — Learn about the Subscriby platform subscriptions ## teams - [Ability Reference](https://docs.subscriby.net/teams/abilities) — The complete list of permissions you can grant through roles or groups, what each governs, and how permission strings are built. - [Create a Team](https://docs.subscriby.net/teams/create-team) — Set up a team so several people can work on your projects, then invite them and assign roles. - [Groups](https://docs.subscriby.net/teams/groups) — Define ad-hoc permission collections for specific members and layer extra access on top of their roles. - [Teams & Roles](https://docs.subscriby.net/teams) — Invite collaborators to run your projects with permissions you define, on the Growth, Enterprise and Custom plans. - [Invite Team Members](https://docs.subscriby.net/teams/invite-members) — Send email invitations, assign a starting role, manage pending invitations and remove members who leave. - [Roles](https://docs.subscriby.net/teams/roles) — Bundle permissions into named roles such as Editor, Billing Admin or Support and assign them to team members. ## webhooks - [access_code.* events](https://docs.subscriby.net/webhooks/v1/events/access-code) — Access-code batch generation, redemption, and expiry. - [billing.* events](https://docs.subscriby.net/webhooks/v1/events/billing) — The creator's own Subscriby subscription tier: trial conversion, - [broadcast.* events](https://docs.subscriby.net/webhooks/v1/events/broadcast) — Message broadcast lifecycle: when a send starts, and what it delivered. - [connector.* events](https://docs.subscriby.net/webhooks/v1/events/connector) — A project's connectors as they are installed, connected, verified, - [coupon.* events](https://docs.subscriby.net/webhooks/v1/events/coupon) — Coupon code lifecycle and redemption. - [creator_task.* events](https://docs.subscriby.net/webhooks/v1/events/creator-task) — A hand-arranged perk a subscriber bought becomes a task for the - [group.* events](https://docs.subscriby.net/webhooks/v1/events/group) — Groups bundle collaborators for access control: a named permission - [Event Reference](https://docs.subscriby.net/webhooks/v1/events) — Every outbound webhook event, generated from the OpenAPI document and grouped by family. - [member.* events](https://docs.subscriby.net/webhooks/v1/events/member) — Member (subscriber) lifecycle events. - [pass_series.* events](https://docs.subscriby.net/webhooks/v1/events/pass-series) — Season-ticket lifecycle: bought, each date completing, dates added - [pass.* events](https://docs.subscriby.net/webhooks/v1/events/pass) — Time-limited pass access window lifecycle: opened, closed, - [payment.* events](https://docs.subscriby.net/webhooks/v1/events/payment) — Payment lifecycle: succeeded, failed, pending, refunded. - [plan.* events](https://docs.subscriby.net/webhooks/v1/events/plan) — Fires on every change to a plan's state, pricing or storefront position. - [project.* events](https://docs.subscriby.net/webhooks/v1/events/project) — Project lifecycle, resource link / unlink, payment method changes. - [recovery.* events](https://docs.subscriby.net/webhooks/v1/events/recovery) — The Disaster Recovery ledger as it moves: incidents opening and - [role.* events](https://docs.subscriby.net/webhooks/v1/events/role) — Role create, update and delete. - [subscription.* events](https://docs.subscriby.net/webhooks/v1/events/subscription) — Every transition across the subscription statuses, plus upgrade / downgrade. - [support.* events](https://docs.subscriby.net/webhooks/v1/events/support) — Member support inbox: conversations opened, replied to, assigned - [team.* events](https://docs.subscriby.net/webhooks/v1/events/team) — Team creation, rename, deletion, and membership changes. - [Outbound Webhooks & Events](https://docs.subscriby.net/webhooks/v1) — Event-driven HTTPS notifications from Subscriby to your server, Zapier or anything that takes JSON over POST, with retries and replay. - [Webhooks Quickstart](https://docs.subscriby.net/webhooks/v1/quickstart) — Register a target, subscribe to an event, receive a signed payload, verify it and respond 200, end to end. - [Retries & Delivery](https://docs.subscriby.net/webhooks/v1/retries-and-delivery) — The exponential back-off schedule, dead-lettering, the auto-disable threshold and how to replay a failed delivery. - [Webhook Security](https://docs.subscriby.net/webhooks/v1/security) — Secret rotation, replay windows and what to trust on an inbound delivery, so nothing can spoof or replay a Subscriby event. - [Signature Verification](https://docs.subscriby.net/webhooks/v1/signature-verification) — HMAC-SHA256 verification of every delivery's SB-Signature header, in a Stripe-compatible scheme, and how rotation replaces the secret. - [Testing & Debugging Webhooks](https://docs.subscriby.net/webhooks/v1/testing-and-debugging) — Fire a test payload, read the delivery log and retry a failed delivery by hand, without waiting for the production trigger.