Validate a revision — RIPS packages

POST/api/v1/workspaces/{workspaceId}/rips-packages/{packageId}/validations

Operation ID: ripsPackages.validate · Access: PAT with write scope and authorized workspace where applicable · Effect: write.

Read the rips packages workflow before this operation.

Read validation.outcome and its issues even on HTTP 200. The check applies to one revision and its current context.

Parameters

Name	In	Required	Type / allowed values
workspaceId	path	Yes	string
packageId	path	Yes	string

Request body

Content type: application/json · Required: yes.

Schema: RevisionInput. Browse schema fields.

Example: revision

Synthetic contract example. Replace identifiers and clinical data with authorized values. This example does not prove ministry acceptance.

Download JSON

{
  "revision": 1
}

Responses

HTTP	Content	Schema
200	application/json	RipsValidationResult
400	application/json	ApiError
401	application/json	ApiError
403	application/json	ApiError
404	application/json	ApiError
409	application/json	ApiError
413	application/json	ApiError
415	application/json	ApiError
422	application/json	ApiError
500	application/json	ApiError
502	application/json	ApiError
503	application/json	ApiError

Use error.code, error.issues, and requestId for JSON errors. Error and recovery guide.

cURL

Set the connection variables from the quickstart. Set each path variable to an authorized identifier or an allowed parameter value from the table above.

Save your authorized JSON input as request.json. Use the request schema and examples above; replace synthetic data before use.

curl --fail-with-body --request POST \
  "$RIPSCLOUD_BASE_URL/api/v1/workspaces/$WORKSPACE_ID/rips-packages/$PACKAGE_ID/validations" \
  --header "Authorization: Bearer $RIPSCLOUD_TOKEN" \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data-binary @request.json