--- title: "POST /udl/sensormetrics/createBulk" method: POST path: "/udl/sensormetrics/createBulk" tags: ["Sensor"] --- # POST /udl/sensormetrics/createBulk `POST /udl/sensormetrics/createBulk` ## Request - Base URL: `https://unifieddatalibrary.com` - URL: `https://unifieddatalibrary.com/udl/sensormetrics/createBulk` - Auth: none declared Service operation intended for initial integration only, to take a list of SensorMetrics records as a POST body and ingest into the database. This operation is not intended to be used for automated feeds into UDL. Data providers should contact the UDL team for specific role assignments and for instructions on setting up a permanent feed through an alternate mechanism. ## Request body - SensorMetricsIngest[] - `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. - `startTime` string, date-time, required: The start time of the observation window, in ISO 8601 UTC format with millisecond precision. - `duration` integer: The duration of the observation window for this data record, in days. - `idSensor` string: Unique identifier of the sensor from which the signature data applied in this assessment was collected. This ID can be used to obtain additional information on a sensor using the 'get by ID' operation (e.g. /udl/sensor/{id}). For example, the sensor with idSensor = abc would be queried as /udl/sensor/abc. - `origSensorId` string: Optional identifier provided by the observation source to indicate the sensor which produced these observations. This may be an internal identifier and not necessarily a valid sensor ID. - `idSite` string: Unique identifier of the site associated with the sensor(s) referenced in this record. This ID can be used to obtain additional information on a site using the 'get by ID' operation (e.g. /udl/site/{id}). For example, the site with idSite = abc would be queried as /udl/site/abc. - `origSiteId` string: Optional identifier provided by the observation source to indicate the site from which these observations originated. This may be an internal identifier and not necessarily a valid site ID. - `sensorNetwork` string: Identifies the network or grouping of sensors associated with the site that collectively contributed to these observations when this record represents more than one sensor. - `aggregationType` string: Indicates whether the object count metrics are computed for a single sensor pairing or for a group of sensors. Use PAIRED when this record represents a single sensor. These metrics are for the sensor that paired with that sensor to track the most or second-most near-unique objects. Use GROUP when this record represents a group of sensors. These metrics are for the sensor in that group that tracked the most and second-most total objects. - `avgUptime` number, double: Average percentage of time per day the sensor or site is available for tasking, taking into account outages for weather, maintenance, and any other reasons. Values are between 0.0 and 100.0. - `avgMaxNumTracks` number, double: Average maximum number of tracks per hour based on performance statistics. This should not be interpreted as a capacity limit, as it combines sensor constraints and tasking; rather, it is a rough estimate of the number of trackable objects. - `cadence` number, double: Rate at which the sensor transmits data, in minutes. - `avgLatency` number, double: Average delay between observation collection and data transmission, in minutes. - `latencySigma` number, double: Standard deviation of the delay between observation collection and data transmission, in minutes. - `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. - `transactionId` string: Optional identifier to track a commercial or marketplace transaction executed to produce this data. - `sensorMetricsTrackedElement` SensorMetricsTrackedElementIngest[]: Collection of element counts for all combinations of element type, uniqueness, and orbit type. - `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. - `idSensorMetrics` string: Unique identifier of the sensor metrics from which the signature data applied in this assessment was collected, auto-populated by the system. - `element` string: Specifies the element represented in this record (e.g., OBJECT, OBSERVATION, TRACK). - `elementType` string: Specifies the element type. For OBJECTS, this includes: ACTIVE PAYLOAD, ANALYST, DEAD PAYLOAD, DEBRIS, PLATFORM, ROCKET BODY, or ALL OBJ to represent all object types. For OBSERVATIONS, this includes: ASSOC (observation associated to a known object by the observation association system), DETAG (incorrect correlation to an object made by the sensor that was removed/unassociated by the observation association system), MANDETAG (incorrect correlation to an object made by the sensor that was removed/unassociated manually by an analyst), MISTAG (incorrect correlation to a known object made by the sensor that was corrected/associated to a different object by the observation association system), RETAG (no correlation made by the sensor but then associated to a known object by the observation association system), SYSMISTAG (incorrect association to an object made by the observation association system), UCT (observation not associated to a known object by the observation association system), or ALL OBS to represent all observation types. - `uniqueness` string: Indicates whether the element was tracked only by the specified sensor for this record (UNIQUE), by the specified sensor and exactly one other sensor (NEAR UNIQUE), or by more than two sensors (NONE). - `elementOrbitType` string: Orbit regime of the tracked/collected element (e.g., DS for Deep Space, GEO for Geosynchronous, HSF for Human Space Flight, NE for Near Earth, or ALL to represent all regimes). - `numElements` integer: The number of elements tracked/collected during the specified observation window. - `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. - `sourceDL` string: The source data library from which this record was received. This could be a remote or tactical UDL or another data library. If null, the record should be assumed to have originated from the primary Enterprise UDL. - `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. - `dataMode` 'REAL' | 'TEST' | 'EXERCISE' | 'SIMULATED', 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. - `sensorMetricsTrackedAggregate` SensorMetricsTrackedAggregateIngest[]: Collection of aggregated counts of tracked unique and near-unique objects for single sensors or a group of sensors. - `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. - `idSensorMetrics` string: Unique identifier of the sensor metrics from which the signature data applied in this assessment was collected, auto-populated by the system. - `idSensorAgg` string: Indicates the sensor these metrics are computed for, depending on the aggregationType (PAIRED or GROUP). For PAIRED, this identifies which sensor paired up with the primary sensor to track the most or second-most near-unique (tracked by exactly two sensors) objects. For GROUP, this identifies the sensor that tracked the most or second-most combined unique (tracked by only one sensor) and near-unique (tracked by exactly two sensors) objects with the specified orbitType. This ID can be used to obtain additional information on a sensor using the 'get by ID' operation (e.g. /udl/sensor/{id}). For example, the sensor with idSensorAgg = abc would be queried as /udl/sensor/abc. - `origSensorAggId` string: Optional identifier of the idSensorAgg provided by the observation source. This may be an internal identifier and not necessarily a valid sensor ID. - `trackingRank` integer: Indicates if the specified pairSensor or groupSensor tracked the most (1) or second-most (2) objects during the observation window. - `objectType` string: Type of object tracked by the specified pairSensor or groupSensor (e.g., ACTIVE PAYLOAD, ANALYST, DEAD PAYLOAD, DEBRIS, PLATFORM, ROCKET BODY, etc. Use TOTAL to indicate all object types). - `orbitType` string: Orbit regime of the tracked objects (e.g., DS for Deep Space, GEO for Geosynchronous, HSF for Human Space Flight, NE for Near Earth). - `objectCount` integer: The number of objects with the specified objectType tracked by the pairSensor or groupSensor during the observation window. - `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. - `sourceDL` string: The source data library from which this record was received. This could be a remote or tactical UDL or another data library. If null, the record should be assumed to have originated from the primary Enterprise UDL. - `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. - `dataMode` 'REAL' | 'TEST' | 'EXERCISE' | 'SIMULATED', 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. - `sensorMetricsTasking` SensorMetricsTaskingIngest[]: Collection of tasking priority data for objects and tracks. - `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. - `idSensorMetrics` string: Unique identifier of the sensor metrics from which the signature data applied in this assessment was collected, auto-populated by the system. - `taskingSource` string: Specifies the element source (e.g., ANALYST-TRACKED, CATALOGED). - `taskingElement` string: Specifies the element represented in this record (e.g., OBJECT, OBSERVATION, TRACK). - `taskingMetric` string: Specifies the type of tasking information given in this record for the specified observation window. Options are TASKED (sensor or site was tasked to observe the element), ACQUIRED (sensor or site successfully acquired the element), RESPONSE RATIO (ratio of elements acquired to elements tasked), or NONE (sensor or site acquired an element without being tasked). - `category` string: The tasking category associated with these metrics. The tasking category defines the priority of gathering the requested observational data. Use SUM to represent the total across all categories. - `metricCount` number, double: The number of elements with the specified taskingSource, taskingElement, taskingMetric, and category. - `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. - `sourceDL` string: The source data library from which this record was received. This could be a remote or tactical UDL or another data library. If null, the record should be assumed to have originated from the primary Enterprise UDL. - `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. - `dataMode` 'REAL' | 'TEST' | 'EXERCISE' | 'SIMULATED', 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. - `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. - `sourceDL` string: The source data library from which this record was received. This could be a remote or tactical UDL or another data library. If null, the record should be assumed to have originated from the primary Enterprise UDL. - `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. - `dataMode` 'REAL' | 'TEST' | 'EXERCISE' | 'SIMULATED', 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. - `origNetwork` string: The originating source network on which this record was created, auto-populated by the system. ## Response `204` Success ## Other responses - `400`: Bad Request - `401`: Invalid/Missing User Credentials - `403`: User Is Not Authorized - `415`: MediaType Unsupported - `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 - endpoint added [Operation history](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/changes/udl/sensormetrics/createBulk/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)