The JOOR Order API allows clients to extract orders generated on the JOOR platform (iPad application and web site). When requests for orders are made, these requests are logged and orders are marked as having been exported. This logging, combined with the required request field for syncing, allows clients to build a system that is resistant to duplication.

πŸ“˜

Paginated Response

Results are paged in counts of 50 by default. The response will include the total number of results and instruction for the next page count starting position.

πŸ‘

Endpoints

GET

Params

  • Accept: application/xml OR application/json
  • Authorization: OAuth2 [Base64 encoded token]

🚧

JOOR Internal Field Validation

Please note that it is possible to ask your integration manager to add a JOOR internal field validation to your GET Order requests.

This will prevent any orders not including the required fields to be included in the response of the API call when using the parameter sync = 1.

Additionally, the order will be marked as failed in JOOR and users will be able to see the issue by hovering over the failed export status.

The list of fields on which validation can be applied is the following:

  • 'payment_method_code'
  • 'shipping_method_code'
  • 'shipping_code'
  • 'customer_code'
  • 'customer_group_name'
  • 'customer_group_code'
  • 'order_delivery_code'
  • 'order_season_code'
  • 'billing_code'
  • 'shipping_code'
  • 'order_type_code'
  • 'company_name'
  • 'company_code'
  • 'order_event'
  • 'order_event_code'
  • 'warehouse_name'
  • 'warehouse_code'
  • 'door_codes'
  • 'door_names'
  • 'division_code'
  • 'sales_representative_code'
  • 'sales_representative'
  • 'tax_id_label'