Dcove
  1. transactional
Dcove
  • master
    • Stores**
      POST
    • Article Batches
      POST
    • Article Eans
      POST
    • Article Master**
      POST
    • Article Supplier Mapping**
      POST
    • DC - Store Mapping**
      POST
    • Manufacturer
      POST
    • Purchase Returns
      POST
    • Wastages
      POST
    • Supplier Master**
      POST
    • Supplier Contacts
      POST
    • Production Pipeline Execution
      POST
    • Kit Master
      POST
    • Bulk Repack Master
      POST
    • Article Uom Master
      POST
    • Supplier WalkIns
      POST
    • Article Pricing Master
      POST
    • Article Store Limits
      POST
    • Current Stock**
      POST
    • Stores As Suppliers
      POST
    • Stock Location**
      POST
    • Customer Master
      POST
    • Company Group
      POST
    • Hierarchy Headers**
      POST
    • Hierarchy Details**
      POST
    • Article Hierarchy**
      POST
    • Article Attributes
      POST
    • ArticleGateKeeperMargin
      POST
  • transactional
    • Stock Ledger**
      POST
    • Bill Header**
      POST
    • Bill Detail**
      POST
    • Invoices Header**
      POST
    • Invoices Detail**
      POST
    • Supplier Invoice Acknowledgement
      POST
    • Purchase Order Header**
      POST
    • Purchase Order Detail
      POST
    • Transfer In Header**
      POST
    • Transfer In Detail**
      POST
    • Transfer Out Header**
      POST
    • Transfer Out Detail**
      POST
    • Transfer Advice Header
      POST
    • Transfer Advice Detail
      POST
  1. transactional

Purchase Order Header**

POST
/tx/po_header/
transactional
Tracks all purchase orders raised in the system.

Request

Query Params
full_sync
boolean 
optional
Whether the data should be synced in an incremental manner or completely. Defaults to false.
Header Params
X-SYNC-TOKEN
string 
required

<sync_token>

Accept-Encoding
string 
required
gzip (mandatory)
Body Params application/json
array of:
store_id
string 
required
supplier_id
string 
required
Supplier that is servicing the PO
po_no
string 
required
Store local PO number - the po is available at the store/dc where GRN is done and this is when the local po number is generated.
This may be different from your central PO number. If not present the central PO number can be used here.
po_display_no
string 
required
Store local display number - this can be the same as po_no if your backend does not use rolling sequences or has workflows for the same.
The display number is used in combination with the year to match with the purchase orders raised in The Eye.
hq_po_ref
string 
required
"Central PO number. This number is unique and when combined with the HQ id, would be unique to your business to lookup a purchase order.
You would see this PO reference for tracking and purchase analysis"
purchase_date
string <date>
required
Date the PO was raised.
expiry_date
string <date>
required
Date the PO gets expired.
created_at
string <date-time>
required
Example
[
  {
    "store_id": "string",
    "supplier_id": "string",
    "po_no": "string",
    "po_display_no": "string",
    "hq_po_ref": "string",
    "purchase_date": "2019-08-24",
    "expiry_date": "2019-08-24",
    "created_at": "2019-08-24T14:15:22Z"
  }
]

Request samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://test.your-api-server.com/tx/po_header/' \
--header 'X-SYNC-TOKEN;' \
--header 'Accept-Encoding;' \
--header 'Content-Type: application/json' \
--data-raw '[
    {
        "store_id": "string",
        "supplier_id": "string",
        "po_no": "string",
        "po_display_no": "string",
        "hq_po_ref": "string",
        "purchase_date": "2019-08-24",
        "expiry_date": "2019-08-24",
        "created_at": "2019-08-24T14:15:22Z"
    }
]'

Responses

🟢200OK
application/json
Successful Sync
Body
status
string 
optional
message
string 
optional
Example
{
  "status": "string",
  "message": "string"
}
🟠403Forbidden
🟠405405
Modified at 2025-02-10 12:39:04
Previous
Supplier Invoice Acknowledgement
Next
Purchase Order Detail
Built with