After setting up a business account and having billing set to Telstra Account:
Retrieving a token succeeds however the scope returned doesn't match the scope requested (as per documentation):
% curl -X POST -H 'Content-Type: application/x-www-form-urlencoded' \ -d "grant_type=client_credentials&client_id=$CLIENT_KEY&client_secret=$CLIENT_SECRET&scope=NSMS" \ 'https://tapi.telstra.com/v2/oauth/token' {"access_token":"XXXXXXX","token_type":"Bearer","expires_in":"3599","scope":""}
Making a call to attempt to provision a service results in the apiproduct match found error:
% curl -X POST https://tapi.telstra.com/v2/messages/provisioning/subscriptions -H "authorization: Bearer $ACCESS_TOKEN" -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{ "activeDays":30, "notifyURL":"http://example.com/" }' { "status":"401", "code":"TECH-ERR", "message":"Technical error : Invalid API call as no apiproduct match found : An error has occurred while processing your request, please refer to API Docs for summary on the issue" }
The documentation says:
If the problem persists, write a post in the Messaging API forum
So here we are, can you please help? We've been trying to provision an SMS service for over a month now, this doesn't seem like a difficult thing to provision (plenty of other providers are 5 minute setups).
Hi Stuart,
This is Vinodh from TelstraDev (dev.telstra.com) support team. Thanks for reaching us over forum channel as per documentation.
Upon checking, it was found that the keys were created on 22-Aug during which the billing method was credit card. Unfortunately, Messaging API is not supported over credit card billing method and because of which the keys does not include access to Messaging API. Though we have specified this in other parts of the website, we understand this is causing unnecessary errrors and confusion. We are aware of this confusion and we are in the process of updating our website to ensure users are aware of this restriction when creating company using credit card.
Could you please create keys again and use the newly created keys for provisioning? You may delete the old keys once you are successful with new keys.
Also, you can provide activeDays as 1825 (30 days is only for free trial) to ensure your subscription does not expire for next 5 years.
Regards,
Vinodh
There is a new troubleshooting guide available to troubleshoot these type of issues on your own. Please visit - https://dev.telstra.com/content/messaging-api-troubleshooting-guide for troubleshooting steps.