Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Scroll Health Check: The link has been rewritten to its master page by check 'P16'.

...

Before the Barcode API calls can be sent, the Barcode module must be activated.

Insert excerpt
SQL API Calls
SQL API Calls
nopaneltrue

Write Call

Available Fields

...

  • transaction_type must be po_receive.
  • When setting up the Barcode API in Admin, the Authentication Required box must be true Authentication Required checkbox example. Barcode requires authentication to work.

Available Fields

Parameter

Required

Data Type

Options

Notes

recid YesInteger
Purchase Order RECID, Status must be Open
eqp_catalogYesInteger
Equipment Catalog RECID
priceYesFloat
Price of Equipment
unitsNoInteger
Units of Equipment
,
Note: that this will default to 1 for units catalogs. It is ignored for non-unit catalogs
. Only valid for Has Units Equipment, else ignored. The value must match an entry on the Purchase Order Equipment, as PCR-360 uses this to detect which item is being received if there is more than one entry for the Equipment Catalog on the Purchase Order and their units are different.
quantityYesInteger
Quantity to Receive
locationYesInteger
Valid Active Warehouse RECID to receive Equipment
received_dateNoDate
Received Date
assetsNoArray
Only valid for Asset or Cabling Equipment, else ignored. If provided the number of entries must match the quantity.


Request Example

Call
Code Block
languagesql
http://DOMAIN/api/API_KEY/barcode.OUTPUT
Headers
KeyValue

Content-Type

application/json

PCR-AUTH-TOKEN

example: e036a785-4d7a-40ed-a04a-c8e339327f55

Body
KeyValue
recid 12874
eqp_catalog346
price9.99
quantity4
location694

Results

If the request is successful, then the response will return as:

Toggle cloak

Cloak


Code Block
{
    "message": "Barcode transaction added successfully."
}


Receiving a PO exampleImage Added

Locating Data related to Barcodes

...