Docusign Developer StrawberryThe Docusign Developer signature requests nobody wants to work through
It reads every signature request your Docusign Developer account holds, drafts the change that follow, and hands you a card for each one before a single signature request moves.
Open the signature request. Check it against something else. Write the change. Move to the next one. That is the Docusign Developer afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a signature request until you approve it.
What it can do is exactly what Docusign Developer exposes to an account you authorise and nothing beyond it: 1 operation, no reads and 1 write. In practice that means it can create a signature request.
The Docusign Developer API stops at Docusign Developer. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Docusign Developer signature requests does a companion see?
In the tab.
Docusign Developer exposes no read operation to a connected account, so a companion opens Docusign Developer in the session you are already signed into and reads the screens you would.
The signature requests are what most of this inventory is about, alongside the signature requests. A companion can hold that operation and forty open tabs in the same pass, which is how an afternoon of Docusign Developer admin becomes a queue you review.
Can it change a signature request without asking?
The one write operation there is waits for you.
A companion can create a signature request, and each one is staged on an approval card first: you see the signature request, the field and the new value before it lands in Docusign Developer.
Nothing in Docusign Developer is sent, changed or deleted on your behalf without that click, and a rejected card leaves the signature request exactly as it was. The gate is the same one on every surface, described at security.
- Create Signature Request
Can it create signature request on a schedule?
Yes.
Saved as a routine, the Docusign Developer signature requests pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the operations, the Docusign Developer signature requests sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents