Unable to access Hidden Field in API Connector

Support
1

Hi, I am able to access hidden fields that I am setting via API connectors in later API Connector instances.

However there is 1 specific hidden field that does not appear to be accessible in the payload when I am trying to access it in the API Connector.
See my video:

2

Hi @bercohen,

I think this is because The {{Docusign Template ID}} is paing passed inside a , If you remove the square brackets, this should work.
image

Let me know if it works.

3

Thanks @Kenny, however placing this value inside the bracket is a requirement of the API endpoint.
Is there any work around here?

4

I actually tested your Docusign API 2, connector and the API endpoint accepted the field without the square brackets, can you give it a try?

5

Thanks @Kenny mine seemed to have returned a Salesforce API error.
Can you share a screenshot of the format that worked for you?

6

Hi bercohen,

I tried and see the Docusign ID is now present on the payload for the Docusign API 2 and also on the Salesforce Intake API.

This is the initial problem you got right?

image
image1410×1076 216 KB

Here are the payload for salesforce intake api and the Docusign Api 2 after your changes.

image
image800×435 19.3 KB

image
image800×457 19.2 KB

7

@Kenny it seems you are correct that sending the Docusign Template ID inside of the brackets means it can not be included in the payload.
However the API requires us to send it inside of the brackets in the API body.
Is there a workaround for this?

8

Hi @bercohen

Let me check this further, can I ask API is rejecting the docusign id that isn’t inside a square bracket?

9

@Kenny yes this is correct.
I was able to work around this by calling the API from javascript instead of with an API connector.
Ideally I would be able to do it from the connector though

10

What does it show when you populate the value directly from the api connector?

11

When the Docusigh Template ID value is in the bracket is does not get included in the payload so the Salesforce API response comes back empty because that value is required

12

Hi @bercohen,

Great work on finding a workaround to achieve your goal. We will implement this as an improvement to our API Connector to save you trouble in the future. We’ll keep you posted once it is deployed.

1 Like