INVALID_REQUEST_BODY

​@Karupps 

When you see the error message "INVALID_REQUEST_BODY" when trying to create a prefill tab, it almost always means DocuSign did not recognize your request body as containing any valid tabs. In other words, the JSON structure you are sending isn’t matching what the API expects.

• Remove the "tabs": { ... }" wrapper.
• Put your prefillTabs at the top level of the envelope request body.
• If you are adding to a template via the .../templates/{templateId}/tabs endpoint, do not use prefillTabs at all—use the standard "textTabs": [ ... ] array instead.

you can reference this document:https://www.docusign.com/blog/developers/common-api-tasks-customize-your-envelopes-pre-fill-fields and https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/prefilled-tabs/

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant
🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/

Now I have encountered a new issue with the Prefiltab POST call. The issue is mentioned below

{

    "errorCode": "INVALID_TAB_OPERATION",

    "message": "The Tab specified is not valid for the requested operation. PrefillTab is"

}

Could you please share a sample request? It is very important for me

Hi ​@Karupps,

I wanted to clarify a point regarding Prefill Tabs. These tabs are generally intended for the sender to prefill certain fields before sending the document for signature. However, if your goal is simply to prefill data for the recipient via the API, you don't necessarily need to use the Prefill Tabs object.

Instead, you can achieve this by using regular signer tabs.

• You can define the text tab as a regular signer tab, set its value, and then lock it by setting the locked attribute to true. This prevents the recipient from editing the prefilled field.

I’ve attached a sample request. In this sample:

• The document contains an anchor string (/CompanyName/) where the prefilled value will be placed.

• The anchor string's font color is matched with the document background color (white), so it's invisible to the recipient.