FD1 Client Protocol
 
Library Developer Home FD1 Client Protocol Home Concepts Reading Data Writing Data Protocol Defined Servers Connect & Authenticate Proxies & Tunnels
Webhooks & Firehoses Programming Support Logging Minor Facts State Facts Response Format How To Guides eCommerce Sites Custom Point of Sale Customer Access Bulk Downloads Major APIs / Endpoints All Endpoints Products Sales SalesBuilder Session Get Attribute Sale Capture General Purpose Data Capture Devices Barcode Scanners Eftpos IoT Sensors Power Outlets Printing Scales Security Cameras Purchasing / Supply Side Purchase Orders Invoices Invoice Payments Document Capture Rare APIs / Endpoints SSL Certificates API Key Management Diagnositics PosGreen Server to Client Messages Overview Resources / Objects Purchase Order Invoice Payable Invoice Payment Product Supplier Location Sale Lines Sale Delivery Details Sales Price Maps Employees Carriers Payments Product Kits Department 1 Customers

FD1 Sales

Functions relating to complete sales, such as completed sales or sales that have been parked.

These functions are not used to build new sales using individual function calls (create sale, add product, add payment). Interactively building a sale uses the SalesBuilder functions

sales.sale_request

Requests actions to be undertaken on a sale. Actions in this context means things around the whole sale itself, not individual details within the sale

TypeRPC
LinksHandler Logic

Example

POST /fd1/sales/sale_request
{
  "a": "sales.sale_request",
  "v": {
    "sid": 12345,                       // The single Sale# to process against
    "action": "sendorderdispatched"     // What is requested to be done
  }
}

Action KeywordDescription
sendorderdispatched This sale has been packed for shipment, send the customer an email/notification now if required.
This action is mostly used by eCommerce sites to send a message to the customer, often including the courier tracking numbers in that email.

sales.sale_save_new

Takes a complete sale JSON and saves it.