This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI-API: Backlog API - Testing and implementation guide for Order Push API

Part Number: TI-API

Tool/software:

Hi,

We are currently in development process to integrate our in-house applications with Order Push API. I was wondering if there is a convenient way to test this before production environment. When I read the documentation in API developer portal I saw that Order Push API's test endpoint is a GET method which is sent to a some boilerplate URL that I can not change. I do not feel confident as I go through with the development process because without proper testing whole development becomes kind of ad hoc. 

In case there is not a way to test this I have some questions:

1- What is the timespan for Order Push API to timeout?

2- In the payload schema `orders` is a list object which makes me expect information about multiple orders in a single Order Push. Is this a case in production environment?

3- In a single `order`, `schedules` and `confirmations` are also a list in hierarchical order inside of a line item. Does this API sends the latest info only or cumulative information(e.g. multiple schedule objects in the `schedules` field for different updates) for the order? What is the meaning of having multiple schedules for an order and having multiple confirmations for a schedule?

I did not want to make assumptions about these questions so I thought it would be better to ask for help.

Thanks in advance for your help,

Best regards,

Furkan

**Attention** This is a public forum