• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 1045 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

Original question:

TI-API: Error in generating tokens

Failing to generate API token via JSON command in Insomnia (FORM works)

Rainer Roese
Prodigy 10 points
Other Parts Discussed in Thread: TI-API

Hello,

I am attempting to generate an API token via JSON script in Insomnia. 

FORM access worked fluently with below response, so I assume my ID and SECRET are correct:

When using JSON, I get a 401 UNAUTHORIZED response:

JSON script has been taken 1:1 from:

TI store API suite - Authentication | TI API Portal

Thanks for help resolving this. 

Rainer

  • 0
    TI__Guru 71526 points

    Hello Rainer,

    Thank you for your post - for future new posts, please enter Part Number = TI-API to ensure your inquiry is automatically routed to the experts.

    Thank you,

    ~Leonard 

  • 0 in reply to LeonardEllis
    Prodigy 10 points

    Thank you, Leonard, fair point. Can I edit my post to add the Part Number? Thanks. 

  • 0 in reply to Rainer Roese
    TI__Intellectual 1276 points

    Rainer:

    I have send you private message to get more info before I can help you further. 

    ~Samip

  • 0 in reply to Samip Banker
    Prodigy 10 points

    Resolved!
    Thank you for your support, Samip.

    I understood that Insomnia doesn't accept CURL commands and the example on the API Portal is CURL, not JSON. 
    The resolution was to verify that CURL is installed on my Windows machine (check) and CMD prompt is accepting CURL commands (check).

    After these steps, entering the curl command in this form

    • curl --request POST --url "">transact.ti.com/.../accesstoken" --header "Content-Type: application/x-www-form-urlencoded" --data grant_type=client_credentials --data client_id=[ID GOES HERE]--data client_secret=[SECRET GOES HERE] 

    has worked and produced the desired answer with the API token

    • {
      "access_token": "TOKEN OUTPUT HERE",
      "token_type": "bearer",
      "expires_in": 3599,
      "scope": "",
      "application_name": "APP NAME OUTPUT HERE",
      "developer.email": "",
      "issued_at": "TIMESTAMP OUTPUT HERE",
      "client_id": "CLIENT ID OUTPUT HERE"
      }

    Again, thank you for this resolution.
    BR,
    Rainer

**Attention** This is a public forum