• State Resolved
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 97 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TI-API: Sandboxed environment for the Backlog Quote and Inventory and Order API

Andrei Errapart
Prodigy 40 points
Part Number: TI-API

Tool/software:

Hi,

I would like to have the access credentials for the sandboxed environment for the Backlog Quote, Inventory API and Order API.

We (Trenz Electronic GmbH) have been using Store API for quite some time and we want to start using the Backlog API.

The production keys are working well, just that I cannot find the sandbox keys anywhere. Simply using sandbox URL of https://transact-pre.ti.com/v2 will get response status of 401 (unauthorized).

According to the instructions on the website api-portal.ti.com/backlog-api-keys one should select "Apps" on the upper right and fetch them from there, but the company account doesn't have any of the "Apps" listed and no means to create a new one.

Perhaps I missed something?

Any help will be appreciated.


Best regards,
Andrei Errapart

  • +1
    Prodigy 40 points

    I think we have more or less resolved this issue by creating our own sandbox. Should TI sandbox access be still available, would be great, but not that important anymore.

    Creating the sandbox for our needs took about an hour with all the usual head-scratching.

    For those who are interested, we used the openapi generator from the latest docker image. The generator for the server side "nodejs-express" is listed as beta, but appears to be in working order almost. In the example of backlog quote API, we changed the file "services/BacklogQuoteAPIService.js" only with some fixed responses. The function "backlogQuotesGET" was simplified as follows:

    async function backlogQuotesGET(request) {

      console.log(`backlogQuotesGET: ${JSON.stringify(request}`);

      return Service.successResponse({

             quote: {

                customerQuoteNumber: '123',

             },
            });

    }

    In the client side, just change the base URL to http://localhost:8080/v2

    No need to bother with authorization.

**Attention** This is a public forum