Developer

Hi DocuSign Community,We are currently integrating with the DocuSign Navigator API in the demo environment and are facing an issue with the $search query parameter.Environment:https://api-d.docusign.comAccount ID:6ed4aa88-5dd9-499a-bc86-d2c29ab47142Issue:The following request returns 403 Forbidden:GET /v1/accounts/{accountId}/agreements?$search=sampleResponse:{"title": "Search Failed","status": 403,"detail": "The query could not be processed. Please check your filter expression."}What we verified: GET /agreements works correctly (200 OK) $filter parameter works correctly $search consistently returns 403 Combining $search and $filter re

Hi Team,  I’ m integrating docusign Embedded Signing in React js Application.   I create below component : import React, {useEffect} from 'react';import PropTypes from 'prop-types';function DocumentSignUI({integrationKey, docUrl}) { useEffect(() => { const loadDocuSign = async () => { const docusign = await window.DocuSign.loadDocuSign(integrationKey); const url = `${docUrl}&output=embed`; const signing = docusign.signing({ url, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary b

 We are facing an issue with the SuccessFactors (SF) to DocuSign connector integration for offer letters.Current Process:The recruiter sends the offer letter from SuccessFactors. The candidate successfully receives the offer letter from DocuSign. The candidate reviews, signs, and submits the offer letter.Issue Observed:After the candidate completes the signing process and submits the document, the candidate is expected to receive a copy of the fully executed/signed offer letter. However, the candidate is not receiving the signed offer letter copy via email.Request:Could you please investigate the integration/workflow and confirm why the completed signed document is not being delivered to the candidate after successful submission? Additionally, please advise if any DocuSign notification or distribution settings need to be con

 Tired of manually downloading, renaming, and routing signed DocuSign documents? 🚀 If you're working in government, public sector, or regulated environments, you know the pain: completed e-signatures pile up, and getting them into your backend systems (Box, Registries, SalesForce, LaserFiche, FTP, etc.) still feels painfully manual.That’s exactly why we built AIRLIFT.AIRLIFT is a governed integration platform that turns your DocuSign completions into clean, auditable, automated workflows — no custom scripting required. What you can do with AIRLIFT + DocuSign:- Automatically pull completed envelopes and form data- Apply field mapping, packaging, and validation- Deliver securely to Box folders, web services, registries, or other systems simultaneously- Get full visibility with stage-by-stage logging and audit trails- Stay compliant with SOC 2 / HIPAA-ready posture Whether you're processin

Hello,I’m currently integrating DocuSign into my ERP system using the API, and I’m working with a developer (demo) account.For several weeks, everything was working perfectly:Envelopes were successfully created via the API They were sent without any issues Recipients were receiving the email notifications and could sign documents normallyHowever, starting about a week ago, the behavior changed unexpectedly.Now:The API still works correctly (no errors returned) Envelopes are created and sent successfully Recipients are correctly assigned But no recipient receives any email notification at allTo troubleshoot, I have tried:Sending to multiple types of email addresses (personal, professional, temporary emails) Recreating a completely new developer account → it worked once for a single envelope, then the same issue occurred again

 Hi DocuSign Community,We are currently integrating the Navigator Agreements API and had a question regarding agreement status values shown in the DocuSign UI.In the UI, we can see statuses such as: Active Expiring Soon Renewing Soon Inactive Effective Soon However, when calling the Agreements List API (GET /agreements), these status values are not returned in the response, and we also could not find supported filters for them.We would like to understand: How can we retrieve these status values through the API? Is there any recommended approach to implement filtering for these statuses in custom integrations? At the moment, since these statuses are

Hi everyone,I am trying to create a new Developer (Sandbox) Account, but I am completely blocked at the final activation step. I’ve already contacted standard support, and after exhaustive troubleshooting, they redirected me here so the product/developer team can look into a potential frontend or application bug.The Problem:During the registration process, I reach the "Activate Your Account" screen. The page displays the following message:“Thank you for choosing Docusign. Please complete the steps below and click ACTIVATE to continue. By clicking the ‘ACTIVATE’ button, you agree to the Terms of Use and Privacy Policy”When I click the "Activate" button, the page seems to briefly reload, but nothing happens. No confirmation email is triggered. The screen does not advance. The account is not created

Hi DocuSign Community,We are testing the Navigator Agreements List API and wanted to confirm whether combining $search and $filter is currently supported.Request:GET /v1/accounts/{accountId}/agreements?$search=sample&$filter=status eq 'completed'Response:{"title": "Bad Request","status": 400,"detail": "The $search and $filter query parameters cannot be combined in the same request. Use $search for full-text search or $filter for structured filtering."}Observations: $search works correctly when used alone $filter works correctly when used alone Combining both returns 400 Bad Request However, in the DocuSign completed documents experience/UI, searching and filtering together appears to work correctly and returns expected results.We would like to confirm: Is this a current limita

I got a requirement as mentioned below:I will be triggering the journey from the oracle HCM, once the employee completed signing the document it need to be moved to oracle HCM document of records, Is that feasible to move the pdf file from Docusign to oracle HCM document of records ? 

Hello,  I would really appreciate your help. Using the API, our envelopes are created and sent with the correct prefilled values. However, when our customers open the document for signing, one of the fields (“Title”) is covered by an editable textbox with some unrelated value.This is the document before signing (created with the correct prefilled valued, Name and Title):  And this is how customers see it when signing: The correct value (“1st Degree”) is underneath a textbox with “Staff”. We have no clue where it gets this default value from or how to edit out the textbox. I’ve recreated this field several times in the template and the issue

Hey Community - hope you’re having a good day...long weekend (In UK) nearly here ! When a Completed Document gets ingested into Workday (via API) for downstream storage and processing, is that document a copy of the ‘original’ ? In other words, would a version / copy of the completed document be stored in both DocuSign AND Workday or only a ‘master’ copy stored within Workday ? Also - does the Certificate of Completion ‘route’ with the completed document into Workday (for audit) ? Hope that makes sense ! Thanks in advance. 

Hello DocuSign Support Team,I am experiencing an issue with pre-filling document generation (DocGen) form fields when creating and sending an envelope via the REST API. Despite trying multiple approaches, the fields are rendering as unresolved placeholders (e.g., {{Agreement Party}}, {{demo_field}}) in the document instead of showing the values passed through the API.---ENVIRONMENT- API Base URL: https://demo.docusign.net/restapi/v2.1/- Template ID: 3cfaca9c-ffd5-4c16-a416-992ca05317b0- Template Name: Final Contract AI- Document Type: .docx (ACE/DocGen format — isAceGenDocument: true)---FIELD DETAILS (from template response)The template contains two DocGen form fields confirmed via GET /templates/{templateId}:1. Field Label: Agreement Party   Internal Name: AgreementParty_displayName_Z2bXg

Hi, I am consuming Doc gen api to automatically generate a document in which I have an image tab. <# <Image Select="//Internal_Signature" Height="1" Width="2" Optional="true"/> #> My original image is very small and need not exceed height and width of 1 inches, but I am unable to add less than 1 inches in the above parameter.Template is in a word doc which I am passing to api The one highlighted is from the image tag, original image is below. Can someone share inputs on how to adjust the image size

Hi, i am currently in the developer phase, I was testing if multiple routing order can be done. Made a request with the following api{{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesand with body{  "documents": [    {      "documentBase64": {{document}},      "documentId": {{documentId}},      "fileExtension": "pdf",      "name": "document"    }  ],  "emailSubject": "Multiple Signing Example from api testing",  "recipients": {    "signers": [      {        "email": {{user1_email}},        "name": {{user1_name}},        "recipientId": "1",

Hello,I am experiencing an issue with the embedded signing flow and would appreciate any guidance.Scenario:We create envelopes using a system administrator account via the eSignature REST API, then attempt to generate an embedded signing URL (CreateRecipientView) while authenticated as a different DocuSign user.Error received when calling CreateRecipientView:{ "errorCode": "ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE", "message": "This account is not authorized to access the requested envelope."}What we have confirmed so far:The envelope is successfully created by the admin account. The accountId used in the CreateRecipientView endpoint matches the one used during envelope creation. recipientId and clientUserId are set in the CreateEnvelope request.

Hi,I was talking to our sys admin about some cloud flare blocking that has since been resolved, but he asked me to ask you about this image I am attaching. Can you give us some information about this screen shot ? Thank you,maggie  

Hello,I have a question regarding the userId assigned to recipients in an envelope versus the userId of an actual DocuSign account.Scenario:When we create an envelope via the eSignature REST API and then retrieve recipient information using the listRecipients API, the userId returned for the signer is different from the userId of the corresponding DocuSign account (retrieved via the Users API).For example:DocuSign account userId (Users API): AAAAA... Envelope recipient userId (listRecipients): BBBBB...The signer email address is the same in both cases, but the IDs do not match.Questions:Is the userId returned by listRecipients intended to represent a recipient-specific identifier rather than the actual DocuSign account userId?

I am working with a developer account and am receiving this error message:502: Error, {"error":"DocuSign send failed","detail":{"errorCode":"RECIPIENT_LIMIT_EXCEEDED","message":"The cumulative recipient limit has been exceeded."}}I tried deleting some envelopes but that did not resolve the issue. Our level of testing seems to be below the published threshold for a developer account.Can DocuSign reset or clarify the cumulative recipient limit on a free developer/demo account? I have also seen reference to some kind of account hold that would result in the same error message. Any insights would be appreciated.

Hi,I’m on a developer sandbox still. My connect setup is set with ‘acknowledgement required’ enabled.I’ve implemented the webhook callback endpoint. It is working fine. I’m trying to test what happens on retries if the initial callback fails. I’m returning http code 500 from the webhook endpoint. It is going through `ngrok` and I see that it is being propagated. The connect dashboard shows the event error code as ‘Success’. The API call to fetch failures returns empty. No retries are sent.The only way I managed to cause it to log an error and retry is if I stopped the process enough for the 100 second limit to engage.I thought maybe something was ‘stuck’ in the settings so I wanted to disable and re-enable the ‘acknowledgement required’ setting, so I tried to disable ‘acknowledgement required’ but upon saving and refreshing, the setting comes back as enabled. I tried to update it through an API call with the same results.I also tried to do see if I

 send 3 documents in a DS envelope - Offer Letter (signatures) Non Disclosure Agreement (Signatures) Benefits Overview no signatures or field completion required.Candidates are saying they cannot see the last document which is a one page benefit summary.  I have no idea why, unless it is because that doc requires no signatures it is just informational?  Has anyone else had this?