Update requirement values in requirement group
Updates the customer reference or regulatory requirement values on the specified requirement group. The response contains the updated group.
Path parameters
ID of the requirement group
Request body
Example request
{
"customer_reference": "0002",
"regulatory_requirements": [
{
"requirement_id": "53970723-fbff-4f46-a975-f62be6c1a585",
"field_value": "new requirement value"
}
]
}Response
Updated requirement group
Example response
{
"record_type": "requirement_group"
}Changes
Changed in 3 of the 99 revisions of this API.251025
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromint32to no format for statusresponse-property-type-changed
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format from no format toint32for statusresponse-property-type-changed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
///from the response with the statusresponse-optional-property-removed
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the response property
//became required for the statusresponse-property-became-required
This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
Of the 99 revisions, 1 has no diff computed.