CRS required fields missing across a selection
POST
/api/v1/applications/bulk/export/crs-gaps
One row per application in the export that is missing CRS fields, including cascaded descendants that land in the file, so clients can warn before it is produced.
Authorizations
Section titled “ Authorizations ”Request Bodyrequired
Section titled “ Request Bodyrequired ” Media type application/json
object
applicationIds
required
Array<string>
Example
{ "applicationIds": [ "68f2c1a9d4b1f2a3c4d5e6fa", "68f2c1a9d4b1f2a3c4d5e6fb" ]}Responses
Section titled “ Responses ” Media type application/json
object
applications
required
One row per application in the export that is missing CRS fields, cascaded descendants included
Array<object>
object
applicationId
required
string
name
required
Display name of the applicant entity or person
string
missingFieldCount
required
CRS required fields the generator would emit a placeholder for
number
Example
{ "applications": [ { "applicationId": "68f2c1a9d4b1f2a3c4d5e6fa", "name": "Acme Corporation", "missingFieldCount": 3 } ]}