App Development
Build a custom app for your Tanqory store: REST + GraphQL APIs, webhooks, App Store distribution. For developers building custom integrations + tools.
On this page
Tanqory App Development lets you build a custom app for your store (or for the App Store). Use Tanqory's REST + GraphQL APIs, webhooks, and authentication. This article covers the high-level path; for detailed reference see Tanqory developer docs.
You'll work outside the admin, in your IDE, but interact with admin for app registration + permissions.
Before you begin
- Start at Tanqory's developer portal to read the auth and API guide, then register your app from the developer dashboard.
- You have programming skills (Node.js, Python, Ruby, Go, etc.).
- You have a Tanqory developer account (or contact Tanqory partner team).
- You've read Tanqory's developer docs.
- You have a development store for testing.
What custom apps can do
| Capability | Example |
|---|---|
| Read data | Pull orders, customers, products via API |
| Write data | Create orders, update inventory, manage discounts |
| Subscribe to events | Webhooks for order events, customer events |
| Custom admin UI | Embed your app's UI in Tanqory admin |
| Customer-facing UI | Embed widgets on the storefront |
| Background jobs | Schedule recurring tasks |
Auth + permissions
| Auth model | Use case |
|---|---|
| API token | Single-store internal integration |
| OAuth (per-store) | Multi-store app distributed via App Store |
| JWT (session) | Embedded admin UI |
| HMAC (webhook verify) | Verify Tanqory's signed webhook events |
Steps
1. Read the developer docs
Start at Tanqory's developer portal. Read the auth + API guide.
2. Decide the app type
- Internal (single-store, private): API token suffices.
- App Store (distributed): OAuth flow + review process.
3. Register your app
In your developer dashboard. Tanqory issues credentials.
4. Build the app
- Authenticate.
- Call APIs.
- (For event-driven) subscribe to webhooks.
- (For embedded UI) build the frontend per Tanqory's UI guidelines.
5. Test in a development store
Don't develop against production. Use a dev store.
6. Verify webhook signatures
Use the HMAC signing secret to verify incoming webhook events. Never skip: security risk.
7. Submit for App Store review (if distributing)
Tanqory reviews app submissions for security + UX. Expect 1-4 weeks.
8. Maintain
After launch:
- Monitor errors.
- Respond to support.
- Update for Tanqory API changes.
Verify the result
- App authenticates successfully.
- API calls return expected data.
- Webhooks deliver + verify.
- (Embedded) UI renders correctly in admin.
Best practices
- Develop against a dev store.
- Verify webhook signatures.
- Handle rate limits gracefully. Tanqory enforces per-app rate limits.
- Document your app: for your team + customers.
- Plan for API versioning: Tanqory may bump versions.
Common mistakes
- Developing against production.
- Skipping webhook signature verification: security risk.
- Ignoring rate limits: your app gets throttled.
- No error handling: silent failures.
- No app monitoring: you don't know it broke.
If something goes wrong
- API call returns 401: auth token issue.
- API call returns 429: rate limit; back off.
- Webhook signature mismatch: verify your HMAC implementation.
- App rejected by App Store: review feedback; resubmit.
Next steps
- Tanqory developer docs (external).
- Apps Overview
- Manage Installed Apps
Related articles
Still stuck?
- Ask Tanqory AIAsk in your own words. It answers from these articles and links the ones it used.
- Ask in your adminThe assistant in your Tanqory admin answers and makes the change for you once you confirm.
- Contact TanqoryWrite to our privacy, security or legal teams, or talk to sales about a plan or a move.