contents is an older, deprecated way to pass parcel contents to Sendle on international orders. These days we prefer that integrations send the parcel_contents list instead – as this list allows multiple items to be defined, the quantity of each, etc.

Preferably, if contents is passed it would be translated into parcel_contents instead, like this:

input:

  "contents": {
    "description": "T-shirt",
    "value": "20.00",
    "country_of_origin": "China",
    "currency": "AUD"
  },

sent to the api:

  "parcel_contents": [
    {
      "description": "T-shirt",
      "value": "20.00",
      "country_of_origin": "China",
      "currency": "AUD"
    }
  ],

Hi,

I'd like to update the HTTP User-Agent header with our app reference information (e.g. refAABB123) so that Sendle can recognise our app more easily. Can I update our reference number in the client below? Could you advise how to do so? An example would be extremely helpful. Thank you for your help!

const client = new SendleClient({
sendleId: 'yourSendleId',
apiKey: 'yourApiKey',
sandbox: true, // default to false
gotOptions: {},
});

Sarah

Hi,
Thanks for sharing codes in node js to create and cancel order. Could you please share code to view a Sendle label using node js? Thanks for your help.

One issue with the current way of automatically creating idempotency keys ( https://sendle-node.vercel.app/orders#idempotency-key ) is that if the order is created, cancelled, and then re-created with the same customerId & orderId, the Sendle API will reject the new order creation attempt (see the advice here: https://developers.sendle.com/reference/using-idempotency-keys#generating-an-idempotency-key ).

In the create order request, the parameters idempotencyKey, customerId, and orderId are recommended. These are passed as-is to the Sendle API as part of the JSON body, like this:

{
  ...
  "customerId": "#132",
  "orderId": "ABC-625",
  "idempotencyKey": "f5233746-71d4-4b05-bf63-56f4abaed5f6"
}

The orders get created successfully, but it'd be nice if they weren't included, both to make the requests cleaner and to prevent potential issues in future.

If possible, cleaning up the JSON before sending it would mean nicer calls. For example, removing idempotencyKey from the body, sending customerId as metadata.customerId instead (if it doesn't already exist) and doing the same for orderId, etc.

Sendle's recently launched in Canada – and some types need to be updated for this:

• Address.country refers to AU and US only.
• currency is commonly defined as 'AUD' | 'USD', need to add CAD onto that list.
• *_country params that are AU/US need to also include CA.