Usage question about docusign-rest-client HOT 7 CLOSED

Looking at the source it looks like the first account returned in the login response is the account used for future calls after that and is automatically prepended to the argument list.

Since this is a thin wrapper around the docusign-php-client we'd actually be using the listTabs method on the TemplatesApi class.

So for this one it looks like it should be:

$client->templates->listTabs($recipient_id, $template_id);

from docusign-rest-client.

That makes a whole lot of sense. It's a valuable lesson in terms of knowing what packages are making easier in terms of interaction.

I'll give this a go, thanks again.

from docusign-rest-client.

Looking at the source it looks like the first account returned in the login response is the account used for future calls after that and is automatically prepended to the argument list.

Since this is a thin wrapper around the docusign-php-client we'd actually be using the listTabs method on the TemplatesApi class.

So for this one it looks like it should be:

$client->templates->listTabs($recipient_id, $template_id);

Just because I'm sometimes a bit dense. Do you just look for the equivalent from the PHP wrapper?

from docusign-rest-client.

Yup.

This client wraps that and will take care of injecting the account id as the first parameter to all methods that require it.

from docusign-rest-client.

That's very cool. I think I'll close this and go find out how to grab the recipient ID, basically a guy made a template and added a load of tabs to it that he wants me to pre-fill via a webform, but I've not even been given any labels, so it's been 'interesting'.

This wrapper has been super helpful though

from docusign-rest-client.

@Tucker-Eric just to follow up, I didn't see a tabs api so in this case are they passed per signer?

from docusign-rest-client.

@blorange2 the way I would approach it based on the uri /v2/accounts/{accountId}/templates/{templateId}/recipients/{recipientId}/tabs. Anything that is account level is automatically handled post authentication for you so we can omit the /v2/accounts/{accountId} portion, which leaves us templates/{templateId}/recipients/{recipientId}/tabs. With templates as the first uri segment, that led me to TemplatesApi which is where I found the listTabs method that is per recipient which seemed like it fit your use case.

Looking at Docusign's TemplatesApi it looks like there is a listDocuments method that can respond with all tabs when passed the option to like:

$templateApi = $client->templates;
$templateApi->listDocuments($template_id, $templateApi->listDocumentsOptions(['include_tabs' => true]));

I hope this makes some sense?

from docusign-rest-client.