A reseller partnership requires you to build the integration and own the customer-facing experience. Before applying, make sure your organisation can meet the following requirements.
| Requirement | Why it's required |
|---|---|
| Customer portal or login system | The integration runs inside your software; your customers use the feature there. |
| Development resource | You build and maintain the integration against Signable's REST API, including authentication, error handling, and webhooks. |
| Support capacity | You provide first-line and ongoing support to your customers (sub-accounts). Signable does not support sub-account customers directly. |
| Pricing and go-to-market plan | You decide how to package, price, and launch the feature. |
You can choose to amplify your reach through co-marketing with Signable. Participation is completely optional.
If you do not have the development capacity to build the integration or cannot provide customer support, consider the Referral Partner type, under which Signable bills and supports the customers you introduce.
If the Reseller Partner type fits your use case, contact the Partnerships team to get started.
You provide: a description of your platform, your intended use case, and how you plan to price the feature.
Signable provides: confirmation of the partnership type and the welcome pack.
| Responsibility | Owner |
|---|---|
| Integration design, configuration, and maintenance | Partner |
| End-customer and sub-account support | Partner |
| API documentation and API-behaviour questions | Signable |
| Signable service availability | Signable |
Once Signable confirms that the Reseller Partner type fits your use case, both parties complete the reseller agreement and confirm the commercial terms.
You build:
- Authentication with your Signable API key.
- Envelope creation and sending from within your product, using the Signable API; test against the API before going live.
- Sub-account lifecycle management, using the Partners endpoints.
- Webhook handling for signature events.
- Optionally, embedded signing for in-product signing.
Signable provides: support on API behaviour throughout the build (Signable cannot see or configure your software). You can request industry context, security information, case studies for training your internal teams and preparing launch material.
Prepare the sub-account experience before adding real customers.
Before onboarding customers, configure:
- Templates for each customer, set up manually in the web app.
- Branding per sub-account, so each customer's signature request emails and signing pages render with their own branding.
Once the agreement is complete and you are ready to onboard customers, Signable activates your partner plan.
Activation:
- Sets your recurring monthly billing date (billed in arrears).
- Enables you to begin creating sub-accounts for your customers.
Before creating a sub-account for a customer who already holds a direct Signable account, see migrating existing customers.
- Track all sub-account usage via
GET /usage. - Your Reseller Partner Manager holds quarterly reviews and remains your point of contact.
| Purpose | Link |
|---|---|
| Partner enquiries | Become a Signable partner |
| Service status | Signable status page |
| Support | Contact Support |