openapi: 3.0.0 info: title: Dotfile API — Checks description: Dotfile public API — Checks operations. Split by tag from the OpenAPI Dotfile publishes at https://docs.dotfile.com/openapi/%EF%B8%8F-api-specifications.json (discovered via https://docs.dotfile.com/.well-known/api-catalog). Content is verbatim; only the tag partition is ours. version: v1 contact: name: Dotfile Support email: support@dotfile.com url: https://docs.dotfile.com/reference/getting-help servers: - url: https://api.dotfile.com description: Production environment tags: - name: Checks security: - DotfileAPIKey: [] paths: /v1/checks: get: operationId: check-get-many summary: List all checks description: "Returns a list of all checks created in your Dotfile workspace.\n\n---\n\n#### See also \nLearn more\ \ about [Checks](./checks-guide) \nLearn more about [Filtering, Sorting and Pagination](./filtering-sorting-and-pagination)\ \ \n" parameters: - name: individual_id required: false in: query description: "Filter items by the `individual_id.{operator}` field. \nYou can use the `eq` and `not_eq` operators,\ \ the `eq` operator being the default." schema: type: string - name: company_id required: false in: query description: "Filter items by the `company_id.{operator}` field. \nYou can use the `eq` and `not_eq` operators, the\ \ `eq` operator being the default." schema: type: string - name: status required: false in: query description: "Filter items by the `status.{operator}` field. \nYou can use the `eq` and `not_eq` operators, the `eq`\ \ operator being the default." schema: type: string enum: - in_progress - need_review - processing - approved - rejected - expired - name: type required: false in: query description: "Filter items by the `type.{operator}` field. \nYou can use the `eq` and `not_eq` operators, the `eq`\ \ operator being the default." schema: type: string enum: - id_verification - id_document - aml - company_monitoring - document - ekyc - electronic_signature - fraud_database - online_reputation - name: exclude_internal required: false in: query description: "Exclude checks that are marked as internal. \nDefault is false" schema: type: boolean - name: include_not_relevant required: false in: query description: "Include checks from individuals marked as not relevant. \nDefault is false" schema: type: boolean - name: created_at required: false in: query description: "Filter items by the `created_at.{operator}` field. \nYou can use the `eq`, `not_eq`, `gt`, `gte`, `lt`\ \ and `lte` operators, the `eq` operator being the default." schema: type: string pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}(T[0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,3})?(Z|([0-9]{2}:[0-9]{2}))?)?$ example: - '2023-01-31' - '2023-01-31T13:30:00Z' - '2023-01-31T13:30:00.000Z' description: Date (`yyyy-MM-dd` eg `2023-01-31`) or date time (`yyyy-MM-ddTHH:mm:ss.S+X` eg `2023-01-31T13:30:00.000Z`) in format [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) - name: updated_at required: false in: query description: "Filter items by the `updated_at.{operator}` field. \nYou can use the `eq`, `not_eq`, `gt`, `gte`, `lt`\ \ and `lte` operators, the `eq` operator being the default." schema: type: string pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}(T[0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,3})?(Z|([0-9]{2}:[0-9]{2}))?)?$ example: - '2023-01-31' - '2023-01-31T13:30:00Z' - '2023-01-31T13:30:00.000Z' description: Date (`yyyy-MM-dd` eg `2023-01-31`) or date time (`yyyy-MM-ddTHH:mm:ss.S+X` eg `2023-01-31T13:30:00.000Z`) in format [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) - name: last_activity_at required: false in: query description: "Filter items by the `last_activity_at.{operator}` field. \nYou can use the `eq`, `not_eq`, `gt`, `gte`,\ \ `lt` and `lte` operators, the `eq` operator being the default." schema: type: string pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}(T[0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,3})?(Z|([0-9]{2}:[0-9]{2}))?)?$ example: - '2023-01-31' - '2023-01-31T13:30:00Z' - '2023-01-31T13:30:00.000Z' description: Date (`yyyy-MM-dd` eg `2023-01-31`) or date time (`yyyy-MM-ddTHH:mm:ss.S+X` eg `2023-01-31T13:30:00.000Z`) in format [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) - name: sort required: false in: query description: "Use this parameter to sort query results. \nIf not specified, sorted in _ascending_ order with values\ \ of field `updated_at`. \nAvailable fields are `created_at`, `last_activity_at` and `updated_at`." schema: default: updated_at type: string examples: created_at: summary: Sort by values of the "created_at" field in ascending order value: created_at last_activity_at: summary: Sort by values of the "last_activity_at" field in descending order value: last_activity_at.desc updated_at: summary: Sort by values of the "updated_at" field in ascending order value: updated_at multiple: summary: Sort by values of multiple fields value: created_at,last_activity_at.desc - name: page required: false in: query description: "Query response is paginated. \nUse this parameter to choose which page you want to display. \nPage\ \ index starts at 1 (the default)." schema: default: 1 type: number minimum: 1 - name: limit required: false in: query description: "Query response is paginated. \nUse this parameter to choose the number of items per page. \nLimit\ \ defaults to 20, maximum value is 100." schema: type: number default: 20 minimum: 1 maximum: 100 responses: '200': description: 'List of checks created in the workspace **â„šī¸ Click to see full payload**' content: application/json: schema: $ref: '#/components/schemas/CheckList' '400': description: "The request is either malformed or contain invalid parameters.\n\n - One or multiple filtering parameters\ \ might be malformed. Make sure to use a supported operator and value for each filter.\n - If specified, make\ \ sure the value of the `page` or `limit` query parameter are valid.\n - Value of the `sort` parameter is invalid.\ \ Make sure the field name is supported, the sorting order is correctly specified, and a same field is not used\ \ multiple times for sorting.\n " tags: - Checks /v1/checks/{id}: delete: operationId: check-delete-one summary: Delete a check description: 'Delete the specified check. ' parameters: - name: id required: true in: path description: Id of the check schema: format: uuid type: string responses: '204': description: '' '400': description: "The request is either malformed or contain invalid parameters.\n\n - Make sure the identifier specified\ \ in the URL is a valid UUID\n " '404': description: No check can be found. tags: - Checks components: securitySchemes: DotfileAPIKey: type: apiKey in: header name: X-DOTFILE-API-KEY description: Configure your api key in the Workspace settings