Integrating With Us

A few words on the integration process

We work closely with software companies, platforms, and developers to create deep integrations that enhance workflow automation for mutual clients. But our bread and butter is sending documents for signing!

Integration Types

We have two primary integration types depending on who you are.

a) Product Integration

• This is another piece of software pushing or pulling information into FuseSign.

b) Private integration into a FuseSign account

• This is typically a large firm that wants to automate processes

Requires Enterprise plan. Read about our pricing plans

How we work with Application Partners

• Intro Call & Use Case Review Let’s understand your platform and your clients’ needs.

• Tech Alignment Call We’ll provide API documentation and sample use cases to validate technical feasibility. Following this we will provide access keys to our production environment with a test developer account loaded with some credits!

• Integration Build You develop the integration with guidance from our technical team as needed. Your account is placed InReview mode which places a watermark on documents you send for signing. Read more below, In Review Mode.

• Review An online review session is conducted to ensure the integration has met the intended requirements.

• Joint Launch Once tested, we’ll support you in announcing and promoting the integration to our mutual audiences.

In Review Mode

To get the best signing experience possible and to ensure proper performance we place a watermark on all bundle documents sent for signing from a developer InReview . All other functionality is the same!

Example Signed Document While InReview

"Sign Entire" document, signed while InReview

What happens on the review call

Review of Use Case Alignment

To get InReview toggled off we need to see demonstration over video call, or recording of the signing flow:

1

Upload a document

If uploading a document via POST /api/Bundle/Create please do not use base64!

2

Create a bundle

We have a few different ways to create a bundle, read more in this deepdive Bundle Create

3

Sign the bundle

Protip: the response to a bundle create contains the property CustomerSignUrl

4

Webhook utilisation

We support webhooks out of the box, read more in this deepdive Webhooks

Questions to expect

Please prepare responses for the following questions:

• How does your integration handle two people with the same email?

• How do you cancel an active bundle?

• How do you remind participants of an active bundle?

• What happens when a signer rejects a single document?

• What verification is used, is it able to handle Email / SMS or both?

• If using anchor searching for placeholder creation, what tags are you using?

• Where and how do you document your support processes?

• How would you like to work with us for developer support ongoing?

• How should we contact you if there are issues with this integration?

Notes for Production Use

• Confirm that any applicable URLs for uploads are whitelisted.

Final Decision and Account Upgrade

• Once all above criteria are met, we will remove the watermark from documents generated by the developer's integration and you're ready for production usage!

For more information email us at [e-mail].