...
Workflow Diagram
...
API Endpoints
1. [POST] /api/authentications (PostAuthenticationAsync)
Creates a new authentication. (Step 2)
If succeeds, returns authenticationId as a GUID in the location header. (Step 3)
Payload property parameter name | Description |
|---|---|
| Desired NEXT PartnerId |
| Authentication method to use:
|
| Identity (personal number / social security number) to verify against |
| Your url that user will be redirected back to as shown in step 8. AuthenticationId value will be appended as a query string parameter with |
| An optional |
2. [GET] /bankid/{partnerId}/{authenticationId}/authenticate (GetBankIdAuthenticationUrlAsync [Redirects user to the corresponding service provider])
End user should be opening this page upon a new authentication is created and authenticationId is claimed. (Step 4)
...
)
Route parameter name | Description |
|---|---|
| Location header value claimed after succesful [POST] /api/authentications request |
| Desired NEXT PartnerId |
3. [GET] /api/authentications/{partnerId}/{authenticationId} (GetAuthenticationAsync])
It could be called anytime once an authentication is created. The best case for you business to call this endpoint would be the place where you check whether the user authentication is complete or not. (Step 9)
Route parameter name | Description |
|---|---|
| Location header value claimed after succesful [POST] /api/authentications request |
| Desired NEXT PartnerId |
2. Signing
todo:add api endpoints along with explanations
...