Skip to content

Commit

Permalink
fix typos in logistics object and missing action request status
Browse files Browse the repository at this point in the history
  • Loading branch information
aloccid-iata committed Dec 6, 2024
1 parent 69766c6 commit bdb3cf9
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Documentation_website/docs/API-Security/logistics-objects.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,7 @@ The following HTTP headers parameters MUST be present in the response:
| **Last-Modified** | Date and time when the Logistics Object was last time changed. Syntax: `Last-Modified: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT`. See https://developer.mozilla.org/en-US/docs/Web/ | Tue, 21 Feb 2023 07:28:00 GMT |

!!! note

The JSON payload of the logistics object MUST include the **Revision** and **Latest-Revision** properties, represented by [`hasRevision`](https://onerecord.iata.org/ns/api#hasRevision) and [`hasLatestRevision`](https://onerecord.iata.org/ns/api#hasLatestRevision). When the query parameter `embedded` is set to `true`, each nested returned logistics object MUST contain the **Revision** and **Latest-Revision**. For an example, refer to the ["Get a Logistics Object"](#get-a-logistics-object) section.
The JSON payload of the logistics object MUST include the **Revision** and **Latest-Revision** properties, represented by [`hasRevision`](https://onerecord.iata.org/ns/api#hasRevision) and [`hasLatestRevision`](https://onerecord.iata.org/ns/api#hasLatestRevision). When the query parameter `embedded` is set to `true`, each nested returned logistics object MUST contain the **Revision** and **Latest-Revision**. For an example, refer to the [`Get a Logistics Object`](#get-a-logistics-object) section.

The following HTTP status codes MUST be supported:

Expand Down Expand Up @@ -464,7 +463,8 @@ classDiagram
REQUEST_ACCEPTED
REQUEST_REJECTED
REQUEST_FAILED
REQUEST_REVOKED
REQUEST_REVOKED
REQUEST_ACKNOWLEDGED
}
```

Expand Down

0 comments on commit bdb3cf9

Please sign in to comment.