-
Notifications
You must be signed in to change notification settings - Fork 88
Open
Description
I'm encountering an issue with the create_recipient_view method in the eSignature examples. My goal is to use this method to allow users to sign documents via a web-view. Here's the relevant code snippet I'm using:
recipient_view_request = RecipientViewRequest(
authentication_method=authentication_method,
client_user_id=envelope_args["signer_client_id"],
recipient_id="1",
return_url=envelope_args["ds_return_url"],
user_name=envelope_args["signer_name"],
email=envelope_args["signer_email"]
)
results = envelopes_api.create_recipient_view(
account_id=args["account_id"],
envelope_id=envelope_id,
recipient_view_request=recipient_view_request
)
return {"envelope_id": envelope_id, "redirect_url": results.url}
The issue I'm facing is that the generated URL returns a PDF document without the option to sign, and the fields that should be automatically populated remain empty.
I want to emphasize that my email flow works correctly: it generates an envelope with dynamically filled fields and provides the signing options. The problem only arises when using the create_recipient_view method.
Is there something I'm missing in the RecipientViewRequest configuration? Any help or guidance would be greatly appreciated.
Thank you!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels