> For the complete documentation index, see [llms.txt](https://fuseworks.gitbook.io/fusesign/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fuseworks.gitbook.io/fusesign/getting-started/readme.md).

# An Overview

## Welcome to the FuseSign API

This API Allows you to interact with the FuseSign platform to send out signing bundles.

<figure><img src="https://2334922495-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZtImBHbaWiDQmQ3uJAL%2Fuploads%2FPhHY5rrbRb7HYqhdnZo1%2Ffusesign.png?alt=media&amp;token=8f6ea389-3968-4bc8-a458-4e7881ec610f" alt=""><figcaption></figcaption></figure>

For more information on FuseSign please see [https://fusesign.com](https://fusesign.com/) or <developersupport@fuse.work>. \
\
*To interact with API using postman, we suggest following the process of importing* [*swagger into postman*](https://learning.postman.com/docs/getting-started/importing-and-exporting/importing-from-swagger/) *using the public* [*swagger.json*](https://api.fuse.work/swagger/v1/swagger.json)

### Key Features

* OAuth2 or fixed header authentication.
* GUIDs everywhere! (tenants, bundles, documents, customers, webhooks)
* Webhooks for any events on a sent document bundle.
* Metadata can be attached to objects to allow reference back to an external API.
* Multiple methods to achieve the same result. *For example:*
  * A document can be uploaded before a bundle is sent and linked via ID, or sent via encoded base64, or sent via a download URL.
  * A customer can be created before a bundle is sent and linked via ID or can be included in the bundle payload.

### Special Cases

* Creating a Draft: To create a bundle as a draft, Set the **CreationMode** to **CreateAsDraft**.
  * This will populate the **DraftUrl** on the response bundle which can be used to review and send the bundle.
* No FuseSign Emails: To disable FuseSign emails Set the Bundle -> Settings -> EmailPreference to NoFuseSignEmails.
  * This will require you to have permission to use the [GetCustomerSigningLink](https://api.fuse.work/api/Bundle/GetCustomerSigningLink) endpoint. Please contact us with your usecase.
* View Modes (2FA)
  * **SmsToSign** will require 2FA authentication before signing. \
    \[*Requires all customers to have a mobile number*]
  * **SmsToView** will require a 2FA code before the recipient can even view the document.\
    \[*Requires all customers to have a mobile number*]
  * **EmailToSign** and **EmailToView** only requires an email address.

***

Any questions please don't hesitate to contact us at <developersupport@fuse.work>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://fuseworks.gitbook.io/fusesign/getting-started/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
