Sorry, you need to enable JavaScript to visit this website.

You are here

Provisioning 500 error

6 posts / 0 new
Last post

Trevor's picture
by Trevor

Provisioning 500 error
We've suddenly begun receiving the following error when provisioning to https://tapi.telstra.com/v2/messages/provisioning/subscriptions with { "activeDays": 30 } :
{     "status": "500",     "code": "TECH-ERR",     "message": "Technical error : Execution of JSModifyCreateSubscriptionResponse failed with error: Javascript runtime error: \"SyntaxError: Empty JSON string. (ModifyCreateSubscriptionResponse.js:6)\" : An error has occurred while processing your request, please refer to API Docs for summary on the issue" }
We can't find anything in the docs. Can you please advise? To be clear, we've been running the following flow for a few months now without issue: 1. Authenticate 2. Provision number (we never GET, just POST) 3. POST SMS

DeveloperSteve's picture
by DeveloperSteve

Hi it_1

Can you please post your code? (without any api creds) 

Trevor's picture
by Trevor

We get the same thing whether

We get the same thing whether we try via Ruby or Postman and our code has remained unchanged for several months:

TELSTRA_ENDPOINT = 'https://tapi.telstra.com/v2'
PROVISIONING_ENDPOINT = "#{TELSTRA_ENDPOINT}/messages/provisioning/subscriptions"
PROVISION_DAYS = 30

def headers
  {authorization: "Bearer #{token}", accept: :json}
end

def provision_number
  RestClient.post(PROVISIONING_ENDPOINT, {'activeDays': PROVISION_DAYS}.to_json, headers)
end

And the Postman:

DeveloperSteve's picture
by DeveloperSteve

Hi it_1

We did a minor deployment to the provisioning api but only new fields were added to responses (not requests), ive just rerun my test scripts against the current production sdk from github which works as expected with brand new keys. 

Has anything changed in the environment that the script is running on?

also which version of the ruby SDK are you using?

Trevor's picture
by Trevor

Hey Steven,
Hey Steven, We're not using any SDK, as we've been using the T.dev API since it's inception through to the current v2 implementation. Have you seen the image at https://ibb.co/m8JhFe? We get the same error with Postman which makes me wonder if it has anything to do with API key limits? Cheers

Trevor's picture
by Trevor

Hi again Steven,
Hi again Steven,   Looks like it had to do with the API key. I created a new one and all is well. Might want to have a dig at the error messaging to be more indicative.   Thanks for your help.
Log in or register to post comments