Swipefast Developers

Everything your account can do,
from code.

Read your products and orders, record sales from your own systems, pull your numbers, and get every event pushed to you as it happens. One key, plain JSON, no SDK required.

API reference

6 endpoints, each with a live try-it runner.

Webhooks

8 events, pushed to any URL as JSON.

Built for AI agents

llms.txt and an OpenAPI 3.1 spec, generated from the same source as this page.

Authentication

Every request carries your API key in the Authorization header. Your key is on your Settings page — it works like a password, so keep it out of client-side code you ship to buyers.

Authorization: Bearer sf_live_your_key_here

Three requests to see it work

List your products, read one product’s numbers, then record a sale:

# 1. What am I selling?
curl https://swipefast.jacob-98c.workers.dev/api/v1/products \
  -H "Authorization: Bearer $KEY"

# 2. How is it doing?  (id from the response above)
curl https://swipefast.jacob-98c.workers.dev/api/metrics/prd_a1b2c3 \
  -H "Authorization: Bearer $KEY"

# 3. Record a sale from your own system
curl -X POST https://swipefast.jacob-98c.workers.dev/api/v1/orders \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"productSlug":"launch-playbook","email":"buyer@example.com"}'

Errors

Errors are JSON with a plain-English error field and an honest status code: 401 for a bad key, 404 for something that isn’t yours, 400 when the request itself is off.

{ "error": "Product not found" }

If you're an AI agent

Fetch /developers/llms.txt — the complete surface as plain text — or /developers/openapi.json for the machine spec. Both are generated from the same registry as these pages, so they never lag behind.

The whole surface