Welcome to the new Box Support website. Check out all the details here on what’s changed.

Box Status

CreateSignRequestAsync: Bad Request response when creating a sign request

Follow
New post
spilafis

Hi, I created an app with App access and client and key auth and using the .net sdk I'm able to authenticate, and also upload a file for the app user. But when creating the sign request for that same uploaded file, I get a "Bad request" which doesn't indicate what's the problem.

Box.V2.Exceptions.BoxAPIException: The API returned an error [BadRequest | 0dbd3ddad74643353c1215dc54c43919c.0dbd3ddad74643353c1215dc54c43919c] bad_request - Bad request

I'm going to try to do the request in a simpler way to see if I can get more information from the response, but if anyone has any clues. Please share.

 

0

Comments

2 comments

Date Votes
  • spilafis

    I found that the issue is with the role of the signers. It looks like for an App with "Only App" access I cannot use the "final_copy_reader" role. Since adding a signer with that role, or the "approver" role, causes the exception.

    But there is no mention of this in the documentation.

    0
    Comment actions Permalink
  • Alex Novotny

    Thanks for bubbling this up. We always appreciate folks letting us know when documentation is lacking! 

    Alex, Box Developer Advocate

    1
    Comment actions Permalink

Post is closed for comments.