Signicat Step Up API

openapi: 3.2.0
info:
  title: Signicat Step Up API
  version: 1.0.0
  contact: ''
  license: ''
  termsOfService: ''
  description: 'Operations tagged Step-up across 2 of this provider''s published API definitions: reuseid-onboarding-openapi.json, signicat-reuseid-onboarding-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.signicat.com
tags:
- name: Step-up
  description: 'The ReuseID **Step-up** API provides you with operations related to the step-up flow, such as starting and getting information about a ReuseID step-up session.


    ### About the step-up flow


    1. The step-up flow initiates a MobileID authentication on the provided device.

    2. Once the end-user has authenticated, an identity proofing session is started.

    3. After the end-user has successfully gone through the identity proofing process, the flow updates the MobileID user information with the data from the identity proofing process.'
paths:
  /reuseid/id-stepups:
    parameters: []
    post:
      tags:
      - Step-up
      summary: Start step-up
      operationId: startStepup
      description: 'The **Start step-up** endpoint initiates a step-up session.


        In this flow, you will:


        - Perform a MobileID authentication.

        - Perform an identity proofing.

        - Add identity attributes to the MobileID user.'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              x-examples:
                Example 1:
                  userId: 0eb66632-88d0-4ef4-8126-495c64a0abd2
                  deviceId: f8d74181-9e00-41ba-ba4f-43aa6a3dfea5
                  provider: signicatvideoid
                  videoidProviderOptions:
                    docType: 138
                    docTypes:
                    - 138
                    - 123
                    defaultId: 138
              required:
              - userId
              - deviceId
              properties:
                userId:
                  type: string
                  example: 0eb66632-88d0-4ef4-8126-495c64a0abd2
                  description: The ID of the user that will carry out the operation, in a valid UUID format.
                deviceId:
                  type: string
                  example: f8d74181-9e00-41ba-ba4f-43aa6a3dfea5
                  description: The ID of the end-user's device that will be used for the operation.
                provider:
                  type: string
                  description: A parameter to specify which identify proofing provider to use. The current two providers available are `readid` and `signicatvideoid`. If no provider is supplied, then the default provider `signicatvideoid` is used.
                videoidProviderOptions:
                  type: object
                  description: "An object that contains parameters for deciding what kind of documents can be used, and which document should be the default. \n\n- If not specified, then all ID documents that our VideoID solution supports will be available as an option for the end-user. \n- If only one specific document is to be used, then you can specify this with `docType`. \n- If multiple documents are to be available, then you can specify this with `docTypes`. \n\n**Note**: When multiple `docTypes` are specified, we recommend that you provide a `defaultId`. This is the first option shown to the user.\n"
                  properties:
                    docType:
                      type: integer
                      example: 138
                      description: A parameter to specify a single document type that you want to be used by the end-user.
                    docTypes:
                      type: array
                      description: A parameter to specify multiple document types that you want to be available for the end-user to choose from.
                      items:
                        type: integer
                        example: 138
                    defaultId:
                      type: integer
                      example: 138
                      description: 'A parameter to specify the default document type that you want to be shown to the end-user, when multiple document types are specified. This can only be used when `docTypes` has been provided.


                        **Note**: If not set, then the default is the lowest integer.

                        '
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                x-examples:
                  Example 1:
                    data:
                      status: Pending
                      transactionId: 0160e8b9-dabc-4a16-b995-29d88e6f102f
                      userId: 0eb66632-88d0-4ef4-8126-495c64a0abd2
                      deviceId: f8d74181-9e00-41ba-ba4f-43aa6a3dfea5
                      dossierId: e73801d2-3e7f-4184-8fda-67cc3b03416d
                      processId: 0dca14cf-957d-46d9-b374-520f9c650859
                properties:
                  data:
                    type: object
                    properties:
                      status:
                        type: string
                        example: Pending
                        description: The status of the step-up. This can be either `Pending`, `Success` or `Failed`.
                      transactionId:
                        type: string
                        example: 0160e8b9-dabc-4a16-b995-29d88e6f102f
                        description: The ID of the transaction. This is used in subsequent API requests to get the transaction data.
                      userId:
                        type: string
                        example: 0eb66632-88d0-4ef4-8126-495c64a0abd2
                        description: The ID of the user that carries out the operation, in a valid UUID format.
                      deviceId:
                        type: string
                        example: f8d74181-9e00-41ba-ba4f-43aa6a3dfea5
                        description: The ID of the end-user's device that is used for the operation.
                      dossierId:
                        type: string
                        example: e73801d2-3e7f-4184-8fda-67cc3b03416d
                        description: The ID of the dossier for the identity proofing session. This is used in API requests to get the evidence files of the identity proofing session.
                      processId:
                        type: string
                        example: 0dca14cf-957d-46d9-b374-520f9c650859
                        description: The ID of the process for the identity proofing session. This is used in API requests to get the evidence files of the identity proofing session.
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                type: object
                x-examples:
                  Example 1:
                    code: missing_permission
                    detail: The subject with ID 'dev-ghastly-thread-446' does not have the required permission 'mobileid:user:read' on the target resource 'a-sdge-c2z0wgHkZjpBnS7uB621'
                    status: 403
                    traceId: 4bf239c088089f2bca77d3a413909f1c
                    title: You do not have the required permission to perform this operation on the target resource
                    type: https://developer.signicat.com/errors?code=missing_permission
                properties:
                  code:
                    type: string
                    example: missing_permission
                    description: A machine-readable string that indicates the error code. This is a constant.
                  detail:
                    type: string
                    example: The subject with ID 'dev-ghastly-thread-446' does not have the required permission 'risk-flow:transaction:create' on the target resource 'a-sdge-c2z0wgHkZjpBnS7uB621'
                    description: "An explanation of the error, specific to this occurrence of the error.\t"
                  status:
                    type: integer
                    example: 403
                    description: "The HTTP status code generated by the origin server, specific to this occurrence of the error.\t"
                  traceId:
                    type: string
                    example: 4bf239c088089f2bca77d3a413909f1c
                    description: The unique identifier of the request in the tracing system. This makes it possible for us to trace the history of the request in detail.
                  title:
                    type: string
                    example: You do not have the required permission to perform this operation on the target resource
                    description: A summary of the error type. This does not change between occurrences of the error.
                  type:
                    type: string
                    example: https://developer.signicat.com/errors?code=missing_permission
                    description: The URI to the documentation that describes the error.
        '422':
          description: Unprocessable Entity (WebDAV)
          content:
            application/json:
              schema:
                type: object
                x-examples:
                  Example 1:
                    code: request_body_error
                    title: Bad Request
                    detail: docTypes and docType cannot be defined in the same request
                properties:
                  code:
                    type: string
                    example: request_body_error
                    description: A machine-readable string that indicates the error code. This is a constant.
                  title:
                    type: string
                    example: Bad Request
                    description: A summary of the error type. This does not change between occurrences of the error.
                  detail:
                    type: string
                    example: docTypes and docType cannot be defined in the same request
                    description: An explanation of the error, specific to this occurrence of the error.
                  status:
                    type: string
                    x-stoplight:
                      id: 1mvgm1vaw80ao
                    description: "The HTTP status code generated by the origin server, specific to this occurrence of the error.\t"
    servers:
    - url: https://api.signicat.com
  /reuseid/id-stepups/{transactionId}:
    get:
      tags:
      - Step-up
      summary: Get step-up
      operationId: getStepup
      description: The **Get step-up** endpoint gets data from a step-up session.
      parameters:
      - name: transactionId
        in: path
        description: The ID of the transaction, given in the **Start step-up** session.
        schema:
          type: string
        required: true
      - schema:
          type: string
        in: query
        name: transactionId
        description: The ID of the transaction, given in the **Start step-up** session.
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                x-examples:
                  Example 1:
                    data:
                      transactionId: e35ebbf7-9631-4966-9762-ae939c80eda1
                      userId: a1e26081-35b4-4557-a46a-ef50bc91672f
                      activationCode: '8954685641'
                      deviceId: b1g73121-55c4-9238-l39j-ek60dc91872g
                      proofingId: 30745db7-4403-4403-aa7e-cb35435ee565
                      dossierId: 3d563ac4-9d26-4a6a-b58d-5a29cacfe015
                      processId: 2f54b0a4-1a77-42e2-98d8-369116ef2055
                      status: Completed
                      userData:
                        firstName: JANE
                        lastName: SMITH
                        dateOfBirth: '1990-01-01'
                        gender: F
                        nationality: NOR
                properties:
                  data:
                    type: object
                    properties:
                      transactionId:
                        type: string
                        example: e35ebbf7-9631-4966-9762-ae939c80eda1
                        description: The ID of the transaction. Used in subsequent API requests to get the transaction data.
                      userId:
                        type: string
                        example: a1e26081-35b4-4557-a46a-ef50bc91672f
                        description: The ID of the user that carries out the operation, in a valid UUID format.
                      deviceId:
                        type: string
                        example: b1g73121-55c4-9238-l39j-ek60dc91872g
                        description: The ID of the end-user's device that is used for the operation.
                      proofingId:
                        type: string
                        example: 30745db7-4403-4403-aa7e-cb35435ee565
                        description: The ID of the identity verification.
                      dossierId:
                        type: string
                        example: 3d563ac4-9d26-4a6a-b58d-5a29cacfe015
                        description: The ID of the dossier for the identity proofing session. This is used in API requests to get the evidence files of the identity proofing session.
                      processId:
                        type: string
                        example: 2f54b0a4-1a77-42e2-98d8-369116ef2055
                        description: The ID of the process for the identity proofing session. This is used in API requests to get the evidence files of the identity proofing session.
                      status:
                        type: string
                        example: Completed
                        description: The status of the onboarding. `Pending`, `Success` and `Failed` are possible values.
                      userData:
                        type: object
                        description: An object containing data from the end-user, extracted from the identity proofing process.
                        properties:
                          firstName:
                            type: string
                            example: JANE
                            description: The first name of the onboarded end-user.
                          lastName:
                            type: string
                            example: SMITH
                            description: The last name of the onboarded end-user.
                          dateOfBirth:
                            type: string
                            example: '1990-01-01'
                            description: The date of birth of the onboarded end-user.
                          gender:
                            type: string
                            example: F
                            description: The gender of the onboarded end-user.
                          nationality:
                            type: string
                            example: NOR
                            description: The nationality of the onboarded end-user.
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                type: object
                x-examples:
                  Example 1:
                    code: missing_permission
                    detail: The subject with ID 'dev-ghastly-thread-446' does not have the required permission 'mobileid:user:read' on the target resource 'a-sdge-c2z0wgHkZjpBnS7uB621'
                    status: 403
                    traceId: 4bf239c088089f2bca77d3a413909f1c
                    title: You do not have the required permission to perform this operation on the target resource
                    type: https://developer.signicat.com/errors?code=missing_permission
                properties:
                  code:
                    type: string
                    example: missing_permission
                    description: A machine-readable string that indicates the error code. This is a constant.
                  detail:
                    type: string
                    example: The subject with ID 'dev-ghastly-thread-446' does not have the required permission 'risk-flow:transaction:read' on the target resource 'a-sdge-c2z0wgHkZjpBnS7uB621'
                    description: An explanation of the error, specific to this occurrence of the error.
                  status:
                    type: integer
                    example: 403
                    description: "The HTTP status code generated by the origin server, specific to this occurrence of the error.\t"
                  traceId:
                    type: string
                    example: 4bf239c088089f2bca77d3a413909f1c
                    description: "The unique identifier of the request in the tracing system. This makes it possible for us to trace the history of the request in detail.\t"
                  title:
                    type: string
                    example: You do not have the required permission to perform this operation on the target resource
                    description: A summary of the error type. This does not change between occurrences of the error.
                  type:
                    type: string
                    example: https://developer.signicat.com/errors?code=missing_permission
                    description: The URI to the documentation that describes the error.
        '404':
          description: Not Found
    servers:
    - url: https://api.signicat.com
components:
  securitySchemes:
    Token:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: ''
          refreshUrl: ''
          scopes: {}
x-refined-from:
- reuseid-onboarding-openapi.json
- signicat-reuseid-onboarding-openapi.yml