Architecture Overview
Sticker’s embedded integration follows a simple but secure architecture that keeps your users authenticated across both platforms while providing a seamless procurement experience.Integration Components
Backend Integration
Two API endpoints to call from your backend server
Frontend Embedding
iframe component to display Sticker in your UI
Organization Management
Automatic provisioning of orgs, users, and billing
Session Authentication
Secure, time-limited tokens for each user session
Two API Endpoints, That’s It
The entire integration requires just two API calls:1. Organization Setup (One-Time)
Called when a customer enables procurement in your platform.- Organization with Stripe customer for billing
- User profile linked to Supabase Auth
- Shipping locations for order delivery
2. Partner Handshake (Per-Session)
Called every time a user opens the supplies module.- Session token (5 min, single-use)
- Complete iframe embed URL
Integration Flow
One-Time Setup Flow
This happens once when a customer enables procurement:1
Customer Enables Supplies
A customer clicks “Enable Supplies” in your platform
2
Gather Data
Collect organization name, user info, and shipping addresses from your system
3
Call Organization Setup
Send data to Sticker:
4
Store Response
Optionally store the returned
profile.id for reference5
Enable UI
Show the supplies module in your navigation
Per-Session Authentication Flow
This happens every time a user opens supplies:1
User Clicks Supplies
User navigates to the supplies section
2
Call Handshake
From your backend, call Sticker:
3
Get iframe URL
Response contains complete embed URL:
4
Embed iframe
Display the iframe in your UI
5
User Shops
User browses, orders—all within your platform
Data Models
Sticker maps users into organizations using a many-to-one structure:- An organization is the customer business, company, practice, store, school, or legal entity.
- A profile is an employee or user inside that organization.
- One organization can have many profiles.
- Each distinct customer business must have a unique
internalOrgId.
What You Send
What You Receive
Security Model
API Key Authentication
API Key Authentication
All API requests require your Partner API Key. Never expose it in client-side code.
Session Tokens
Session Tokens
- 5 minute expiry - Must be used quickly
- Single-use - Invalidated after first use
- User-bound - Tied to specific profile
- Partner-bound - Only works with your iframe URL
iframe Sandboxing
iframe Sandboxing
The iframe runs with restricted permissions:
What’s Included Out of the Box
When you embed Sticker, your users get:Environments
Use sandbox for development and testing. Sandbox data is isolated from production.
Rate Limits
Implement exponential backoff for 429 responses.
Next Steps
Organization Setup
Provision organizations and users
User Handshake
Authenticate users for each session
iframe Embedding
Display Sticker in your application
Best Practices
Tips for a robust integration

