Get an internal note

An inter­nal note added to a freight can be down­loaded at any time.

The freight-id iden­ti­fi­ca­tion num­ber in method call can be tak­en from response after cre­at­ing the freight or by down­load­ing the freight list.

GET
/ext/freights-api/v1/freights/{freight-id}/internal-note
Request Authorization

Every request MUST include a valid access token obtained dur­ing the user autho­riza­tion process, pro­vid­ed using the Bear­er token scheme in the Autho­riza­tion head­er.

Successful Response
Request Header
GET /ext/freights-api/v1/freights/{freight-id}/internal-note HTTP/1.1 
Host: api.platform.trans.eu 
Content-Type: application/json
Accept: application/json
Authorization: Bearer {access_token) 
Api-key: {unique_app_api-key}
Response Fields
AttributeTypeExam­pleDescrip­tion
con­tentsString“Mem­o­ry note”Con­tent of the inter­nal note
Example Response Body
{ 
"contents": "Memory note" 
}

Client errors (code 400)

HTTP 4xx sta­tus codes indi­cate client errors, mean­ing that the request could not be processed due to an issue on the client side. Below is a list of request-spe­cif­ic errors.

Example error 1

Inter­nal note does not exists

{
    "detail": "Freight (id: 3772908) does not have any internal note",
    "status": 404,
    "title": "Not Found",
    "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"
}
Example error 2

Incor­rect freight id

{
    "detail": "Freight 1234 not found or not accessible",
    "status": 404,
    "title": "Not Found",
    "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"
}