HELP & DOCS·UPDATED 2026-06-18·answers to common questions

Everything you need to get unstuck.

Straight answers to the questions we get most — API keys, connecting your store, checkout, plans, and building with the SDK. Can’t find it? Ask the support chat in the corner.

§01

How do I rotate my Trama API key?

Open your dashboard and go to Settings → API keys. Click “Create new key” to mint a fresh key, copy it immediately (the full value is shown only once), and update your app or environment variables with the new value. Once your integrations are using the new key, revoke the old one from the same page.

Rotating is safe to do anytime — a new key works instantly, and revoking the old key takes effect immediately. If a key is ever exposed, revoke it right away and create a replacement.

What is the difference between live, test, and public keys?

A live key (prefixed tr_live_) is a server-side secret for production traffic — keep it on your backend, never in browser code. A test key (tr_test_) behaves the same but is for development and staging. A public key (tr_pub_) is the only key safe to use in the browser: it is read-only and locked to the website origins you allow, so it cannot be misused if someone reads your frontend source.

Rule of thumb: anything running in a customer’s browser uses a tr_pub_ key; anything on your server uses a tr_live_ key.

Where do I find my API key?

Your dashboard, under Settings → API keys. You can create separate keys for production, testing, and your public storefront, and revoke any of them independently. For security we only store a hashed version of each key, so the raw value is shown once at creation — copy it then.

Is it safe to put a Trama key in my frontend?

Only a public key (tr_pub_). Create one in Settings → API keys, set the allowed website origins (for example your store’s domain), and use it in your storefront. Never put a live (tr_live_) or test (tr_test_) key in browser code — those are server-side secrets.


§02

How do I connect my Wix, Shopify, or Webflow store?

From the dashboard, create a project and choose your platform (Wix, Shopify, or Webflow). You’ll be sent to that platform to authorize the connection, then returned to Trama. Once connected, your products, collections, and cart are available through the Trama API and SDK in a single, consistent shape — no matter which platform they came from.

Do I have to migrate my data or change my store setup?

No. Trama is a connector — your products, orders, and customers stay exactly where they are on Wix, Shopify, or Webflow. You connect your existing store and build a custom frontend on top of it. There is no data migration and nothing about your current store changes.


§03

How does checkout work?

When a shopper checks out, Trama hands them off to your platform’s own secure, hosted checkout (the same checkout your store already uses on Wix, Shopify, or Webflow). Payments, taxes, and order creation are handled by your platform — you don’t have to build or maintain any of that.

Can I build my own custom checkout page?

Checkout itself runs on your platform’s native, hosted checkout — that’s what keeps payments secure and compliant and stays within each platform’s terms. You build the entire shopping experience (storefront, product pages, cart) with Trama, and the final checkout step redirects to your platform’s checkout.


§04

What are the plan limits?

Each plan sets how many projects you can run, how many products you can fetch per request, and your request rate. Free is for trying Trama on a single project; Starter, Pro, and Agency raise the limits and unlock features like webhooks and the support agent; Enterprise removes the caps. See the Pricing page for the current numbers per plan.

How do I upgrade or change my plan?

Go to Settings → Billing in your dashboard to upgrade, downgrade, or manage your subscription. Plan changes take effect immediately, and your new limits apply right away.


§05

What happens if my store changes a field or layout?

Trama is built to keep working when your store changes. If your platform renames or restructures a field, Trama detects it and adapts the connection automatically — usually within minutes — so your frontend keeps showing the right data without you touching code.

How is my data secured?

Every tenant’s data, keys, and connections are fully isolated from one another. Connection tokens are encrypted at rest, API keys are stored only as one-way hashes, and all traffic is served over HTTPS. We never return raw platform errors or secrets to your app.

Where is my product and order data stored?

It stays on your platform — Wix, Shopify, or Webflow. Trama reads from your store on demand and serves it through a fast, consistent API; it doesn’t take ownership of your catalog or customer records.


§06

How do I add Trama to my React app?

Install the SDK with “npm install trama-sdk”, wrap your app in the TramaProvider with your public key and project ID, then use the hooks (useProducts, useProduct, useCart) to render products and a cart. The quickest start is our Next.js starter template — clone it, add your three NEXT_PUBLIC_TRAMA_* values, and deploy.

How do webhooks work?

On Pro and higher plans, you can register webhook endpoints in Settings → Webhooks to be notified when products, orders, or your store change. Trama signs every webhook so you can verify it came from us before acting on it.

How do I add the support chat widget to my own site?

Create a public key (tr_pub_) in Settings → API keys, add your site’s origins to its allowlist, and drop the Trama widget script onto your pages with that key. The floating support button then appears for your visitors and answers using your project’s knowledge base.