| Table of Contents |
|---|
...
| Code Block |
|---|
{
"clientId": "8f92e604-b9b9-11ec-8422-0242ac120002",
"clientSecret": "8f92ea14-b9b9-11ec-8422-0242ac120002",
"clientReferences": [
{
"clientReference": "<customer-reference>"
}
],
"processId": "USER_ONLY"
}
|
The response will refer to the customer reference and include a process token, that identifies the process instance.
| Code Block |
|---|
{
"processes": [
{
"clientReference": "<customer-reference>",
"processToken": "8f92ec58-b9b9-11ec-8422-0242ac120002"
}
]
}
|
Step 2: Get the OAuth Token
With the process token, the (finAPI Access-) user OAuth token (required to get authorised GiroIdent API calls) can be retrieved from the Process Controller endpoint GET /processes/{process-token}?invalidate=true.
The response will look like this:
| Code Block |
|---|
{
"accessToken": "89e3b64c-b9ba-11ec-8422-0242ac120002"
}
|
Sequence diagram (GiroIdent as an example)
...
| Code Block |
|---|
{
"access_token": "fnsXpguIBkChhCsN8bVty9Y68AsUvJYyXUILcsFBvWABF03k8Ov68Ev2BTyANuBjyX8r9XuuTajNM2zZnhZMDjKWHN4lbRSRcVhg9_PcE7eeXHm0t28ZjzM4TJlrupZD",
"token_type": "bearer",
"expires_in": 3599,
"scope": "all"
}
|
To get authorized as a Client, use the obtained access_token as input for Access QUICK AUTH.
...
| Code Block |
|---|
{
"id": "username",
"password": "password",
"email": "email@localhost.de",
"phone": "+49 99 999999-999",
"isAutoUpdateEnabled": false
}
|
The user creation request response:
| Code Block |
|---|
{
"id": "username",
"password": "password",
"email": "email@localhost.de",
"phone": "+49 99 999999-999",
"isAutoUpdateEnabled": false
}
|
Step 3: Get authorized as a user
...
| Code Block |
|---|
{
"access_token": "nnsXpguIBkChhCsN8bVty9Y68AsUvJYyXUILcsFBvWABF03k8Ov68Ev2BTyANuBjyX8r9XuuTajNM2zZnhZMDjKWHN4lbRSRcVhg9_PcE7eeXHm0t28ZjzM4TJlrupZD",
"token_type": "bearer",
"expires_in": 3599,
"scope": "all"
}
|
To get authorized as a User, use the obtained access_token
...