FLAPI: About Customers

Stage	API call (some parameters omitted)
1. create customer category	POST /categories
2. create customer	POST /customers
(add addresses)	POST /customers/<customer.code>/addresses
(view contacts/users) (view specific contacts) (create contacts/users) (update contacts/users)	GET /customers/<customer.code>/contacts GET /customers/<customer.code>/contacts/<contact.id> POST /customers/<customer.code>/contacts PUT /customers/<customer.code>/contacts/<contact.id>
create order for customer	POST /orders customer=<customer.code>
create job for customer	POST /jobs customer=<customer.code>
view invoices	GET /invoices Then filter your results by customer.
(retire customer)	Customer records become dormant, rather than retired, so that historical records remain. If you have reason to employ checks before trading with a customer, then record it in your own data.

	FLAPI: Customers Quick Reference Available to: FLAPI, M-FLAPI Paths for Customers GET /customers/<customer.code>/ POST /customers/<customer.code>/ name=<name> PUT /customers/<customer.cod...
	FLAPI: Customer Main Details Request 'customer' by code GET Syntax /customers/<customer.code> Retrieves a single customer item. You must have permission to view this customer. HTTP request GET http://dev.f...
	FLAPI: Customer Addresses Each customer has a main invoicing address. They may have additional delivery addresses, accessed using these .../addresses requests. Request 'addresses' by customer GET Syntax /customers/...

Jump to contents page of