> 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/portals-and-interfaces/developer-portal.md). # Developer Portal The Developer Portal is the platform's public face and the channel through which third-party providers discover, test and consume APIs. Everything a third party needs from first look to production traffic happens here. ## Public area No account required. Product catalog, getting-started guides, API references and glossary — enough for a developer to judge whether the APIs fit before committing to anything. Content is maintained by the operator through the content management system. ## Registered area Registration unlocks the working parts of the portal. | Area | Purpose | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Sandbox | Test regulatory and premium services in sandbox mode. **Dynamic** **sandbox** is offered for compliance APIs, **Static sandbox** — for premium and aggregation services. | | Applications | Create and version client applications, define API scopes, obtain credentials | | Certificates | Manage your certificates: upload QWAC and QSealC, submit signing requests to generate platform-issued certificates for premium APIs, revoke and rename | | Subscriptions | View available products per provider and subscribe to gain live access | | Users | Invite colleagues, assign roles, suspend accounts | | Reports | Traffic and fee reports for the organization's own consumption | | Documentation | Getting-started guides, per-service integration guides with request and response examples, API references and downloadable specifications | | Profile | Manage password and authenticator devices | --- # 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/portals-and-interfaces/developer-portal.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.