---
title: "POST /udl/trackroute/createBulk"
method: POST
path: "/udl/trackroute/createBulk"
tags: ["AirOperations"]
---

# POST /udl/trackroute/createBulk

`POST /udl/trackroute/createBulk`

## Request

- Base URL: `https://unifieddatalibrary.com`
- URL: `https://unifieddatalibrary.com/udl/trackroute/createBulk`
- Auth: none declared

Service operation intended for initial integration only, to take a list of trackroute 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

- TrackRouteIngest[]
  - `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.
  - `type` string, required: The track route type represented by this record (ex. AIR REFUELING).
  - `externalId` string: Optional air refueling track ID from external systems. This field has no meaning within UDL and is provided as a convenience for systems that require tracking of an internal system generated ID.
  - `direction` string: The principal compass direction (cardinal or ordinal) of the track route.
  - `creatingOrg` string: The name of the creating organization of the track route.
  - `locationTrackId` string: Track location ID.
  - `trackId` string: Identifier of the track.
  - `trackName` string: Name of the track.
  - `shortName` string: Abbreviated name of the track.
  - `typeCode` string: Type of process used by AMC to schedule an air refueling event. Possible values are A (Matched Long Range), F (Matched AMC Short Notice), N (Unmatched Theater Operation Short Notice (Theater Assets)), R, Unmatched Long Range, S (Soft Air Refueling), T (Matched Theater Operation Short Notice (Theater Assets)), V (Unmatched AMC Short Notice), X (Unmatched Theater Operation Short Notice (AMC Assets)), Y (Matched Theater Operation Short Notice (AMC Assets)), Z (Other Air Refueling).
  - `regionCode` string: Region code indicating where the track resides as determined by the data source.
  - `regionName` string: Region where the track resides.
  - `apxBeaconCode` string: The APX radar code sent and received by the aircraft for identification.
  - `receiverTankerCHCode` string: The receiver tanker channel identifer for air refueling tracks.
  - `apnSetting` string: The APN radar code sent and received by the aircraft for identification.
  - `sic` string: Standard Indicator Code of the air refueling track.
  - `reviewDate` string, date-time: Date the track needs to be reviewed for accuracy or deletion in ISO 8601 UTC format with millisecond precision.
  - `lastUsedDate` string, date-time: Used to show last time the track route was added to an itinerary in ISO 8601 UTC format with millisecond precision.
  - `lastUpdateDate` string, date-time, required: The last updated date of the track route in ISO 8601 UTC format with millisecond precision.
  - `priFreq` number, double: The primary UHF radio frequency used for the track route in megahertz.
  - `secFreq` number, double: The secondary UHF radio frequency used for the track route in megahertz.
  - `artccMessage` string: Air Refueling Track Control Center message.
  - `schedulerOrgName` string: Point of contact for the air refueling track route scheduler.
  - `schedulerOrgUnit` string: The unit responsible for scheduling the track route.
  - `effectiveDate` string, date-time: The date which the DAFIF track was last updated/validated in ISO 8601 UTC format with millisecond precision.
  - `routePoints` RoutePointsIngest[]: Points identified within the route.
    - `ptSequenceId` integer: Sequencing field for the track route. This is the identifier representing the sequence of waypoints associated to the track route.
    - `ptTypeCode` string: Code representation of the point within the track route (ex. EP, EX, CP, IP, etc.).
    - `ptTypeName` string: The name that represents the point within the track route (ex. ENTRY POINT, EXIT POINT, CONTROL POINT, INITIAL POINT, etc.).
    - `waypointName` string: Name of a waypoint which identifies the location of the point.
    - `dafifPt` boolean: Flag indicating this is a Digital Aeronautical Flight Information File (DAFIF) point.
    - `ptLat` number, double: WGS84 latitude of the point location, in degrees. -90 to 90 degrees (negative values south of equator).
    - `ptLon` number, double: WGS84 longitude of the point location, in degrees. -180 to 180 degrees (negative values west of Prime Meridian).
    - `magDec` number, double: The magnetic declination/variation of the route point location from true north, in degrees. Positive values east of true north and negative values west of true north.
    - `navaidLength` number, double: The length of the course from the Navigational Aid (NAVAID) in nautical miles.
    - `navaid` string: Navigational Aid (NAVAID) identification code.
    - `countryCode` string: The DoD Standard Country Code designator for the country where the route point resides. This field should be set to "OTHR" if the source value does not match a UDL country code value (ISO-3166-ALPHA-2).
    - `altCountryCode` string: Specifies an alternate country code if the data provider code is not part of an official NAVAID Country Code standard such as ISO-3166 or FIPS. This field will be set to the value provided by the source and should be used for all Queries specifying a Country Code.
    - `navaidType` string: The NAVAID type of this route point (ex. VOR, VORTAC, TACAN, etc.).
  - `altitudeBlocks` AltitudeBlocksIngest[]: Minimum and maximum altitude bounds for the track.
    - `altitudeSequenceId` string: Sequencing field for the altitude block.
    - `lowerAltitude` number, double: Lowest altitude of the track route altitude block above mean sea level in feet.
    - `upperAltitude` number, double: Highest altitude of the track route altitude block above mean sea level in feet.
  - `poc` PointOfContactIngest[]: Point of contacts for scheduling or modifying the route.
    - `pocSequenceId` integer: Sequencing field for point of contact.
    - `pocTypeName` string: A code or name that represents the contact's role in association to the track route (ex. Originator, Scheduler, Maintainer, etc.).
    - `pocName` string: The name of the contact.
    - `office` string: Office name for which the contact belongs.
    - `username` string: The username of the contact.
    - `rank` string: The rank of contact.
    - `pocOrg` string: Organization name for which the contact belongs.
    - `phone` string: Phone number of the contact.
    - `remark` string: Text of the remark.
  - `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.
  - `updatedAt` string, date-time: Time the row was updated in the database, auto-populated by the system.
  - `updatedBy` string: Application user who updated 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 `204`

Success

## Other responses

- `400`: Bad Request
- `401`: Invalid/Missing User Credentials
- `403`: User Is Not Authorized
- `405`: Method Not Allowed
- `415`: MediaType Unsupported
- `429`: Rate of Requests Exceeds Allowed Limit
- `500`: Internal Server Error

## Changes

> 12 revisions in range; 1 could not be searched.

- **2025-09-26** `45631f9bb3f0`: 1 breaking
  - the `items/origNetwork` request property's minLength was increased from `0` to `1`
- **2025-04-16** `75f764c843a9`: 2 info
  - api operation id `createBulks_40` removed and replaced with ``
  - the endpoint scheme security `BasicAuth` was removed from the API

[Operation history](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/changes/udl/trackroute/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)
