Skip to main content
Workspace settings allow you to customize email templates, team contact information, and timezone preferences at the workspace level. These settings apply to all signing requests and templates within the workspace.

Use cases

  • Custom email branding: Personalize email headers and body text for signing request invitations
  • Team contact info: Set a team email for recipient support questions
  • Timezone management: Configure timezone for date/time displays and reminders
  • Multi-tenant applications: Separate settings per workspace for white-label solutions
See the guide on Rate Limits.

Get workspace settings

Retrieve current workspace settings including email templates, team email, and timezone configuration.

Endpoint

Parameters

  • workspace_id (string, required) - UUID of the workspace

Example — cURL

Response (200 OK)

Response fields

  • workspace_id (string) - Workspace UUID
  • email_header (string) - Custom header text for signing invitation emails
  • email_body (string) - Custom body text for signing invitation emails
  • team_email (string) - Contact email displayed to recipients
  • timezone (string) - IANA timezone identifier (e.g., “America/New_York”)
  • updated_at (string) - ISO 8601 timestamp of last update

Rate limit headers


Update workspace settings

Update workspace settings. You can update one or more fields — only provided fields will be updated.

Endpoint

Parameters

  • workspace_id (string, required) - UUID of the workspace

Request body

All fields are optional — only include fields you want to update:

Field descriptions

  • email_header (string, optional) - Custom header text for signing emails (max 255 characters)
  • email_body (string, optional) - Custom body text for signing emails (max 2000 characters)
  • team_email (string, optional) - Valid email address for recipient support
  • timezone (string, optional) - IANA timezone identifier

Example — cURL

Response (200 OK)

Returns the updated workspace settings:

Rate limit headers


Implementation examples

Node.js (Express) — Get settings

Node.js (Express) — Update settings

Python (Flask) — Get settings

Python (Flask) — Update settings

React — Settings management component


Email template customization

Best practices

Email header (max 255 characters):
  • Keep it concise and action-oriented
  • Clearly state the purpose (“Sign your agreement”, “Review document”)
  • Avoid generic text like “You have a notification”
Email body (max 2000 characters):
  • Explain what the recipient needs to do
  • Include support contact information
  • Set expectations (urgency, deadline if applicable)
  • Keep tone professional but friendly

Example templates

Professional services:
Real estate:
HR onboarding:
Generic/flexible:

Supported timezones

Workspace settings support all IANA timezone identifiers. Common timezones:

United States

  • America/New_York - Eastern Time
  • America/Chicago - Central Time
  • America/Denver - Mountain Time
  • America/Los_Angeles - Pacific Time
  • America/Anchorage - Alaska Time
  • Pacific/Honolulu - Hawaii Time

Europe

  • Europe/London - GMT/BST
  • Europe/Paris - Central European Time
  • Europe/Berlin - Central European Time
  • Europe/Madrid - Central European Time
  • Europe/Rome - Central European Time

Asia Pacific

  • Asia/Tokyo - Japan Standard Time
  • Asia/Shanghai - China Standard Time
  • Asia/Singapore - Singapore Time
  • Asia/Dubai - Gulf Standard Time
  • Australia/Sydney - Australian Eastern Time

Americas

  • America/Toronto - Eastern Time (Canada)
  • America/Vancouver - Pacific Time (Canada)
  • America/Mexico_City - Central Time (Mexico)
  • America/Sao_Paulo - Brasilia Time
Full list of IANA timezones

Rate limiting

Get workspace settings

  • Limit: 200 requests per minute
  • Use case: Frequent reads for dashboard displays
  • Recommendation: Cache settings client-side for 5-10 minutes

Update workspace settings

  • Limit: 100 requests per minute
  • Use case: Admin configuration changes
  • Recommendation: Debounce updates in UI (wait 1-2 seconds after user stops typing)

Rate limit headers

Every response includes:

Handling rate limits

If you exceed the limit:
Best practices:
  • Implement client-side caching
  • Debounce frequent updates
  • Check X-RateLimit-Remaining before making requests
  • Implement exponential backoff for retries

Error responses

400 Bad Request — Validation error

Invalid input data (e.g., malformed email, invalid timezone):

401 Unauthorized

Invalid or missing API key:

404 Not Found

Workspace doesn’t exist or you don’t have access:

429 Too Many Requests

Rate limit exceeded:
Check X-RateLimit-Reset header for when you can retry.

Multi-tenant best practices

For multi-tenant applications (multiple workspaces):

1. Cache settings per workspace

2. Validate workspace access

Always verify the authenticated user has access to the workspace:

3. Audit logging

Log all settings changes for compliance:

4. Default settings on workspace creation

Set sensible defaults when creating new workspaces:

Troubleshooting

Settings not applying to emails

Symptom: Updated settings don’t appear in signing emails Possible causes:
  • Email template cache not cleared
  • Wrong workspace ID used
  • Updates didn’t save (check API response)
Solution:
  • Verify update was successful (check 200 response)
  • Test with a new signing request (not existing draft)
  • Check workspace ID matches signing request

Invalid timezone error

Symptom: 400 error when setting timezone Solution: Use IANA timezone identifiers (e.g., “America/New_York”, not “EST”)

Team email validation failure

Symptom: 400 error on team email update Solution: Ensure valid email format (contains @ and domain)

Rate limit exceeded

Symptom: 429 errors when updating settings Solution:
  • Implement debouncing on form inputs
  • Cache settings client-side
  • Wait for X-RateLimit-Reset before retrying
See the guide on Rate Limits.

API reference

For complete details on workspace operations, see:

Workspace Management

Workspace Settings


Next steps