Integration
Connect NetLicensing to BoldSign
When something happens in NetLicensing, your agent does the next thing in BoldSign. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want NetLicensing and BoldSign to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with NetLicensing and BoldSign
Triggers and actions 2 triggers · 25 actions
Trigger
New LicenseeTriggers when a new licensee is created
Trigger
New ProductTriggers when a new product is created
Action
Create LicenseIssue a new license for a licensee. POST /core/v2/rest/license (licenseeNumber, licenseTemplateNumber, plus template-dependent params).
Action
Create LicenseeCreate a new Licensee
Action
Delete LicenseDelete a license by licenseNumber. DELETE /core/v2/rest/license/{licenseNumber}.
Action
Delete LicenseeDelete a licensee by licenseeNumber. DELETE /core/v2/rest/licensee/{licenseeNumber}.
Action
Delete ProductDelete a product by productNumber. DELETE /core/v2/rest/product/{productNumber}.
Action
Find a LicenseGet a license by licenseNumber, or list all licenses. GET /core/v2/rest/license/{licenseNumber} or GET /core/v2/rest/license.
Action
Find a LicenseeSearch a Licensee by its number
Action
Find a License TemplateGet a license template by licenseTemplateNumber, or list all license templates. GET /core/v2/rest/licensetemplate/{licenseTemplateNumber} or GET /core/v2/rest/licensetemplate.
Action
Find a ProductSearch a Product by its number
Action
Update LicenseUpdate an existing license by licenseNumber. POST /core/v2/rest/license/{licenseNumber}.
Action
Update LicenseeUpdate an existing licensee by licenseeNumber. POST /core/v2/rest/licensee/{licenseeNumber}.
Action
Update ProductUpdate an existing product by productNumber. POST /core/v2/rest/product/{productNumber}.
Action
Add contactAdds a contact to BoldSign so it can be picked as a signer when creating documents. Returns the new contact's id and email address.
Action
Delete contactDeletes a contact from your BoldSign organization by its contact ID.
Action
Delete documentDeletes a BoldSign document. By default the document moves to trash for 30 days; it can be removed permanently instead.
Action
Download documentDownloads the signed PDF of a BoldSign document and returns it as a file you can attach or upload in later steps.
Action
Get contactReturns the details of a BoldSign contact — name, email, company, job title and phone number.
Action
Get documentReturns the properties of a BoldSign document — its status, title, signers and timestamps.
Action
List contactsReturns the contacts in your BoldSign organization, optionally filtered by a search keyword.
Action
List documentsReturns the documents in your BoldSign account, with optional filters for status, sender, signer, labels and date range.
Action
List templatesReturns the reusable templates in your BoldSign account, with optional filters for type, creator, labels and brand.
Action
Revoke documentRevokes a BoldSign document that is still in the signing workflow, so signers can no longer open it. The reason you supply is shown to the signers.
Action
Send documentSends a document out for signature in BoldSign: uploads the file, adds up to three signers with their signature fields, and returns the new document's id.
Action
Send document reminderEmails a reminder to the signers who have not yet signed a BoldSign document. A manual reminder can be sent once a day.
Action
Update contactUpdates an existing BoldSign contact's name, email, phone number, job title and company.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.