From f28a797b6bd4220e0c4ccde0c66f66c3ee5eeaa7 Mon Sep 17 00:00:00 2001 From: "b.boterman@htm.nl" Date: Thu, 18 Jun 2026 11:17:04 +0200 Subject: [PATCH] OVPAY-2485 - Improved TP requests. --- src/openapi/customers/SE-customers-v2.yaml | 30 ++++++++++++++-------- 1 file changed, 19 insertions(+), 11 deletions(-) diff --git a/src/openapi/customers/SE-customers-v2.yaml b/src/openapi/customers/SE-customers-v2.yaml index a3882c6..1b59ae6 100644 --- a/src/openapi/customers/SE-customers-v2.yaml +++ b/src/openapi/customers/SE-customers-v2.yaml @@ -3757,13 +3757,8 @@ paths: application/json: schema: $ref: "#/components/schemas/ActivateAgoRequest" - examples: - For self: - value: - emailAddress: null - For other: - value: - emailAddress: stasjo@htm.nl + example: + emailAddress: stasjo@htm.nl responses: "200": description: OK @@ -3879,15 +3874,25 @@ paths: post: tags: - AGO - summary: Request additional OV-pas security for a token in profile. - description: Request additional OV-pas security for a token in profile. + summary: Submit an OTP for a triggered OTP flow. + description: | + Submit an OTP for a triggered OTP flow. This can either be result of an AGO activation, or + result of an AGO authorization flow. Since the backoffice behaves slightly different depending + on which use case is executed, the calling TP needs to provide an `action` in the request body. requestBody: content: application/json: schema: $ref: "#/components/schemas/VerifyOtpRequest" - example: - otp: 123456 + examples: + OTP verification for TAT security activation: + value: + otp: 123456 + action: secure + OTP verification for TAT security authorization: + value: + otp: 123456 + action: authorize responses: "200": description: OK @@ -4908,6 +4913,9 @@ components: emailAddress: type: string example: 123456 + action: + type: string + example: secure VerifyOtpResponse: type: object properties: