Skip to content

Migrating from RapidAPI

If you've been calling the Signet QR API through RapidAPI, nothing breaks. The marketplace channel is exactly as it was — same URL, same auth header, same JSON shape, same SLA.

What changed is that the same engine now also powers a consumer site at qr-branding.com with one-time credit packs. You can stay on the marketplace, switch, or use both.

What stays the same

  • URL: api.qr-branding.com (CNAME to the same Azure Function App signetqr-core).
  • Auth: X-RapidAPI-Proxy-Secret header.
  • Endpoints: every path you were calling.
  • Body shapes: QrConfig and AiQrRequest are untouched.
  • Response shapes: identical.
  • Rate limits: identical RapidAPI plan caps.
  • Billing: still via RapidAPI's monthly subscription / per-call model.

What's new

  • A second auth path for the consumer site: HMAC-signed internal headers (X-Internal-Service-Secret + X-Internal-Signature). You won't see these — they're set server-side by the Next.js BFF.
  • A server-side AI endpoint /api/qr/ai/generate/server that doesn't require you to supply your own llmApiKey. Available to consumer-site customers only. Marketplace customers keep using /api/qr/ai/generate with their key.
  • A 30-day prompt cache (Upstash Redis). Re-running the same prompt + provider + model + creativity + style + strict returns the cached config — no LLM call, no token cost.

When to switch to consumer credits

You probably want to move if:

  • You make < 200 AI generations / month (Starter at $9 once is cheaper than a monthly plan).
  • You're tired of bring-your-own LLM keys and want server-side LLM with a flat per-credit price.
  • You want dynamic QRs with stats (from 1 free with an account) or bundled API access (only on Studio).

You probably want to stay on the marketplace if:

  • You make > 1500 AI generations / month at consistent volume (subscription beats packs).
  • You have an existing RapidAPI integration with tooling, billing reconciliation, etc.
  • You want OpenAI/Anthropic/Cohere/Mistral choice — the marketplace endpoint lets you pick.

Side-by-side use

Nothing prevents you from running both channels in parallel. Marketplace calls hit api.qr-branding.com, consumer-site flow hits qr-branding.com/api/internal/.... Same engine, two billing meters, zero contention.

If you have questions about whether to migrate, reply to your last receipt — it goes to us.