Skip to main content

Order Push JSON Versions Breakdown

This is a list of all previous JSON versions and the fields and features that were included in them.

Yordan Mitrev avatar
Written by Yordan Mitrev
Updated over 2 months ago

Version

Summary changes

V1.17 - added Release-58

New fields added:

min_order_value

vat_on

project_url

customer_discount:

hidden

displayed

Part fields added:

part_url

density

post_processing_services (changed):

name

cost

cycle_time

programming_time

setup_time

V1.16 - added Release-57

New fields added:

custom_ticket_id

V1.15 - added Release-56

Fix for issues with versions 1.14 & 1.13

V1.14 - added Release 56

Add a new field:

  • Customer

V1.13 - added Release 56

Moved signature to Header

V1.12 - added Release 54

Added a new field:

  • Voucher

V1.11 - added Release 54

Update: Works not only for orders but for tickets too.

  • ticket_status

  • customer__cc_email

  • assignees: Array of users and departments assigned to a ticket

  • vat_%

  • discount_amount

  • discount_percentage

    • Part fields:

      • custom_part_id

      • part_price_with_discount

      • builds: information about part items builds assignment

    • Manual service field

      • price_with_discount

Note: the Order Push JSON v1.11 will work not only for orders but for tickets too.
​​Please note that the email address used will receive the full Order JSON in the event that the JSON cannot reach the specified webhook (e.g. if the webhook system loses access to the internet or electricity) after the attempt has been made a number of times.

V 1.10 - added Release 51

New array added:

  • part_cost_breakdown

    • Items fields:

      • service_code

      • service_cost

V 1.9 - added Release 49

New fields added.

New fields common:

  • priority

  • region

New fields items:

  • production_notes

  • shipping_deadline

  • delivery_date

  • part_price_with_discount (was removed)
    ​
    ​Root cause: This JSON field was implemented not taking into consideration discount logic. it is possible to have % discount and fixed amount discount and when customer use the fixed amount discount it will not divided it correctly between parts, AMFG discount is always applied at project level.)
    ​
    ​

  • waybill_number

  • shipping_label_number

V 1.8 - added Release 48

New fields added:

Dates converted to ISO format:
​
​

New fields added:

  • quote_id

  • quote_expiry_date

  • quote_version

  • quote_currency

  • currency_exchange_rate

  • order_source

  • ticket_name

  • ticket_custom_id

  • quote_price_incl_vat

  • quote_price_excl_vat

  • quote_delivery_price_incl_vat

  • quote_delivery_price_excl_vat

  • creation_flow

New fields added (parts):

  • unit_price

  • quote_unit_price

  • quote_price_incl_vat

  • quote_price_excl_vat

  • quote_currency

V1.7

To enable this version use:

{ "version": 1.7 }

New fields added:

  • external_production_center_name

  • internal_production_center_name

  • profit_center_id

V1.6

To enable this version use:

{ "version": 1.6 }

New fields added:

  • uploaded_file_download_link

  • uploaded_file_full_path

  • quoted_file_download_link

  • quoted_file_full_path

V1.5

To enable this version use:

{ "version": 1.5 }

New array added:

  • manual_services

    • Items fields:

      • description

      • quantity

      • price_per_item

      • price_per_item_incl_vat

      • total_price

      • total_price_incl_vat

V1.4

This schema working by default

New fields added:

  • company_number

  • address_second_line

  • industry

Fields removed:

  • vat_number

  • service_id

  • service_name

  • build_status

  • material_group

  • colour_group

Schema changes:

  • Moved delivery fields to order part

  • Moved the address to the order level

V1.3.1

New field added:

  • po_number

V1.3

New field added:

  • payment_id

V1.2

Schema: message info was added, now it’s a full json schema.

1 schema field data type change:

  • created_at: datetime -> string

4 JSON example data type changes:

  • delivery_vat: string -> number

  • price_excl_vat: string -> number

  • price_incl_vat: string -> number

  • vat_number: number -> string

V1.1

Three new fields were added:

  • order_price_excl_vat

  • order_price_incl_vat

  • shrink_wrap_volume

Misspelling corrected in the documentation:

  • price_excl_vat

Did this answer your question?