All pages
Getting started
1. Apply as a developer
Open craving Apps from your Resident account and apply with your display name (shown on your listings), support email, website and what you want to build. We review developer applications by hand. Your Resident account needs identity verification and payout setup completed before approval.
2. Create the app
Once approved, tap New app to create a listing with a name (3 to 50 characters; do not include craving or another platform’s name), a fixed slug (/marketplace/<slug>, lowercase letters, numbers and dashes, not starting with craving), an optional tagline, a category and an audience. Complete the Listing section (tagline, description, icon, at least 2 safe-for-work screenshots, and support, privacy and terms URLs) before submitting a version.
3. Configure credentials
In the Connection section of your app page:
- Client id and secret: your server uses these at the token endpoint. Open Client secret to mint or rotate the secret. It is shown once; we store only its hash.
- Redirect URIs: up to 10 https URLs where the browser may return after an install.
- Webhook: every event for your app (installs, uninstalls, block placements, support threads, review decisions and subscribed Resident events) is POSTed here with a signature. You must set a webhook URL before submitting a version. The signing secret is shown once when set or rotated.
4. Write the manifest
A version is an immutable JSON manifest declaring capabilities, scopes, origins and capability config. In Versions, tap New version (pre-filled with a starter template), save it as a draft, fix any validation errors, then tap Submit for review. See the Manifest reference for every field.
5. Handle the install
When an installation activates, your webhook receives installation.created:
{
"event": "installation.created",
"app_id": "…",
"installation_id": "…",
"scope": "account",
"agency_id": null,
"installer": { "id": "…", "username": "sophie", "name": "Sophie" },
"granted_scopes": ["profile.read", "chat.tools"],
"plan_id": null,
"install_code": "…",
"install_code_expires_at": "2026-09-13T20:10:00Z",
"sent_at": "2026-09-13T20:00:00Z"
}Verify X-Craving-Signature (Authentication), then exchange install_code within 10 minutes:
curl -u "$CLIENT_ID:$CLIENT_SECRET"
-d grant_type=install_code
-d install_code="$CODE"
https://api.craving.com/functions/v1/gc_marketplace_oauth/tokenStore the returned token pair keyed by installation_id. Every block session, tool call, webhook and API request for that installer uses installation_id.
6. Go live
Submitting starts the automated review right away. Versions without heavy capabilities or scopes go live as soon as every check passes. Heavy versions wait for a reviewer after passing the automated checks. If a check fails, the version is rejected with the requirement number so you can edit it and submit again. Your app page tracks each step under Getting live and Versions.
7. Test before you publish
You can install your own draft app on your Resident account from its preview listing and place its block on your Home. See Test installs.