Adding Custom Fields When Creating Tracking Request

Last updated: December 3, 2025

Most teams prefer to populate Custom Fields at the moment tracking is created.

Tracking by CSV

Custom Fields are supported within the Bulk Spreadsheet Upload page.

Once configured, you can:

  • Upload a file, or

  • Enter data manually in the grid, including Custom Fields.

image.png

Include Custom Field columns using these naming conventions:

  • shipment-<field_identifier>

  • container-<field_identifier>

Your Customer Success contact can confirm correct field identifiers.

As Terminal49 processes your CSV:

  • Tracking is created.

  • Custom Field values are populated on the relevant shipments and containers.

Tracking via Email (CSV Attachment)

Use the same column headers as CSV uploads.
Custom Field values are applied as part of that import.

Custom Fields in API & Webhooks

Custom Fields are fully available throughout the Terminal49 API.

Using Custom Fields via API

  • Include Custom Fields when creating tracking (ex. POST Tracking requests).

  • Read Custom Field values through:

    • Fetching shipments and containers via GET endpoints

    • Receiving updates via webhooks

The API exposes Custom Fields in structured format for both shipments and containers, so your systems can:

  • Send values to Terminal49.

  • Store the values returned from Terminal49 for matching and sync.

For details on request/response formats:

  • See the Custom Fields section in the Terminal49 API documentation.

  • Or ask your Customer Success contact for API examples.

See next article: Custom Fields - Example Workflows

If you need help with adding Custom Fields when creating tracking requests or have any other questions, the fastest way to get assistance is through our in-app chat. You can also reach us at support@terminal49.com.