Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/api-docs/in-depth-guides/adding-customer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,8 @@ Adding a party to a tracking request associates customer information with the re

You can either find an existing party or create a new one.

- To find an existing party, jump to [Listing all parties](#listing-all-parties) section.
- To create a new party, jump to [Adding party for a customer](#adding-party-for-a-customer) section.
- To find an existing party, jump to [Listing all parties](#list-all-parties) section.
- To create a new party, jump to [Adding party for a customer](#create-a-party-for-a-customer) section.

## List all parties

Expand Down
2 changes: 1 addition & 1 deletion docs/api-docs/in-depth-guides/event-timestamps.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Event timestamps are stored and returned in UTC. If you wish to present them in

### Example

If you receive a container model with the attributes
If you receive a container model with the attributes
```
'pod_arrived_at': '2022-12-22T07:00:00Z',
'pod_timezone': 'America/Los_Angeles',
Expand Down
4 changes: 2 additions & 2 deletions docs/api-docs/useful-info/test-numbers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,14 @@ Test numbers do not simulate every milestone, ETA, LFD, or availability event. T

## Tracking request API
You create shipments by making requests to the tracking request API.
When using the API , ensure that:
When using the API, ensure that:
- you set the test number in `request_number` attribute in the request body
- you set the `scac` attribute to `TEST` in the request body


## Test numbers

Number. | Use Case
Number | Use Case
-------------------|---------
TEST-TR-SUCCEEDED | Test the `tracking_request.succeeded` outcome and webhook
TEST-TR-FAILED | Test the `tracking_request.failed` outcome and webhook
2 changes: 1 addition & 1 deletion docs/datasync/table-properties/containers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ This is a large table with denormalized columns to make it easy to use for repor
| `equipment_type` | Container type: Dry, Flat Rack, Open Top, Reefer, Tank, unknown | `text` |
| `equipment_height` | Container height: High Cube, Standard, unknown | `text` |
| `equipment` | Concatenation of the equipment_length, equipment_type, and equipment_height | `text` |
| `weight_in_lbs` | Weight of the containre in lbs | `integer` |
| `weight_in_lbs` | Weight of the container in lbs | `integer` |
| `seal_number` | Seal number of the container | `text` |
| `pod_full_out_chassis_number` | The chassis number used when container was picked up at POD, if available | `text` |
| `pol_voyage_number` | Voyage number of the vessel that departed or will depart from the POL | `text` |
Expand Down
4 changes: 2 additions & 2 deletions docs/datasync/table-properties/containers_rail.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ _Columns marked with * are only included with the Intermodal Rail product._
| `ind_rail_unloaded_at`* | Inland Destination Rail Unloaded, as a UTC timestamp | `timestamp`|
| `ind_rail_unloaded_at_local`* | Inland Destination Rail Unloaded, as a string in the Inland Destination local time zone | `text` |
| `ind_last_free_day_on`* | Last Free Day at the inland destination facility from the rail carrier, as a UTC timestamp<br /><br />Named `ind_facility_lfd_on` in the API | `timestamp`|
| `ind_last_free_day_on_local`* | Last Free Day at the inland destination facility from the rail carrier, as a string in the inland estination local time zone | `text` |
| `ind_last_free_day_on_local`* | Last Free Day at the inland destination facility from the rail carrier, as a string in the inland destination local time zone | `text` |
| `ind_full_out_at` | Inland Destination Full Out event, as a UTC timestamp<br /><br />Named `final_destination_full_out_at` in the API | `timestamp`|
| `ind_full_out_at_local` | Inland Destination Full Out event, as a string in the Inland Destination local time zone | `text` |
| `empty_terminated_at` | Container Empty Returned event, as a UTC timestamp | `timestamp`|
Expand All @@ -114,7 +114,7 @@ _Columns marked with * are only included with the Intermodal Rail product._
| `equipment_type` | Container type: Dry, Flat Rack, Open Top, Reefer, Tank, unknown | `text` |
| `equipment_height` | Container height: High Cube, Standard, unknown | `text` |
| `equipment` | Concatenation of the equipment_length, equipment_type, and equipment_height | `text` |
| `weight_in_lbs` | Weight of the containre in lbs | `integer` |
| `weight_in_lbs` | Weight of the container in lbs | `integer` |
| `seal_number` | Seal number of the container | `text` |
| `pod_full_out_chassis_number` | The chassis number used when container was picked up at POD, if available | `text` |
| `pod_voyage_number` | Voyage number of the vessel that arrived or will arrive at the POD | `text` |
Expand Down
2 changes: 1 addition & 1 deletion docs/datasync/table-properties/shipments.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ A shipment contains 1 or more containers.
| `shipping_line_name` | Name of the shipping line | `text` |
| `bill_of_lading_number` | Shipment number exactly as submitted in the tracking request. May differ from `normalized_number` when the carrier expects a different format. | `text` |
| `normalized_number` | The normalized version of the shipment number that Terminal49 uses when querying the carrier. Some carriers require a specific format (for example a stripped prefix or padded digits), so this value may differ from `bill_of_lading_number`. | `text` |
| `reference_numbers` | Reference numbers of the shipment, contatenated | `text` |
| `reference_numbers` | Reference numbers of the shipment, concatenated | `text` |
| `tags` | Tags added to the shipment, sorted by alphabetical order, concatenated and separated by a comma | `text` |
| `customer_id` | Account ID of the customer | `text` |
| `customer_name` | Name of the customer | `text` |
Expand Down
Loading