Zenki
Zenki Home Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Notification orders

Notify service type orders delivered

The next endpoint allows you to confirm the delivery of the service related to an order. The notification process for service type orders is very simple, you must refer to the order with the identifier ‘orderId’.

This service will respond with a summary of the status of the order and its services.

💡 Remember that you must use the previously generated Bearer Token Access Token

ENDPOINT

POST  https://api.zenki.fi/v1/api/escrow/orders/services/fulfillments 
  • Headers
    • Accept: application/json
    • Authorization: Bearer Tokens
  • Authorization [Bearer Token]
    • Token: (token)
  • Body [raw / json]
    • orderId : (string | required)
  • Response attributes
    • orderId: (string)
    • merchantOrderId: (string)
    • orderStatus: (string)
    • orderPlacedAt: (timestamp)
    • approvedAt: (timestamp)
    • orderApprovals: (Array)
      • serviceId: (string)
      • deliveryServiceStatus: (string)
      • fulfillmentServiceExpiresAt: (timestamp)
      • fulfillmentAt: (timestamp)
      • serviceDeliveryBy: (string)

cURL

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
curl --request POST \
     --url https://api.zenki.fi/v1/api/escrow/orders/services/fulfillments \
     --header 'Accept: application/json' \
     --header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIwenJMTnEwbzBab1R4NTlaeWVPaTI1RGxZLWl6cV91SVFSLThWS0RaWjlFIn0.eyJleHAiOjE2NjE3ODk3NTQsImlhdCI6MTY2MTc4Nzk1NCwianRpIjoiYTczZDUwN2MtZmJkMS00MjE0LThjMjUtMDBlN2ZiYTk5Nzc0IiwiaXNzIjoiaHR0cHM6Ly9kZXYtYXV0aC56ZW5raS5maS9hdXRoL3JlYWxtcy9wYnciLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZWQ3ZWQ1ZmMtZjBmNy00OWEwLWEwNWYtNWNiZTFkMjZkYTlkIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoiemVua2ktcGF5Iiwic2Vzc2lvbl9zdGF0ZSI6IjhmNmJkYzYzLWFiYTctNGMxNy1hZTcyLWEwNDcyZjA1ZmQ4NyIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiIl0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJhcGkiLCJhcGlfemVua2lwYXkiLCJkZWZhdWx0LXJvbGVzLW1ldGFiYW4iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJzaWQiOiI4ZjZiZGM2My1hYmE3LTRjMTctYWU3Mi1hMDQ3MmYwNWZkODciLCJlbWFpbF92ZXJpZmllZCI6dHJ1ZSwibmFtZSI6IlJlYWwgTWFkcmlkIEZDIFJlYWwgTWFkcmlkIEZDIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiOGRjNDY5YTFkZTRiNDI3NTljMDdjNGYyYmQ2YzAzZjQiLCJnaXZlbl9uYW1lIjoiUmVhbCBNYWRyaWQgRkMiLCJsb2NhbGUiOiJlbiIsImZhbWlseV9uYW1lIjoiUmVhbCBNYWRyaWQgRkMiLCJlbWFpbCI6IjhkYzQ2OWExZGU0YjQyNzU5YzA3YzRmMmJkNmMwM2Y0In0.CnshdJfvJp6Memb7BQ8yJo0YuzvXPZ8egs52nzPqWKTLHYPqxPSm1QeWXZh8u5EpdWiVsDW4csIBtKEkCUlwI0pO9U9nFtV-_vaAk0NIH0ArOOhRhiDGggkkIWbudXUaSpnG5jyLNLg_nvbPcMWOp5jSbDlc6p3KY67h_LWzT8qLGnSoTdX05NKSYnjUe9woqm5aGXBcKbCPQsxPOLlVPFeGCjDW-n1oKEQsh8HIKoMvH07J4cO_wAukz9GvoCcz1GG8j8T8kZy-LGxRwqLervTbor4RhYeAZODwiVLmj-mGILppJqgZLBhiJebxDeoExqukQ1mpfBGaugCZM5Eai' \
     --header 'Content-Type: application/json' \
     --data '

{

     "orderId": "f325da2b8e3f476caa07e039406e72f0"

}
'

Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
{

  "orderId": "f325da2b8e3f476caa07e039406e72f0",
  "merchantOrderId": "l94jakpc3jpvdhzm",
  "orderStatus": "SETTLED",
  "orderPlacedAt": "2022-10-11T18:26:14.784+00:00",
  "approvedAt": "2022-10-11T23:54:34.220+00:00",
  "orderApprovals": [

    {

      "serviceId": "4bc1abeff4154050b327504f56263436",
      "deliveryServiceStatus": "COMPLETED",
      "fulfillmentServiceExpiresAt": "2022-10-11T19:32:38.761+00:00",
      "fulfillmentAt": "2022-10-11T23:34:01.580+00:00",
      "serviceDeliveryBy": "API"
    }
  ]

}

Errors

Code Description
400 The request is not in the requested format.
401 The request failed because it lacks valid authentication credentials for the requested resource.
404 An order number for the trade was not found.