Skip to content

RapidAPI Marketplace Terms

These terms govern your use of the QR Branding API when consumed through the RapidAPI marketplace (qr-branding.p.rapidapi.com). They are additional to, and not in place of, our general Terms of Service and Privacy Policy.

If you purchased credit packs on qr-branding.com instead, the marketplace terms below do not apply — only the general Terms of Service do.

Effective date: 2026-10-07

1. Parties

The API is operated by Juan José Camacho, registered at 04005, Almería, Spain (full identification details in the Terms of Service), contact support@qr-branding.com (the "Provider", "we").

Distribution, billing and customer onboarding through the marketplace are handled by RapidAPI under its own RapidAPI Terms of Use. Nothing on this page overrides those marketplace-level terms — it complements them with the Provider-specific rules below.

2. Subscription plans

The plans shown on the marketplace product page are monthly subscriptions sold and invoiced by RapidAPI. Quotas, overage prices and renewal dates are the ones shown on the marketplace when you subscribed; they take precedence over any older copy elsewhere on the web.

Every request that reaches the API counts towards your plan's quota, including requests that end in an error (for example 422 QR_UNSCANNABLE), because RapidAPI meters calls, not outcomes.

Refunds and cancellations for marketplace plans are processed through the RapidAPI billing portal, not directly with us.

3. Authentication & key handling

Marketplace traffic is authenticated by RapidAPI via the X-RapidAPI-Proxy-Secret header injected at their gateway. You must:

  • Keep your X-RapidAPI-Key confidential. We treat it as opaque proof that your request came through your RapidAPI account.
  • Not embed your key in client-side code, public repositories, or distributed binaries.
  • Not share your key across organisations beyond what your plan allows.

We may temporarily suspend traffic from a key that we reasonably believe is compromised, and we will notify RapidAPI so they can rotate it.

4. Acceptable use

You may not use the API to:

  1. Encode content that is illegal in your jurisdiction or in ours, or that targets a third party for harassment, fraud, phishing or malware delivery.
  2. Impersonate another brand without authorisation, or use trademarked logos you do not have the right to display.
  3. Re-sell raw API responses as a substitutable competing API. You may embed the output in your own application, product or service freely.
  4. Probe, scrape, scan or attempt to overwhelm the gateway or the underlying Function App.

Breaches will, at our discretion, result in throttling, key suspension via RapidAPI, or termination.

5. AI generations on the marketplace

Two AI endpoints are available on the marketplace:

  • POST /api/qr/ai/generate-managed (Managed AI). No LLM key needed: we run the models on our own accounts. Calls to this endpoint count towards the separate Managed AI quota of your plan.
  • POST /api/qr/ai/generate (bring your own key). You supply your own LLM API key (llmApiKey) for one of the supported providers (OpenAI, Anthropic, Google, Mistral, Cohere, Groq, xAI, DeepSeek, Qwen) or any OpenAI-compatible endpoint. LLM costs are billed by your provider, not by us and not by RapidAPI; we add no markup. Your key is used only to fulfil the request and is never logged or stored.

AI output is a design proposal: every AI render goes through the same scan verification as any other render (section 7).

6. Quotas, rate limits and overage

The hard limits are those declared by your marketplace plan. In addition, the API applies a per-account safety throttle to protect the service from accidental loops: about 30 renders and 15 AI generations per minute per RapidAPI account. Above it you receive 429 Too Many Requests with a Retry-After header. When you exceed your plan quota, RapidAPI returns its own 429 before the request reaches us.

7. Scan guarantee

Every render endpoint decodes the QR it has just produced, server-side, before returning it. If the requested design cannot be read back, the engine retries with progressively safer settings; if it still cannot produce a scannable code it returns 422 QR_UNSCANNABLE and no file.

Every successful render carries an X-Generation-Id response header. If a QR produced by the API fails to scan with standard consumer readers within 90 days of generation, email support@qr-branding.com with that X-Generation-Id and a photo of the failed scan. After checking it, we re-render an equivalent QR at no API charge. The re-issue covers the digital file only; printing, shipping and other physical costs are not reimbursed.

8. Data handling

When you call the API through the marketplace:

  • Your request body (including the encoded content, the prompt for AI calls, and any logo data) is processed in-memory to produce the response and then discarded.
  • We keep technical request metadata (timestamp, route, response code, latency; no QR content, prompts or logos) in our monitoring logs for up to 90 days, for troubleshooting and abuse prevention.
  • AI design results are cached for 30 days under a one-way hash of the prompt and its parameters, so an identical request returns the same design without calling the LLM again. The cache stores the generated design settings, never your LLM key.

See the Privacy Policy for the complete picture.

9. Liability

To the extent permitted by law, our maximum liability for any claim arising from your use of the marketplace API is the amount you paid us through RapidAPI in the 12 months preceding the claim. We are not liable for indirect, incidental or consequential damages, nor for downstream third-party failures (LLM providers, RapidAPI gateway, payment networks).

10. Changes & continuity

We may update these marketplace terms. Material changes are announced on the marketplace listing and via the email associated with your RapidAPI account at least 30 days in advance. Continued use after the effective date implies acceptance.

If we ever discontinue the marketplace listing, active paid subscriptions are honoured until the end of their current billing period, and the public consumer site at qr-branding.com remains available for credit-pack purchases under the general Terms of Service.

11. Governing law

These terms are governed by the laws of Spain. Disputes are subject to the exclusive jurisdiction of the courts of Almería, without prejudice to mandatory consumer protection rules in your country of residence.

For RapidAPI-side issues (billing, account management, marketplace dispute resolution), RapidAPI's own Terms of Use apply.