--- title: "POST /filedrop/udl-collectresponse" method: POST path: "/filedrop/udl-collectresponse" tags: ["Sensor Tasking"] --- # POST /filedrop/udl-collectresponse `POST /filedrop/udl-collectresponse` ## Request - Base URL: `https://unifieddatalibrary.com` - URL: `https://unifieddatalibrary.com/filedrop/udl-collectresponse` - Auth: none declared Service operation to take a list of CollectResponse as a POST body and ingest into the database. This operation is intended to be used for automated feeds into UDL. A specific role is required to perform this service operation. Please contact the UDL team for assistance. ## Request body - CollectResponseIngest[] - `id` string: Unique identifier of the record, auto-generated by the system. - `classificationMarking` string, required: Classification marking of the data in IC/CAPCO Portion-marked format. - `idRequest` string, required: Unique identifier of the request associated with this response. - `idOnOrbit` string: Unique identifier of the target on-orbit object associated with this response. - `origObjectId` string: Optional identifier provided by data source to indicate the target object of this response. This may be an internal identifier and not necessarily a valid satellite number. - `satNo` integer: Satellite/catalog number of the target on-orbit object. - `taskId` string: Optional task ID associated with the request/response. - `idPlan` string: Unique identifier of the parent plan or schedule associated with the request/response. - `externalId` string: UUID from external systems. This field has no meaning within UDL and is provided as a convenience for systems that require tracking of internal system generated ID. - `status` string: The status of the request (ACCEPTED, CANCELLED, COLLECTED, COMPLETED, DELIVERED, FAILED, PARTIAL, PROPOSED, REJECTED, SCHEDULED): ACCEPTED: The collect or contact request has been received and accepted. CANCELLED: A previously scheduled collect or contact whose execution was cancelled. COLLECTED: The collect has been accomplished. A collected state implies that additional activity is required for delivery/completion. COMPLETED: The collect or contact has been completed. For many systems completed and delivered constitute an equivalent successful end state. DELIVERED: The collected observation(s) have been delivered to the requestor. For many systems completed and delivered constitute an equivalent successful end state. A DELIVERED state is typically used for systems that exhibit a delay between collect and delivery, such as with space-based systems which require ground contact to deliver observations. FAILED: The collect or contact was attempted and failed, or the delivery of the collected observation(s) failed. A FAILED status may be accompanied by an error code (errCode), if available. PARTIAL: A PARTIAL state indicates that a part of a multi-track request has been accomplished, but the full request is incomplete. A PARTIAL status should ultimately be resolved to an end state. PROPOSED: Indicates that the request was received and alternate collect or contact time(s) (altStartTime, altEndTime) have been proposed. If an alternate is accepted by the requestor the current request should be cancelled and a new request created. REJECTED: The request has been received and rejected by the provider. A REJECTED status may be accompanied by an explanation (notes) of the reason that the request was rejected. SCHEDULED: The request was received and has been scheduled for execution. - `actualStartTime` string, date-time: The actual start time of the collect or contact, in ISO 8601 UTC format. - `actualEndTime` string, date-time: The actual end time of the collect or contact, in ISO 8601 UTC format. - `altStartTime` string, date-time: Proposed alternative start time, in ISO 8601 UTC format. - `altEndTime` string, date-time: Proposed alternative end time, in ISO 8601 UTC format. - `errCode` string: Error code associated with this request/response. - `srcTyps` string[]: Array of UDL record type(s) (DOA, ELSET, EO, RADAR, RF, SV) collected or produced in response to the associated request. See the associated 'srcIds' array for the record UUIDs, positionally corresponding to the record types in this array. The 'srcTyps' and 'srcIds' arrays must match in size. The appropriate API operation can be used to retrieve the specified object(s) (e.g. /udl/rfobservation/{uuid}). - `srcIds` string[]: Array of UUIDs of the UDL data record(s) collected in response to the associated request. See the associated 'srcTyps' array for the specific types of data, positionally corresponding to the UUIDs in this array. The 'srcTyps' and 'srcIds' arrays must match in size. The appropriate API operation can be used to retrieve the specified object(s) (e.g. /udl/rfobservation/{uuid}). - `notes` string: Notes or comments associated with this response. - `createdAt` string, date-time: Time the row was created in the database, auto-populated by the system. - `createdBy` string: Application user who created the row in the database, auto-populated by the system. - `source` string, required: Source of the data. - `origin` string: Originating system or organization which produced the data, if different from the source. The origin may be different than the source if the source was a mediating system which forwarded the data on behalf of the origin system. If null, the source may be assumed to be the origin. - `origNetwork` string: The originating source network on which this record was created, auto-populated by the system. - `idSensor` string: Unique identifier of the reporting sensor. - `origSensorId` string: Optional identifier provided by the collection source to indicate the sensor identifier responding to this collect or contact. This may be an internal identifier and not necessarily a valid sensor ID. - `dataMode` 'REAL' | 'TEST' | 'SIMULATED' | 'EXERCISE', required: Indicator of whether the data is REAL, TEST, EXERCISE, or SIMULATED data: REAL: Data collected or produced that pertains to real-world objects, events, and analysis. TEST: Specific datasets used to evaluate compliance with specifications and requirements, and for validating technical, functional, and performance characteristics. EXERCISE: Data pertaining to a government or military exercise. The data may include both real and simulated data. SIMULATED: Synthetic data generated by a model to mimic real-world datasets. - `tags` string[]: Optional array of provider/source specific tags for this data, where each element is no longer than 32 characters, used for implementing data owner conditional access controls to restrict access to the data. Should be left null by data providers unless conditional access controls are coordinated with the UDL team. ## Response `202` Accepted ## Other responses - `400`: Bad Request - `401`: Unauthorized - `403`: Forbidden - `429`: Rate of Requests Exceeds Allowed Limit - `500`: Internal Server Error ## Changes > 12 revisions in range; 1 could not be searched. - **2026-04-09** `bd17bc53681e`: 1 info - added the non-success response with the status `429` - **2025-04-16** `75f764c843a9`: 1 info - the endpoint scheme security `BasicAuth` was removed from the API [Operation history](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/changes/filedrop/udl-collectresponse/post.md) --- [API](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api.md) - [All operations](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/revisions/bd17bc53681e?raw)