---
title: "POST /filedrop/udl-itemtracking"
method: POST
path: "/filedrop/udl-itemtracking"
tags: ["AirOperations"]
---

# POST /filedrop/udl-itemtracking

`POST /filedrop/udl-itemtracking`

## Request

- Base URL: `https://unifieddatalibrary.com`
- URL: `https://unifieddatalibrary.com/filedrop/udl-itemtracking`
- Auth: none declared

Service operation to take multiple itemtracking records 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

- ItemTrackingIngest[]
  - `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.
  - `scanCode` string, required: The tracking identifier of an item or person. May be similar in representation of a barcode or UPC.
  - `scGenTool` string: The algorithm name or standard that generated the scanCode (e.g. UPC-A, EAN-13, GTIN, SSCC, bID, JAN, etc.).
  - `scannerId` string, required: The ID of the scanner or input device.
  - `ts` string, date-time, required: The timestamp of the scan, in ISO 8601 UTC format with millisecond precision.
  - `idItem` string: The UDL ID of the item this record is associated with.
  - `type` string: The type of item that is being scanned (e.g. CARGO, PERSON, MAIL, MICAP, OTHER).
  - `lat` number, double: WGS84 latitude where the item was scanned, in degrees.
  - `lon` number, double: WGS84 longitude where the item was scanned, in degrees.
  - `scanType` string: The type of scan for tracking the item within it's journey (e.g. IN, OUT, RECEIVED, DELIVERED, TRANSIT, ABANDONDED, REFUSED, UNABLE, RETURNED, HELD, OTHER). For example, received and delivered are for when an item is received from or delivered to the end customer. In and out are for stops in between such as being loaded on an airplane or received at a warehouse.
  - `dvCode` string: The United States distinguished visitor code of the person scanned, only applicable to people.
  - `notes` string: Optional notes or comments about the tracking data.
  - `keys` string[]: Array of keys that may be associated with this tracked item.
  - `values` string[]: Array of values for the keys that may be associated to this tracked item. The entries in this array must correspond to the position index in the keys array. This array must be the same length as keys.
  - `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' | '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.

## 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-itemtracking/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)