# Insy Docs > Build on Insy — REST API, API keys, outbound webhooks and Sign in with Insy (OAuth 2.0). ## Docs - [Insy Help Center](https://docs.insy.io/): Guides for creators selling on Insy — set up your community or products, get paid, and grow. ## Getting started - [Getting started](https://docs.insy.io/getting-started): What Insy is, how to create your account, set up your public profile, and what Insy charges when you make a sale. - [Welcome to Insy — what it is and how it works](https://docs.insy.io/getting-started/welcome): Insy is a platform for selling access — paid communities, Telegram-gated groups and digital products. Here is what you can sell and how the journey works. - [Creating your account](https://docs.insy.io/getting-started/account): There is no password and no separate sign-up on Insy. Your account is created the first time you log in — by email link, Google, or Telegram. - [Setting up your profile](https://docs.insy.io/getting-started/profile): Your public profile on Insy — display name, @username, bio, avatar, social links, and the showcase that decides which communities and products appear on your page. - [Understanding fees](https://docs.insy.io/getting-started/fees): What Insy keeps on each sale — the platform commission, how it differs between card and crypto, the VAT added on card sales, and which costs are passed through to you. ## Communities & Telegram - [Communities & Telegram](https://docs.insy.io/communities): Create a paid community, price the access, connect your Telegram group, and keep members in sync as their access starts and ends. - [Create your paid community](https://docs.insy.io/communities/create): Fill in the handle, name, description, category and images that make up your community page — and learn how drafts, edits and deletion work. - [Pricing plans and how members pay](https://docs.insy.io/communities/pricing): Set the price for your community, choose monthly or lifetime access, offer more than one plan, and understand how renewals and reminders work. - [Connect your Telegram group](https://docs.insy.io/communities/telegram): Create your own Telegram bot, add it to your group as an admin, and let paying members join automatically — plus how to fix a bot that has stopped working. - [Managing members and expiry](https://docs.insy.io/communities/members): Roles, bans and the member cap, how access expires and members are removed, letting former members rejoin, and handing out free access with invite codes. ## Selling & payments - [Selling & payments](https://docs.insy.io/selling): Create a digital product, choose a price model, understand how buyers pay, and set up coupons, refunds and sales limits. - [Create a digital product](https://docs.insy.io/selling/create-product): Build a digital product on Insy — name, description, pictures, product type, and the one to five priced options buyers choose between. - [Choosing a price model](https://docs.insy.io/selling/pricing): Set each product option's price on Insy — one-time, subscription, free or pay-what-you-want — plus free trials and crossed-out "was" prices. - [How buyers pay](https://docs.insy.io/selling/payments): The ways buyers pay on Insy — card, BLIK and P24 through Stripe, crypto through CoinGate — the two supported currencies, and the Stripe account a paid product needs. - [Coupons, refunds and limits](https://docs.insy.io/selling/coupons-refunds): Discount coupons, how refunds work on Insy, sales limits, availability windows, waitlists and custom checkout fields. ## Integrations - [Integrations](https://docs.insy.io/integrations): Where to find the Integrations page for a community and for a digital product, which connections each one offers, and what the Inactive and Active badges really mean. - [Automatic invoices with Fakturownia and inFakt](https://docs.insy.io/integrations/invoicing): How to connect your own Fakturownia or inFakt account, what lands on the invoice Insy creates for each sale, and the cases where no invoice is created at all. - [Google Analytics and Meta Pixel](https://docs.insy.io/integrations/analytics): How to connect your own GA4 property and Meta pixel to a community or product, exactly which events Insy forwards, and why cookie consent decides whether anything arrives. - [Connecting a custom domain](https://docs.insy.io/integrations/custom-domain): How to point your own hostname at a product page — the DNS records Insy asks for, why the status only moves when you press Sync Status, and what your domain actually serves. ## Payouts - [Payouts](https://docs.insy.io/payouts): Understand your Insy balances, withdraw your earnings to a bank or a crypto wallet, and get discovered by new buyers. - [Your wallet](https://docs.insy.io/payouts/wallet): The two balances Insy keeps for you — a fiat clip-reward balance and a crypto balance — what is withdrawable now, and how to read your money history. - [Withdrawing crypto earnings](https://docs.insy.io/payouts/crypto-payouts): How to add a wallet address, why every crypto withdrawal is held for review, the hold window after a sale, and the network fee you have to leave room for. - [Getting paid in fiat](https://docs.insy.io/payouts/fiat-payouts): Connect a Stripe account and withdraw your PLN clip-reward balance — plus what happens when fiat withdrawals are paused platform-wide. - [Getting discovered](https://docs.insy.io/payouts/discovery): Request a spot on the explore page, understand how ranking and badges work, and handle the reviews that feed into both. ## Growth - [Growth](https://docs.insy.io/growth): Control how your pages look when they are shared, and pay other people a commission for bringing you buyers. - [SEO settings and link previews](https://docs.insy.io/growth/seo): What the four SEO fields change, which meta tags they overwrite, and the exact order Insy picks a share image — your upload, then the generated card, then a picture from the page. - [Affiliate program](https://docs.insy.io/growth/affiliate): How to set up an affiliate program on a community or product, what the two commission rates mean, how a referral is attributed, and how commissions get paid out. ## Clipping - [Clipping](https://docs.insy.io/clipping): Run a clipping campaign to get your content clipped everywhere, or earn by clipping other creators — how the two sides fit together on Insy. - [Run a clipping campaign](https://docs.insy.io/clipping/for-creators): Create a campaign, set the budget and the pay rate per 1,000 views, choose platforms and rules, approve or reject clips, top up or wind it down, and see where the spend comes from. - [Earn by clipping](https://docs.insy.io/clipping/for-clippers): Find a campaign, verify the social account you post from, submit your clips, understand how views are counted and what a clip is worth, and get paid. - [Clip rules and disputes](https://docs.insy.io/clipping/rules-and-disputes): How a clip gets approved or rejected, what makes a clip fail, and what happens when a clipper or a creator disagrees with a decision. ## For developers - [Insy for developers](https://docs.insy.io/developers): Build on Insy — sell access to paid communities, Telegram groups and digital products with a REST API, outbound webhooks and Sign in with Insy. - [Quickstart](https://docs.insy.io/developers/quickstart): Choose between the API key, OAuth and webhook integration surfaces, then make your first authenticated call to the Insy API. ### REST API - [REST API](https://docs.insy.io/developers/api): The Insy REST API is JSON over HTTPS, served from api.insy.io and authenticated with a server-side API key sent as a bearer token. - [API keys](https://docs.insy.io/developers/api/authentication): How Insy API keys look, how to get one, how to send them, and how the permission bitmask and community-role check decide what a key may do. - [Endpoints](https://docs.insy.io/developers/api/endpoints): Reference for the five Insy REST endpoints an API key can call — membership provisioning, Telegram invites and checks, hosted checkout and drop signups. - [Errors](https://docs.insy.io/developers/api/errors): HTTP status codes the Insy REST API returns, the two failure body shapes, and the usual causes behind 400, 401, 403, 404 and 409 responses. #### Reference - [Insy API](https://docs.insy.io/developers/api/reference) ##### Checkout API Key - [Start checkout session with external ID and custom URLs](https://docs.insy.io/developers/api/reference/checkout-api-key/buy-plan) ##### Drop Notification API Key - [Sign up for drop notification with auto-detected upcoming slot](https://docs.insy.io/developers/api/reference/drop-notification-api-key/signup) ##### Membership API Key - [Check if a Telegram user has an active membership in a community](https://docs.insy.io/developers/api/reference/membership-api-key/check-membership-by-telegram-user-id) - [Join a telegram community using an external ID](https://docs.insy.io/developers/api/reference/membership-api-key/join-telegram-community-external) - [Provision a community membership from an external sales funnel. Looks up / creates the user by email or telegramUserId, handles overlap with existing memberships, and is idempotent via externalOrderId.](https://docs.insy.io/developers/api/reference/membership-api-key/provision-external-membership) ##### OAuth - [Authorize](https://docs.insy.io/developers/api/reference/oauth/authorize) - [Memberships](https://docs.insy.io/developers/api/reference/oauth/memberships) - [Products](https://docs.insy.io/developers/api/reference/oauth/products) - [Public identity of an OAuth client, for the consent screen](https://docs.insy.io/developers/api/reference/oauth/get-public-client) - [Revoke](https://docs.insy.io/developers/api/reference/oauth/revoke) - [Token](https://docs.insy.io/developers/api/reference/oauth/token) - [Userinfo](https://docs.insy.io/developers/api/reference/oauth/userinfo) ### Webhooks - [Webhooks](https://docs.insy.io/developers/webhooks): Insy posts signed JSON to your endpoint when memberships, payments and digital product purchases change. Delivery is at-least-once and unordered. - [Events](https://docs.insy.io/developers/webhooks/events): The shared webhook envelope and the payload of all five Insy event types — membership, payment and digital product purchase events. - [Verifying signatures](https://docs.insy.io/developers/webhooks/verify): How to validate the X-Insy-Signature header — HMAC-SHA256 over the raw body, keyed with the secret as a literal string, compared in constant time. ### Sign in with Insy - [Sign in with Insy](https://docs.insy.io/developers/oauth): Let Insy users grant your application access to their memberships and products using the OAuth 2.0 authorization code flow. - [Login widget](https://docs.insy.io/developers/oauth/widget): Add Sign in with Insy to any page with a single script tag — a public OAuth client that runs PKCE in the browser and returns tokens to your code. - [Server-side flow](https://docs.insy.io/developers/oauth/server-side): The confidential-client OAuth 2.0 walkthrough for Sign in with Insy — authorize, exchange the code for tokens, call a resource endpoint, and refresh. - [PKCE and public clients](https://docs.insy.io/developers/oauth/pkce): How to run Sign in with Insy from a single-page app, a mobile app or anything else that cannot keep a client secret — using PKCE with S256. - [Scopes](https://docs.insy.io/developers/oauth/scopes): The two OAuth scopes Insy grants, what each one unlocks, how to request them, and why products.read is not what most people assume. - [Endpoint reference](https://docs.insy.io/developers/oauth/reference): Every Sign in with Insy endpoint — parameters, request and response examples, error codes, and the places Insy deviates from the OAuth RFCs.