> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/features/api-publication.md). # API Publication and Governance Publication is how an API product becomes available to third-party providers. Our API Management module in [Central Administration Portal ](/portals-and-interfaces/central-portal.md)allows to publish APIs by simply uploading an OpenAPI specification and specifying product's name and URL. Once published, the API product gets automatically documented on the [Developer Portal](/portals-and-interfaces/developer-portal.md) and becomes available to third-party providers for testing and integration. In multi-tenant deployments an API product can be made available automatically in each tenant's own Developer Portal without a separate publication step. Every API Product on the Platfom has a governed lifecycle. You can create multiple versions of the same API Product and govern each version separately. Consumers are given notice when an API is deprecated or retired, and the gateway resolves each incoming call to a version that is actually serving traffic. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.api.tieto.com/features/api-publication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.