Integrations / Dropbox Sign

Dropbox Sign

Dropbox Sign (formerly HelloSign) e-signature platform for sending, tracking, and templating legally binding signature requests.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Dropbox Sign (HelloSign) account you can administer.

Account owner or a user who can open API settings.

Vendor setup

Get the credential

Open API settings

In Dropbox Sign, go to Settings → API (or the API tab in the old HelloSign admin).

Copy the API key

Copy the API key. Dropbox Sign uses HTTP Basic: the key is the username and the password is empty.

Paste in Telara

Settings → Integrations → Dropbox Sign. Paste the API key. Leave password blank or use a placeholder if the form requires it.

Permissions Telara requests

account_access
OAuth 2.0
signature_request_access
OAuth 2.0
template_access
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

OAuth 2.0 authorization-code connection for Dropbox Sign users. Select Signature Request Access, Template Access, and Account Access in the Dropbox Sign API app settings; the vendor applies those app-configured scopes to the resulting token. Production distribution requires Dropbox Sign app approval.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Basic auth

Dropbox Sign API key over HTTP Basic Auth. Use the API key as the username and leave the password blank (or any placeholder value — it is ignored). Confirmed against the spec's components.securitySchemes.api_key entry, which declares type http and scheme basic — not a bearer/header token scheme, despite the "api_key" name. An alternate oauth2 (bearer JWT) security scheme also exists on every operation but is out of scope here; this connector only implements the API-key/Basic path.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

API key
Password

Knowledge

What gets indexed

Resource	Coverage
Signature request	Partial — not every record the vendor holds is synced
Template	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Signature request	Up to 1 day	Removed records disappear on the next full sync
Template	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Signature request, Template.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Test-mode keys do not list production signature requests.

Team vs personal API keys see different documents.