Mark order as delivered

PUT 
/financing/v1/applications/:uuid/order/deliver

Requires applications.order.ship_deliver authority for authenticated user

When the whole order was delivered to the customer, use /financing/v1/applications/{applicationId}/order/deliver resource where {applicationId} is the application ID you received in the response of /financing/v1/applications after its creation.

Financing type	Supported
INSTALLMENT	YES

Application state	Availability
PROCESSING	NO
REJECTED	NO
CANCELED	NO
READY	YES* (see the availability note below)

AVAILABILITY NOTE: Request is valid when Application.stateReason = READY_TO_SHIP. Request is also valid after the transition of Application to the stateReason = READY_DELIVERED or stateReason = READY_PAID (i.e. repeated valid requests return HTTP status code 200 OK unless the Application.stateReason = CANCELLED_RETURNED)

If the request was successfully processed, you receive HTTP status code 200 and object of information about changed order plus basic information about respective application (ID, state, substate) with at least following information in the response:

• Order number
• Order total price (including VAT)
• Order items (array)
  • Order item name
  • Total price (all pieces, including VAT)
  • Order item state
• Order state
• Application basic information
  • ID
  • Application state
  • Application substate

In other cases, you receive one of the following errors:

Status code	Code	Explanation
400	INVALID_REQUEST	Request was not well formatted (malformed request syntax, size too large, etc.)
404	OBJECT_NOT_FOUND	The requested resource could not be found
422	NOT_SUPPORTED	Resource is not supported for given financing type
422	UNPROCESSABLE	The request was well-formed but was unable to be followed due to semantic errors
500	INTERNAL_SERVER_ERROR	Unexpected condition was encountered and no more specific message is suitable

Request

Responses

200

OK

201

Created

401

Unauthorized

403

Forbidden

404

Not Found