Uploading RightSignature documents with private token

  • 1
  • Question
  • Updated 8 months ago
Is there any way to access the old API using private token requests? 

I work for a company that makes hotel software. We wrote an integration with RightSignature about a year ago that was humming along fine, but I was trying today (with a new permanent account- last year we just had a 90-day temporary sandbox) to verify everything was still working before demoing the integration for a new client, and it appears the whole API is different.  Whenever I try to use the old url - https:/rightsignature.com/api/document.xml - it's expecting an OAuth token, instead of private api token, even if I've included the api-token header.

Is there decent documentation for the new API?  It appears that now we have to go to new URL, and do the uploads in three pieces - request an upload, put the document to the url returned by the upload request, and then confirm the upload as done.  There's a number of changes to make here - the information about the document appears different, the requests use json instead of xml, etc.  I don't mind making the changes, but is there anyway to access the old one in the meantime? 
Photo of Caryn Babstock

Caryn Babstock

  • 5 Posts
  • 0 Reply Likes

Posted 8 months ago

  • 1
Photo of Kelly Leeman

Kelly Leeman, Employee, Software Engineer

  • 63 Posts
  • 5 Reply Likes
We have 2 different products, new Rightsignature and original.  The documentation for the original api is available at https://rightsignature.com/apidocs/api_documentation_default.  Documentation for the new applications api is available https://api.rightsignature.com/documentation/authentication.  They are 2 different products, not two api's for the same product. Secure token authentication is an option in both.
Photo of Caryn Babstock

Caryn Babstock

  • 5 Posts
  • 0 Reply Likes
Is there anyway to get an api-token for the original api if your account is on the new system?  When I try to log into the old system (Following the link you provided), it only shows the expired account I had a year ago,  and I'm unable to generate a token for that account.  Or did we purchase the account in the wrong place?
Photo of Kelly Leeman

Kelly Leeman, Employee, Software Engineer

  • 63 Posts
  • 5 Reply Likes
It sounds like you may have purchased an account for the new product and discontinued your account for our original product.  In both products you can generate tokens under account>api, thought the buttons are in different locations.
Photo of Caryn Babstock

Caryn Babstock

  • 5 Posts
  • 0 Reply Likes
The initial issue was that the "private api token" generated under the new account would not work with the original product - I kept getting an  "Invalid OAUTH Request" response when I tried sending a document with that token to the rightsignature.com/documents.xml url.  Is there anyway, with a new account, to get a token that will work with the original product?  It's not that we don't want to use the new system (the Sharefile integration, in particular, is a big plus for us), but rewriting our interface wasn't on the schedule for this week. :-)
Photo of Kelly Leeman

Kelly Leeman, Employee, Software Engineer

  • 63 Posts
  • 5 Reply Likes
No, they are 2 separate products.  If you have an account in the new system you need to use that api and token for that system.  If you want to use the original application and api then you would need reopen that account and close the new one.