POST /pois/orders/accessories/{poiUid}

Creates an order for add-on accessories & consumables (e.g. stationery) which are typically used with a POI

Servers

Path parameters

Name Type Required Description
poiUid String Yes

The assigned ID corresponding for the POI.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
paymentDetails Object No

Details of how the order will be paid, and the further re-occuring billing for services.

paymentDetails.paymentType String Yes

Type of payment that can be made.

Default value: "CREDIT"

notes String No

Notes for the Order

orderReference String Yes

Client reference for the Order

requestedDate String No

The requested date for this order.

poRef String No

Purchase Order Reference

accessory Object Yes

Accessory type and bundle

accessory.accessoryType String Yes

Type of accessory

Valid values:

  • "OTHER"
  • "CONSUMABLES"

Default value: "CONSUMABLES"

customerEntityUid String Yes

Verifone allocated ID for the customer this order is for (packages and bundles are associated with this entity).

additionalOrderData[] Array No

Input data which maybe required for the country/business unit to to complete the order. For example some countries require a VAT ID, or different legal forms of business, this will be defined by Verifone if needed for your integration

additionalOrderData[].variableName String No

Variable name (this would be provided by Verifone)

additionalOrderData[].variableValue String No

Value of the variable

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.