Submitting an app

The lifecycle

A listing version moves through these statuses, and only these:

Draft → Submitted → InReview → Approved or Rejected → Listed → Suspended or Delisted

Status	Meaning	Who moves it
Draft	You are still writing it. The only status you can edit.	you
Submitted	Handed to review. Locked: a change is a new version.	you
InReview	A named reviewer has taken it.	CIQRA
Approved	Review passed; not on the market yet.	CIQRA
Rejected	Review failed. The note says why. You can reopen it as a draft.	CIQRA
Listed	On the market.	CIQRA
Suspended	Pulled back reversibly (security or policy). The note says why.	CIQRA
Delisted	Ended for good. The note says why.	CIQRA

A rejection, suspension or delisting always carries its reason.

Steps

1. Write the manifest (see the reference): a JSON object. Each (key, version) is one submission.
2. Save it as a draft: PUT /partner/v1/organisations/{partnerId}/listings. The manifest is checked on the spot; every problem comes back at once as findings, nothing is stored until it is clean. Saving the same version again replaces the draft.
3. Submit it: POST .../listings/{id}/submit. It is validated again, so a stale draft cannot slip through.
4. Follow it: GET .../listings/{id}. If it was rejected, read the note, POST .../listings/{id}/reopen, fix the manifest, and submit again.
5. Change a submitted version? Publish the change as a new version (1.1.0). A submitted version is locked (version_locked).

Rules that apply to every partner manifest

• It is an app you run: kind is Vendor, availability is Live.
• It has no connectPath, integrationSlug or shelfKey: those belong to CIQRA’s own apps and integrations.
• Its pricing.model is Free or VendorBilled.
• It asks only for scopes the platform publishes, and each one needs a route that enforces it.
• It cannot carry a rating or a review count, or any member the platform does not define: an unknown member is an error, never silently dropped.