Who this is for — Independent integrators and partners building connectors for external services. Karzoun operates the hosting layer — you deliver the definition and supporting assets.
Before you submit
- Complete document — Identity,
auth,actions, and (if applicable)triggers,webhook,sync, andsourceblocks per the document schema. - Unique
ns— Lowercase kebab-case namespace (e.g.my-service). Cannot change after approval without a new submission. - Marketplace metadata —
title, descriptions,icon,logo,category,docsUrl. See Marketplace listing. - Provider assets — Host
iconandlogoon HTTPS URLs you control (SVG or PNG). Karzoun does not host partner brand assets during review. - Test credentials — Sandbox API keys or OAuth app for reviewers (see checklist below).
- Webhook URL — Document the Karzoun endpoint pattern:
https://{tenant-api}/miniapps/{ns}/webhooks(exact host provided during onboarding).
Submission package
Send to your Karzoun partner contact ordevelopers@karzoun.chat:
Review process
Typical turnaround is 5–10 business days depending on complexity (OAuth + webhooks + sync take longer than bearer-token + actions).
After approval
- Your MiniApp appears in Marketplace for tenants to install.
- OAuth redirect URI to register with your provider:
{SAAS_API_URL}/miniapps/{ns}/oauth2 - Webhook URL tenants register:
{SAAS_API_URL}/miniapps/{ns}/webhooks - For breaking changes, increment
versionand submit again — do not changens.
Updating an approved MiniApp
- Edit your JSON definition locally.
- Bump
version(semver). - Submit the package again with a short changelog.
- Karzoun rolls out after QA — existing installs keep working unless you document migration steps.
Next steps
- Marketplace listing — Copy and media checklist
- Troubleshooting — Issues while building locally
- Examples — Reference definitions