In-app signing workflows
Embed signing and requesting flows directly in your product.
Dropbox Sign Connector
Build in-app eSignature workflows, send and track signature requests, and embed signing experiences for customers using Cyclr’s low-code integration builder and white-label marketplace.
Governed MCP tools
Expose selected Dropbox Sign methods as controlled tools for customers.
Operational controls
Centralize credentials, retries and error handling across tenants.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
The Dropbox Sign connector gives SaaS product teams programmatic access to signature requests, templates, embedded signing and account features. Use Cyclr to orchestrate multi-step workflows, capture signed documents, and deliver customer-facing signing flows inside your application without building each integration from scratch.
PRODUCT USE CASES
Use cases
Create in-app signing flows, automate document delivery and downloads, embed template editors, and publish governed integrations to your customers via Cyclr’s embedded marketplace.
In-app contract sending and signing
Allow users to generate and send contracts from your app, track signer status and download final signed PDFs automatically.
Embedded onboarding forms and agreements
Embed signing flows and template editors so customers sign onboarding documents without leaving your product.
Automated approvals and bulk sends
Automate bulk signature distribution and reminders for invoices, NDAs and regulatory documents across tenants.
ORCHESTRATION
How Dropbox Sign works with Cyclr
Cyclr sits between your SaaS product and Dropbox Sign to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Dropbox Sign
Dropbox Sign processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Dropbox Sign methods you can orchestrate through Cyclr.
Account1
Get Account
ActionGets an account by Account ID.
Signature Request5
List New Signature Requests
ActionLists new Signature Requests since last run.
Get Signature Request
ActionGet a Signature Request by specified ID.
Get Signature Request PDF
ActionGet a Signature Request Data String or URL.
Send Signature Request
ActionCreates and sends a new Signature Request.
List Signature Requests
ActionLists all Signature Requests.
TECHNICAL DETAILS
Dropbox Sign integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Dropbox Sign integrations in Cyclr.
API and authentication
- API host
https://api.hellosign.com/v3- Authentication
- API key (Basic) or OAuth 2.0 (Bearer)
- Credentials
Account API key or OAuth client_id and client_secret; callback URL for API apps.
- Method categories
Signature requests, templates, embedded signing, API apps, accounts, teams, reports, callbacks.
Pagination and rate limits
Pagination
Page-number pagination using page and page_size (1–100). Responses include list_info with page, page_size, num_pages and num_results.
Rate limits
Standard endpoints ~100 requests per minute; higher-tier document endpoints ~25 per minute; test mode ~10 per minute. Rate headers and 429 responses provided.
IMPLEMENTATION
Authentication at a glance
Supports account API keys via HTTP Basic auth and OAuth access tokens (Bearer). API key is used as Basic username with empty password; OAuth tokens go in Authorization header.
- Authentication method
- API key (Basic) or OAuth 2.0 (Bearer)
- Credential required
Account API key or OAuth client_id and client_secret; callback URL for API apps.
Before you begin:
View setup guideEmbedded or OAuth apps may require Dropbox Sign app approval or self-publish before production.
COMMON QUESTIONS
Frequently asked questions
Dropbox Sign supports account API keys (HTTP Basic with key as username) and OAuth access tokens (Bearer). Cyclr can store either credential type and use them per-tenant.
Yes. Dropbox Sign supports embedded signing and embedded templates. Embedded and OAuth workflows may require app approval or self-publishing before production.
Events are sent as multipart/form-data with a json field. Use the event_hash or Content-Sha256 and IP whitelist to verify callbacks; Dropbox Sign requires HTTPS for callbacks.
Design for ~100 requests per minute for standard endpoints, ~25 per minute for document-heavy endpoints and ~10 per minute in test mode. Honor X-Ratelimit-* headers and handle 429 responses.
KEEP EXPLORING
Related resources and connectors
Documentation
How to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorGoogle Cloud Storage
Related Data Tools connector for customer-facing integration workflows.
Related connectorHarbour
Related Data Tools connector for customer-facing integration workflows.
Related connectorSmartsheet
Related Data Tools connector for customer-facing integration workflows.