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

This thread has been locked.

Invalid API call as no apiproduct match found on API call.

Jamie Lake
Prodigy 20 points


Hello,

I have written an application for users to request part information and place orders using your api. All calls have been successful so far to the routes while testing on my local server, however publishing the application to a test server for users results in all requests returning an "Invalid API call as no apiproduct match found". I am using the same api ulrs and authentication Client ID and Secret ID and appear to get back a valid authetication token.

Thank you. 

  • 0
    TI__Genius 9365 points

    In the authorization for the API access Keys - is your test server using different API URLs than what you have published in  myTI company account setup?  That would be the first avenue to check the API calls use the API access URL that has been setup in that app as part of your myTI Account if your test server API URL is different than what is listed there I would presume no match on the API call was found would be presented

  • 0 in reply to Tammy Rawdon
    Prodigy 20 points

    As I recall on the Company setup page there are only fields for Account Name, Description and Company website. I don't see any other URL's published. My application works fine on my local machine, and fine on published server #1 (DEV), but not on published server #2 (UAT). 

  • 0 in reply to Jamie Lake
    TI__Genius 9365 points

    I am sorry for delay, I received a new laptop was out of commission a bit. - on our side we are not seeing the issue you are experiencing with your server #2 all looks valid on our side, so i would direct you to this area it would most likely be the authentication that is causing you an issue - TI store API suite - Authentication | TI API Portal - go to this link and verify your authentication and the other few points to see if this helps get you working.

    • using the client credentials flow.
    • The "Content-Type" must be "application/x-www-form-urlencoded".

**Attention** This is a public forum