RightSignature Public API v2: one-off sending_request auto-send errors at "Creating Document from file" for every PDF, but prepare_document:true builds the doc fine. Upload is verified good (S3 200, ETag=MD5). How do I get the non-prepare path working?
  1. Why does the non-prepare (auto-send) path error at "Creating Document from file" when prepare_document:true succeeds on the identical upload?
  2. Is anything needed on the account to enable API document creation on the auto-send path?
  3. For per-document (non-template) API sending, is there a supported alternative to the one-off sending_request that finalizes headlessly (no browser document-builder step)?

 


  • Hello @Shams Khan​ - Thank you for posting your query on the forums. I believe you already have a ticket with us with Support team.

     

    From the case notes, we appreciate your testing and isolation (non text tags, size checking etc);

     

    We've updated the agent internally and they'll keep working on this to resolve your issue. Please note that the API functionality is working globally and we'll make sure to provide a resolution.

     

     

    EDIT 1 (10 July 2026) - For future reference and other people browsing the forums, our current hypothesis for the above issue was that the "identity_method" and "api_embedded" parameters were misconfigured. For all API related issues, it'll be appreciated if you can help us with the endpoints and payload (PII redacted) for troubleshooting.

     

    Selected as Best
  • Hello @Shams Khan​ - Thank you for posting your query on the forums. I believe you already have a ticket with us with Support team.

     

    From the case notes, we appreciate your testing and isolation (non text tags, size checking etc);

     

    We've updated the agent internally and they'll keep working on this to resolve your issue. Please note that the API functionality is working globally and we'll make sure to provide a resolution.

     

     

    EDIT 1 (10 July 2026) - For future reference and other people browsing the forums, our current hypothesis for the above issue was that the "identity_method" and "api_embedded" parameters were misconfigured. For all API related issues, it'll be appreciated if you can help us with the endpoints and payload (PII redacted) for troubleshooting.

     

    Selected as Best