Skip to content

Releases: drewry-uk/openapi

v1.1.0 API Release

30 Oct 05:57
Compare
Choose a tag to compare

v1.1.0

Changelog

All notable changes to this project will be documented in this file. Dates are displayed in UTC.

 [1.1.0](1.0.8...1.1.0)

> 29 October 2020

- Release 1.1.0 [`edd449e`](edd449e)

[1.0.8](v1.0.7...1.0.8)

> 29 October 2020

- refactor(api): refactor deps and build [`e246762`](e246762)

- update build [`2b42e4e`](2b42e4e)

- Release 1.0.8 [`22e7425`](22e7425)

#### [v1.0.7](1.0.4...v1.0.7)

> 19 October 2020

- feat(v1.0.8): 1.0.8 release [`8d883bd`](8d883bd)

- fixing some API documentation [`499f5fb`](499f5fb)

- feat(refactor): refactor and new updates to api [`78f21df`](78f21df)

#### [1.0.4](1.0.2...1.0.4)

> 10 August 2020

- 1.0.5+alpha [`#2`](#2)

- v1.0.3 [`#4`](#4)

- feat(bunp): patch update to api [`d90fbbc`](d90fbbc)

- Initial commit from create-openapi-repo [`3bd2d7f`](3bd2d7f)

- feat(v1.0.5+beta): version 1.0.5+beta release [`a8626ba`](a8626ba)

#### [1.0.2](v1.0.1...1.0.2)

> 1 August 2020

- Release 1.0.2 [`773bfe1`](773bfe1)

#### [v1.0.1](1.0.1...v1.0.1)

> 1 August 2020

- v1.0.3 [`#4`](#4)

- Initial commit from create-openapi-repo [`3bd2d7f`](3bd2d7f)

- feat(api improvements): changed some syntax and switched PUT to POST [`dbfcdd3`](dbfcdd3)

- feat(v1.0.5+beta): version 1.0.5+beta release [`a8626ba`](a8626ba)

[1.0.1](v1.0.0+stable...1.0.1)

> 1 August 2020

#### v1.0.0+stable

> 1 August 2020

- Revert "drewry container freight" [`38cb133`](38cb133)

- drewry container freight [`2316b7d`](2316b7d)

- feat(v1.0.0+release): api release v1 [`36b9b8a`](36b9b8a)

Drewry Container Freight Benchmark Index API

01 Aug 16:37
ad39bfc
Compare
Choose a tag to compare

Drewry Freight API

Drewry Publishes Specific contract-routes for Container Frieght Pricing (Maritime). This endpoint returns all the Price Releases you can access according to your current subscription.

Drewry releases (publishes) prices several times per week, which is called Price Release. Please read our Methodology and Specifications Guide for more details.

For a specific contract, this endpoint (pictured below) returns the latest Price Releases if, according to your current subscription, you can access it. Drewry releases (publishes) prices several times per week, which is called Price Release. Please read our Methodology and Specifications Guide for more details.

{ "/v1.0/contracts/{contract_ticker_symbol}/price-releases/latest/": {
            "get": {
                "tags": [
                    "Contracts & Price Releases"
                ],
                "summary": "Read Latest Price Release",
                "description": ".",
                "operationId": "read_latest_price_release_v1_0_contracts__contract_ticker_symbol__price_releases_latest__get",
                "parameters": [
                    {
                        "required": true,
                        "schema": {
                            "title": "Contract Ticker Symbol",
                            "type": "string"
                        },
                        "name": "contract_ticker_symbol",
                        "in": "path"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {
                                "schema": {
                                    "$ref": "#/components/schemas/PriceReleaseDetailResponse"
                                }
                            }
                        }
                    }
DATA REVISION POLICY

Drewry will on occasion publish corrections to price assessments after the publication date. These errors may arise from clerical mistakes or miscalculation errors amongst other reasons. Any changes or revisions will take place within two working days following the closing of the submission window. Drewry will send a notification of any changes to its previous assessments via email to all users with an explanation as to why a correction was implemented.