• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 553 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Push notification API for Backlog order and Financial documents

Jørgen Haugmo
Prodigy 10 points
Part Number: TI-API

Tool/software:

Hi,

We are in early stages of implementing Backlog API and want to use Push Notifications.

To sort the incoming messages we need to have other information than is available in json messages from TI API.

In Push API settings there are 3 rows of API request parameters. I can't find information about these fields in the API documentation.

Could we input in 1 line information and will this be sent in the API Push Notification?

example: associationNo=1234567890

We will setup this in all Push API settings and all messages can then be sorted correctly in our receiving system.

  • 0
    TI__Genius 9365 points

    I will see if I can find some documentation on these parameters inbound  on  PUSH.

  • 0 in reply to Tammy Rawdon
    Prodigy 10 points

    Thank you for looking into this! I look forward to your response.

  • 0 in reply to Jørgen Haugmo
    TI__Genius 9365 points

    re-asking for some parameters explanations. please  stay with us.

  • 0 in reply to Tammy Rawdon
    TI__Genius 9365 points

    I am not sure how much this will assist you but this is what was shared to me thus far - We primarily only utilize the headers fields - in the PUSH API

    In Backlog Push, our expectations is that you as our customer will always pass all headers like this: header_name=header_value
    header1-name=header1-value => it is set in the code like   <header1-name> : <header1-value>,
    header2-name=header2-value     => it is set in the code like l<header2-name> : <header2-value>,
    header3-name=header3-value     => it is set in the code like  <header3-name> : <header3-value>

    I do not think we utilize these anywhere else in any of our code or lower-level processing just at the header level.

    Hopefully this is helpful, sorry for such long delay.

  • 0 in reply to Tammy Rawdon
    Prodigy 10 points

    Thank you for the reply.
    Just to clarify my understanding:

    Will we be able to input any data in these parameter fields and they will be present in every PUSH message from TI? They will be a value in the header?

    If I setup our Order management push API like the example picture below. How will this be presented in the JSON message for PUSH API?

    Will the attribute have the same name in all PUSH messages like Financial documentation?

    Will this be the result for the header of orders in JSON from TI?

      "orders": [
        {
          "messages": [],
          "orderNumber": "string",
          "orderDate": "string",
          "customerPurchaseOrderNumber": "string",
          "orderStatus": "string",
          "endCustomerCompanyName": "string",
          "header1-name" : "associationNo=1234567890",

**Attention** This is a public forum