> 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.md).

# Features

Thirteen platform capability areas — API publication and lifecycle, back office and register integration, policies, multi-tenancy, consents, access control and monetization.

Thirteen capability areas. Together they describe what the platform does beyond terminating an API: how interfaces are published and governed, how banks and external authorities connect, how tenancy and access work, and how commercial APIs are metered and charged.

## Publishing and governing APIs

|                                                                 |                                                                                                                        |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| [API Publication](/features/api-publication.md)                 | The API Group model, specification upload and validation, preprocessing, and how a product reaches the catalog         |
| [API Lifecycle Management](broken://pages/ZQyBAhLEpkWQSgGOTo1N) | Version statuses, version resolution, change cadence and notice periods, four-eyes governance and retirement           |
| [API Policies](/features/api-policies.md)                       | The full policy set — trust and identity, message integrity, validation, traffic management, request shaping and audit |

## Connecting the bank and external authorities

|                                                                                         |                                                                                                                               |
| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| [Back Office Integrations](/features/back-office-integrations.md)                       | The SCA Server and Core Server interfaces, authentication in both directions, integration decisions and version mapping       |
| [Consent Management](/features/consent-management.md)                                   | Consent storage and lifecycle, authentication sessions, integration into the bank's own channels, and staff oversight         |
| [API Aggregation](/solutions-and-use-cases/aggregation.md)                              | Fronting many banks behind one interface, including how certificate substitution works                                        |
| [Integration with National Registers](/features/integration-with-national-registers.md) | Validating every call against the register of licensed providers, and adding the custom verification checks a market requires |

## Operating a multi-tenant platform

|                                                                                           |                                                                                            |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| [Multi-Tenancy and White-Labeling](/features/multi-tenancy-and-white-labeling.md)         | What a tenant is, what is isolated, the separated and marketplace models, and branding     |
| [Access Control](/features/access-control.md)                                             | Roles in every portal, mandatory two-factor authentication, separation of duties and audit |
| [Content Management](/features/content-management.md)                                     | Customer-owned portal content, review and preview, service notices                         |
| [Localization and Regional Adaptation](/features/localization-and-regional-adaptation.md) | Regulatory, payment, time zone, content and identifier adaptation per market               |

## Running it as a business

|                                                                            |                                                                                              |
| -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| [Monitoring and Reporting](/features/monitoring-and-reporting.md)          | Availability measurement, the statistics regulators require, and reports for each audience   |
| [Limits, Fees and Monetization](/features/limits-fees-and-monetization.md) | Technical and commercial limits, recurring and per-call pricing, billing data and governance |


---

# 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.md?ask=<question>&goal=<user_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.