Support for

FLAPI: About Customers

Alistair Wilson
by Alistair Wilson 7 years ago
 
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.
 

See also

FLAPI: Customers

FLAPI: Customer Main Details

FLAPI: Customer Addresses

Jump to contents page of

Flyerlink API Guide

 
 
 

All content is (c) Nettl Systems Limited, 2024 and may not be used, copied or distributed without permission.