ValidationSet

Queries the validation rapids for a specific validation set.

Changed on
get/validation-set/{validationSetId}/rapids

Request

  • Base URL
    https://api.rapidata.ai
  • URL
    https://api.rapidata.ai/validation-set/{validationSetId}/rapids
  • Auth
    OpenID Connect (https://auth.rapidata.ai/.well-known/openid-configuration, scopes: openid, profile, email, offline_access, api)

Path parameters

validationSetIdstring required

The validation set to query.

Query parameters

pageinteger

The 1-based page index.

page_sizeinteger

The number of items per page.

sortstring[]

Sort fields. Prefix with - for descending order (e.g. -created_at).

eqstring
neqstring
gtstring
gtestring
ltstring
ltestring
containsstring
starts_withstring
ends_withstring
instring[]
not_containsstring

Filter by id.

eqstring
neqstring
gtstring
gtestring
ltstring
ltestring
containsstring
starts_withstring
ends_withstring
instring[]
not_containsstring

Filter by type.

eqstring
neqstring
gtstring
gtestring
ltstring
ltestring
containsstring
starts_withstring
ends_withstring
instring[]
not_containsstring

Filter by state.

logic'and' | 'or'

How to combine the field filters: "and" (default) requires every filter to match, "or" requires any of them to match.

Response

OK

totalinteger required
pageinteger required
pageSizeinteger required
totalPagesinteger

Changes

  • 21c16ab2e7abRevision changes
    • info

      added the optional property /////////// to the response with the status

    • info

      added the optional property /////////// to the response with the status

  • ebc7fbc31114Revision changes
    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • breaking

      the ///////////////// response's property format changed from date-time to no format for status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status

    • info

      the ///////////////// response's property pattern ^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$ was added for the status