> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1t-ocra-client/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1t-ocra-client/overview/supported-flows.md).

# Supported Flows

The OCRA API provide the following Mutual Challenge Response Flows:

## Without using hardware tokens or smart cards

The following sequence diagram describes the OCRA Mutual Challenge Response flow implemented by the OCRA API.

In order to access the OCRA-API a valid api-key is needed. The Notification API is an optional component, which is available on the [Trust1Team Marketplace](https://mkt.t1t.be), you can choose to implement your own or use a 3rd Party API as well.

![](/files/-L9hsb1UhG_-clpoQ4rI)

## Using the Trust1Connector (no hardware needed)

![](/files/-L9hsb1kZ_TzE-xmiES7)

## Using a hardware token or a smartcard with OCRA applet

![](/files/-L9hsb1rkMvIdUmJ3uAz)


---

# 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://t1t.gitbook.io/t1t-ocra-client/overview/supported-flows.md?ask=<question>&goal=<endgoal>
```

`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.