Infusion Knowledge Base

    Sorry, we didn't find any relevant articles for you.

    Send us your queries using the form below and we will get back to you with a solution.

    FAQs - Public API

    Here are some common questions and answers about our Public API.

    1. Do the licenseuuid and sessionuuid tokens expire, or are they unlimited?

    Tokens expire after 60 days of non-use.


    2. Is modifiedTimestamp set the same as createdTimestamp when a record is created (rather than null)?

    They are both set when the record is created and the versionNumber is set to 0. Subsequent changes update the modifiedTimestamp and the versionNumber.


    3. Are there any API restrictions such as calls per minute/download or size/IP whitelisting? 

    The Rate Limiting is 10 requests per second. We don’t place limits on download size and we don’t whitelist IP addresses.


    4. Does every entity in the data model have a UUID (as in, all records can be uniquely identified)?

    Every entity has a UUID.


    5. Should I use Search or Synchronisation?

    Both the Search endpoints and Data Synchronisation can provide the same information. When using Search you make a request each time you need information which can put load on the servers, however it does have the advantage of built-in search criteria and text-matching. Data Synchronisation on the other hand, allows you to keep an up-to-date local copy of the data.

    We strongly recommend using Data Synchronisation where possible, especially if you need to constantly request data, for example when providing a product search for an e-commerce website.


    6. What happens if I generate a new session ID?

    If a new session ID is generated, it renders the previous session ID invalid and will cease to work. You will enter in the new session ID to reestablish the connections.


    7. What validation rules exist when text fields are being loaded?

    When text fields are being loaded through the API, such as an address field, the following validation occurs on the text field:

    • May not contain double spaces. 
    • May not contain tab characters. 
    • May not contain new line characters. 
    • May not contain form feed characters. 
    • May not contain carriage return characters. 
    • May not contain control characters. 
    • May not contain Unicode space characters. 
    • May not start with a space. 
    • May not end with a space.


    8. What triggers a data sync requirement?

    When an addition of a new entry, update to, or deletion of an existing entry in any of the following data types:

    • Products
    • Customers
    • Customer Invoices
    • Customer Contract Rates
    • Product Promotional Prices
    • Discount Matrix Entries

    A new timestamp is added to the entry, which also marks the item to be resynchronised on the next sync. This sync needs to be performed before the item can be used in the API.


    There are currently six Data Synchronisation endpoints available: Products, Customers, Customer Invoices, Customer Contract Rates, Product Promotional Prices and Discount Matrix Entries. When there is an addition, change or deletion for any of these, they will be provided in the next request to the Data Synchronisation. For deletions, the data included will resemble what was deleted but it can be distinguished from insertions or changes by checking the deletedTimestamp which will have the timestamp of the deletion.

    Was this article helpful?

    Still can't find what you are looking for?

    Our award-winning customer care team is here for you.

    Contact Support

    Powered by