error 400 when trying to Get Embedded Sign URL

[Jalapina]

Hi I'm trying to Embedded the Dropbox sign api into my react project.

im using javascript 

i want the user to sign in with their account and see their documents that need to be signed.
when they click in a document it sends them to a page where the documents should be embedded 

i have the documents id and with that i can get the signature id, now when i try to make this api call it gives me an error

"error_msg": "Signature request is not authorized for embedded signing.",

i tried using the playground and still get the same result , any help is appreciated 

async function fetchEmbeddedSignUrl(signatureId) {
console.log(signatureId)
const response = await fetch(`https://api.hellosign.com/v3/embedded/sign_url/${signatureId}`, {
method: 'GET',
headers: {
'Authorization': `Basic ${btoa(API_KEY + ':')}`,
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data)
return data.embedded.sign_url;
}

[pcmiguel]

What api do you use to create the signature request? 

https://api.hellosign.com/v3/signature_request/create_embedded

right? 

[Jalapina]

I’m trying to embed the documents I created on the Dropbox platform.

Are you only able to embed documents that you created with the embed create api function ?

[pcmiguel]

Yes

[DB-Des]

Hi!

That error is typically thrown when the signature request is a non-embedded signature request — it was either created in the UI or via Send Signature Request endpoint.

In order to retrieve a sign_url, to embed a document to be signed, you'll need to Create an Embedded Signature Request and then send a request (per signer) to the Get Embedded Sign URL endpoint with each signer's unique signature_id.

Hope this helps!

[Jalapina]

so the only way to sign a document via the dropbox sign api is by using the "Create Embedded Signature Request" endpoint ? we cant sign documents that we made on the dropbox platform on our app using the api ?

[DB-Des]

Hi,

Documents can be signed on the Dropbox Sign platform (non-embedded request) or on your own platform on an iframe (embedded request). On a high overview, the Dropbox Sign API can be used to create a non-embedded signature request (via /signature_request/send) or an embedded request (via /signature_request/create_embedded).

What is non­-embedded signing?

With non-­embedded signing, your users sign documents through Dropbox Sign. We notify the signer via email and collect their eSignature on Dropbox Sign. We also send signature request reminders to the signer. 

Documentation regarding non-embedded signing can be found here.

What is embedded signing?

With embedded signing, users sign directly on your web application instead of being redirected to Dropbox Sign to complete the signature process. This is achieved by displaying the document to the user at any time using the Dropbox Sign iframe. You will have complete control and flexibility with the entire signing flow which includes sending your own email notifications. Embedded workflows in general do not have any automatic emails sent from Dropbox Sign to the specified signers.

Documentation specific to embedded signing can be found here.