> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/marketplace/concepts/concept-publishing.md). # Publishing & productizing Publishing turns a governed API into something a consumer can find and subscribe to. Productizing packages one or more APIs into a subscribable unit with commercial terms attached. ![Figure. From a governed API to a working app, with the subscription lifecycle.](/files/bNlmtLTp8sONUJu8CTE9) ![Figure. Manage API Products, where APIs are bundled into subscribable units.](/files/n87UPl5q9qypmsieRLEt) ### Publishing Publishing moves an imported, governed API from draft into the catalog your consumers see. A moderation state controls visibility: change it to Published to take an API live, or revert it to pull the API back. The edit form sets the consumer-facing metadata that drives the catalog tile and detail page, including the overview, documentation, logo, domain, and tags. * **Visibility:** scope the audience to public, or to partner and signed-in users only. * **Revision log:** each publish records who changed what, surfaced in the Change Log. Publish only after governance, since the score is the agreed quality bar. ### Products & plans A Product bundles one or more APIs into the thing a consumer actually subscribes to. APIs can be grouped across gateways, so a Product can span several backends and still present as one offering. Plans attach the commercial and operational terms to a Product. Each plan sets a quota, rate limits, and a pricing tier, so Free, Standard, and Premium map to different limits on the same Product. Subscribing to a Product grants access to every API in it under one subscription. Plans are where monetization begins; enforcement happens at the gateway, not in the portal. ### Subscriptions A subscription links a consumer's app to an API or Product under a chosen plan. Providers review requests and manage each subscription through its life. * **Request:** a consumer requests a subscription to a Product under a plan. * **Approve or reject:** providers approve, optionally with a reason; auto-approval is configurable. * **Lifecycle:** Pending, Active, Suspended, then Revoked or Cancelled. * **Revocation:** suspending or revoking invalidates the credential at the gateway. Subscription state is the source of truth the gateway honours on every call. ### Apps & credentials An app is the consumer's application that holds credentials. When a subscription is active, Astra provisions credentials to the gateway, which validates them on every request. * **Register:** a consumer creates an app, which can hold several subscriptions. * **Credentials:** a client identifier and secret, or an API key, are issued. * **Validated downstream:** the gateway checks the credential on every call. Astra issues and provisions; the gateway enforces, and the portal stays out of the request path. * **Rotate and revoke:** keys rotate without losing the subscription, and revoking a subscription cuts access. > **How-to:** for step-by-step configuration, see the How-to guides. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digitalapi.ai/marketplace/concepts/concept-publishing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.