Didit History API

openapi: 3.2.0
info:
  version: 3.0.0
  title: Didit Verification History API
  description: Identity verification API. Authenticate with x-api-key header.
servers:
- url: https://verification.didit.me
tags:
- name: History
paths:
  /v3/organization/{organization_id}/application/{application_id}/cases/routing-rules/{record_uuid}/history/:
    get:
      operationId: list_case_routing_rule_history
      parameters:
      - in: path
        name: organization_id
        schema:
          type: string
          format: uuid
        required: true
      - in: path
        name: application_id
        schema:
          type: string
          format: uuid
        required: true
      - in: path
        name: record_uuid
        schema:
          type: string
          format: uuid
        required: true
      - name: ordering
        required: false
        in: query
        description: Which field to use when ordering the results.
        schema:
          type: string
      - name: limit
        required: false
        in: query
        description: Number of results to return per page.
        schema:
          type: integer
      - name: offset
        required: false
        in: query
        description: The initial index from which to return the results.
        schema:
          type: integer
      tags:
      - History
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RoutingPublicationPaginatedPolicyRevisionList'
          description: ''
        '403':
          description: Case access is required.
      security:
      - ApiKeyAuth: []
      summary: List case routing rule history
      x-summary-source: derived
components:
  schemas:
    RoutingPublicationPaginatedPolicyRevisionList:
      type: object
      required:
      - count
      - results
      properties:
        count:
          type: integer
          example: 123
        next:
          type:
          - string
          - 'null'
          format: uri
          example: http://api.example.org/accounts/?offset=400&limit=100
        previous:
          type:
          - string
          - 'null'
          format: uri
          example: http://api.example.org/accounts/?offset=200&limit=100
        results:
          type: array
          items:
            $ref: '#/components/schemas/RoutingPublicationPolicyRevision'
    RoutingPublicationPolicyRevision:
      type: object
      properties:
        version:
          type: integer
          maximum: 2147483647
          minimum: 0
        snapshot: {}
        actor_email:
          type:
          - string
          - 'null'
          format: email
          maxLength: 254
        published_at:
          type: string
          format: date-time
      required:
      - published_at
      - snapshot
      - version
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: 'Your application''s API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key''s workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.'
    TransactionTokenAuth:
      type: apiKey
      in: header
      name: X-Transaction-Token
      description: Short-lived scoped token minted by your backend via POST /v3/transactions/sdk-token/. Used by the Didit SDKs on the device-facing /v1/transactions/ endpoints.
    SessionTokenAuth:
      type: apiKey
      in: header
      name: Session-Token
      description: Short-lived token returned in the `session_token` field of POST /v3/session/. Used by the hosted verification flow (and custom sandbox UIs) to call session-scoped endpoints on behalf of the verifying user, without your server-side API key.
    BearerAuth:
      type: http
      scheme: bearer
      description: The application's client-credentials access token.
    CaseRequestToken:
      type: apiKey
      in: header
      name: X-Case-Request-Token
      description: Request-specific credential from the secure link. Grants access only to this request.