snipy.dev

A platform you can build on

A REST API for links and QR codes with least-privilege scoped keys, an OpenAPI reference, and a non-executing playground — so Snipy fits the systems you already run.

REST API

Create, read, update, and delete links and QR codes over a versioned REST API — the same engine the dashboard runs on, so behavior and limits match exactly.

Least-privilege scoped keys

Every key carries an explicit set of scopes; each endpoint requires exactly one. A key with no scopes authorizes nothing — grant only what an integration needs.

OpenAPI reference & playground

A machine-readable OpenAPI 3.1 spec generated from the live route registry, plus a request playground that previews the exact request and a sample response.

Playground

Try the API — nothing executes

Pick an endpoint to see the request shape and an illustrative sample response. Safe preview only — no calls leave your browser.

Scope: links:readList links
Request
curl -X GET https://api.snipy.com/v1/links \
  -H "Authorization: Bearer snipy_live_..."
The 5 scopes
links:readlinks:writeqr:readqr:writestats:read
Ecosystem

Build the connection you need

An open REST API, signed webhooks and embeds. Stripe Connect handles payouts; one-click app connectors are not part of this release.

StripePayments

Payouts run through Stripe Connect, and Stripe handles the card details — it is the commerce spine, not an optional add-on.

REST APIBuild

Scoped API keys over the /v1 endpoints for links and QR, with an OpenAPI document you can generate a client from.

Signed webhooksBuild

10 event types, each delivery signed and replayable, so your own service can react to what happens in Snipy.

EmbedsBuild

Bio blocks, pages and forms render chromeless on your own site, so a CMS needs no plugin to host them.

One-click app integrations are not in this release

Snipy ships no connector for Zapier, Make, Slack, HubSpot, Notion, WordPress or any other third-party app, and the dashboard says the same thing: its Integrations page shows no connections and offers no connect button, because there is nothing behind one yet. Anything offering a “Snipy integration” for those tools today is not ours.

The API, the webhooks and the embeds above are how you connect Snipy to the rest of your stack in the meantime — the same surface a connector would be built on. See the developer platform.

There is no third-party app directory to show yet. This page will list apps built on the Snipy API once they exist and we can name them honestly — it will not list examples of what one might look like.