0

Trying to Create New Client In Sandbox via rest call

Mike Willis

December 08, 2011 15:47

Answered

Follow

Originally from ticket #3555.

Is there anyway to get more information about why my call to create a new client is failing I get back a 401 error and I am not what I am missing in my request. I have tried numerous variations with no success and the only response I get back is 401. Would I be able to send you a sample request so you could take a look? Or do you have some logging available that you could share with me?

A possible long term solution might be to have an api control panel on your site where I might be able to set the logging level or just view the log for when there is an exception. Always getting back the same error obviously makes debugging very difficult.

thanks

• Facebook
• Twitter
• LinkedIn

10 comments

• 0
  
  Mike Willis December 08, 2011 16:00

  I am developing in .Net.

• 0
  
  J Cobb December 09, 2011 02:29

  I don't use .NET, but if you want to post or email me a sample of your POST I can probably troubleshoot it for you.

• 0
  
  Mike Willis December 10, 2011 16:05

  Here is the sample request that I am sending, for the signiature I am hashing "POST api.sandbox.ticketevolution.com/clients?"

   

  ALL_HTTP: HTTP_CONNECTION:Keep-Alive HTTP_CONTENT_LENGTH:39 HTTP_CONTENT_TYPE:application/vnd.ticketevolution.api+json; version=8; charset=utf-8 HTTP_ACCEPT:application/vnd.ticketevolution.api+json; version=8 HTTP_EXPECT:100-continue HTTP_HOST:kyrian-pc HTTP_X_SIGNATURE:0nSAre8GxwKD1QIvHDoq8MfGCvvLsNcRlAuxp5E3TOA= HTTP_X_TOKEN:07724fe3dbe1d43e764bf6fcd726056d
  
  ALL_RAW: Connection: Keep-Alive Content-Length: 39 Content-Type: application/vnd.ticketevolution.api+json; version=8; charset=utf-8 Accept: application/vnd.ticketevolution.api+json; version=8 Expect: 100-continue Host: kyrian-pc X-Signature: 0nSAre8GxwKD1QIvHDoq8MfGCvvLsNcRlAuxp5E3TOA= X-Token: 07724fe3dbe1d43e764bf6fcd726056d

   

  my token is 

  and my secret is 

   

  The code I am using has no problem making get requests, it is just the posts that I am having trouble with.

  I appreciate your help, let me know if there is any more information I can provide.

• 0
  
  J Cobb December 10, 2011 16:38

  What are you trying to do with this call? It looks like are trying to list clients, which would be a GET request. If you are trying to create a client you seem to be missing the JSON containing the client data.

• 0
  
  Mike Willis December 11, 2011 03:15

  I am trying to create a client, this is the posted data i am sending (this is directly from the api documentation):

  d: {"clients":[{"name":"Elissa Weimann"}]}

   

  1 item I am not clear on, is the posted data supposed to be part of the signature? In the documentation it mentioned including the body of the request but I was not clear is that was referring to the post or not. In either case I've tried the request both ways but with the same 401 response.

• 0
  
  J Cobb December 11, 2011 23:19

  A 401 error typically usually means you’ve computed the X-Signature incorrectly. But first you should check that you are using the correct API Token & Secret at http://exchange.ticketevolution.com/brokerage/offices. 

  If what you are using is correct then it is most likely that you are computing the X-Signature incorrectly. Using your example below, what you should be using to compute your X-Signature would be 

  POST api.sandbox.ticketevolution.com/clients?{"clients":[{"name":"Elissa Weimann"}]}

  As the documentation states, “In the case of  POST  requests when a request body is present, the request body should be used in the source string in lieu of the query string…” In this case the request body would be the JSON {"clients":[{"name":"Elissa Weimann"}]} 

• 0
  
  Mike Willis December 13, 2011 03:58

  i was able to get my post to work. I was using d={"clients":[{"name":"Elissa Weimann"}]}  in the signature. I thought I had tried it with dropping the "d=" but I must have had something else that was off in those tests.

   

  While I was able to make a post to production I am still not able to make any posts or gets to the sandbox. I am using the same token and secret for both production and the sandbox and I am pointing to api.sandbox.ticketevolution.com.

  I have verified that I am using: POST api.sandbox.ticketevolution.com/clients?{"clients":[{"name":"Elissa Weimann"}]} as the text in the hash.

  The signature for this call is: GW9RGWsuSIHbcbBESDp3YOI+4QWeHaXrmbvmJSSf

  Do I need to use a separate token for the sandbox? Is there any other reason you can think of that a call to production would fail when pointing to the sandbox?

   

  thanks again for your help

• 0
  
  J Cobb December 13, 2011 19:07

  I suspect that the 'd=' portion you were trying is remnant from copy/pasting from the API docs where it currently shows how to POST using cURL. With cURL, the d flag is for the data to be posted.

  It appears that currently your API credentials do not exist in the sandbox. I have asked the engineers to see if they can activate the sake key/secret you have for production in the sandbox.

• 0
  
  Mike Willis December 18, 2011 20:18

  I am still not able to make calls to the sandbox. Do you know if my API credentials have been added to the sandbox?

• 0
  
  J Cobb December 20, 2011 05:04

  I just emailed new Sandbox credentials to  justgreattix@gmail.com