> For the complete documentation index, see [llms.txt](https://docs.slingdata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slingdata.io/connections/api-connections/dropbox-sign.md).

# Dropbox Sign

Connect & Ingest data from Dropbox Sign

Dropbox Sign (formerly HelloSign) is an eSignature platform for sending, signing, and managing legally binding documents. The Sling Dropbox Sign connector extracts data from the Dropbox Sign API, supporting signature requests, templates, API apps, bulk send jobs, and account details.

{% hint style="success" %}
**CLI Pro Required**: APIs require a [CLI Pro token](/sling-cli/cli-pro.md) or [Platform Plan](/sling-platform/platform.md).
{% endhint %}

## Setup

The following credentials and inputs are accepted:

**Secrets:**

* `api_key` **(required)** -> Your Dropbox Sign API key

**Inputs (optional):**

* `anchor_date` (optional) -> The start date for the first incremental sync of `signature_requests`. The default is 1 year ago. Format: `YYYY-MM-DDTHH:MM:SSZ`

### Getting Your API Key

Dropbox Sign provides free API access for testing with test mode enabled:

1. Sign up for a free account at <https://app.hellosign.com/>
2. Go to **Settings** > **API**
3. Under the **API** tab, click **Generate key**
4. Copy the generated API key

{% hint style="info" %}
**Test Mode:** Signature requests created with `test_mode=1` are not legally binding and are free to use during development.
{% endhint %}

### Using `sling conns`

{% code overflow="wrap" %}

```bash
sling conns set DROPBOX_SIGN type=api spec=dropbox-sign secrets='{ api_key: "${DROPBOX_SIGN_API_KEY}" }'
```

{% endcode %}

### Environment Variable

See [here](https://docs.slingdata.io/connections/api-connections/pages/eAdVs2BHCgdr6RS8GoJC#dot-env-file-.env.sling) to learn more about the `.env.sling` file.

{% code overflow="wrap" %}

```bash
export DROPBOX_SIGN='{ type: api, spec: dropbox-sign, secrets: { api_key: "your_api_key_here" } }'
```

{% endcode %}

### Sling Env File YAML

See [here](https://docs.slingdata.io/connections/api-connections/pages/eAdVs2BHCgdr6RS8GoJC#sling-env-file-env.yaml) to learn more about the sling `env.yaml` file.

```yaml
connections:
  DROPBOX_SIGN:
    type: api
    spec: dropbox-sign
    secrets:
      api_key: ${DROPBOX_SIGN_API_KEY}
```

**With anchor date for historical data:**

```yaml
connections:
  DROPBOX_SIGN:
    type: api
    spec: dropbox-sign
    secrets:
      api_key: ${DROPBOX_SIGN_API_KEY}
    inputs:
      anchor_date: "2024-01-01T00:00:00Z"
```

## Replication

Here's an example replication configuration to sync Dropbox Sign to a PostgreSQL database:

```yaml
source: DROPBOX_SIGN
target: MY_POSTGRES

defaults:
  mode: full-refresh
  object: public.dropbox_sign_{stream_name}

streams:
  # sync all endpoints
  '*':

  # incremental sync for signature requests
  signature_requests:
    mode: incremental
    primary_key: [signature_request_id]
    update_key: created_at
```

## Endpoints

| Endpoint             | Description                                                     | Incremental        |
| -------------------- | --------------------------------------------------------------- | ------------------ |
| `signature_requests` | All signature requests with metadata                            | Yes (`created_at`) |
| `templates`          | All reusable document templates                                 | No                 |
| `api_apps`           | API applications integrated with Dropbox Sign                   | No                 |
| `bulk_send_jobs`     | Bulk signature send jobs (needs a paid API plan to create jobs) | No                 |
| `account`            | Authenticated account details and quota information             | No                 |

## Incremental Sync

The `signature_requests` endpoint supports incremental sync with the `created_at` field. The API has no date filter, but it lists the newest requests first. Sling stops to read pages when it reaches a request that is not newer than the last synced value. On the first sync, Sling uses `anchor_date` (default: 1 year ago) as the limit.

Sling reads the whole page that holds the limit. It merges the records on the primary key, so no duplicate rows occur.

If you are facing issues connecting, please reach out to us at <support@slingdata.io>, on [discord](https://discord.gg/q5xtaSNDvp) or open a Github Issue [here](https://github.com/slingdata-io/sling-cli/issues).


---

# 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://docs.slingdata.io/connections/api-connections/dropbox-sign.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.
