What is the GetAccept Public API?
The GetAccept Public API is a REST-based interface that allows you to programmatically interact with GetAccept from custom applications and workflows. You can use the API to automate document creation, sending, signing workflows, recipient management, and data retrieval,enabling seamless integration between GetAccept and your internal systems.
The API is designed for developers who need to build custom integrations beyond pre-built connectors. Common use cases include automating repetitive document workflows, syncing data between GetAccept and proprietary tools, building custom reporting dashboards, and triggering actions based on document events.
Plan Requirements
Access to the GetAccept Public API requires a Professional plan or higher. If you're on a lower plan and need API access, contact GetAccept support to discuss plan options.
Authentication
The GetAccept Public API uses API key-based authentication. Each API key is tied to a specific user account and grants access to that user's documents, templates, and related data.
Generating an API Key
To create and manage API keys, navigate to your settings by clicking your profile image in the top-right corner, then select **Settings**. Look for the API or Developer settings section. Generate a new API key and store it securely,treat it like a password. Once generated, you'll see the key displayed once; copy and save it immediately as you cannot retrieve it again.
You can create multiple API keys for different applications or purposes. If a key is compromised, you can revoke it immediately from the settings panel.
Using Your API Key in Requests
Include your API key in the Authorization header of every request. The format is:
Authorization: Bearer YOUR_API_KEY
All requests must be made over HTTPS. Requests without a valid API key will be rejected with a 401 Unauthorized response.
Request and Response Format
The GetAccept Public API communicates using JSON (JavaScript Object Notation). All request bodies must be valid JSON, and all responses are returned in JSON format.
When you send a request, include the Content-Type: application/json header. The API will respond with a JSON object containing the requested data, metadata, or error details.
Rate Limits and Throttling
GetAccept enforces rate limits to ensure fair usage and platform stability. Rate limits are applied per API key and vary based on your subscription plan. When you approach or exceed the rate limit, the API returns a 429 Too Many Requests response.
To avoid hitting rate limits, implement exponential backoff in your integration,if you receive a 429 response, wait before retrying the request. Check the response headers for rate limit details and remaining quota.
Supported Endpoints Overview
The GetAccept Public API includes endpoints for managing key resources:
Documents , Create, retrieve, update, and manage documents and contracts
Recipients , Add, update, and manage signing recipients and approvers
Signing Workflows , Trigger signing actions, retrieve signing status, and manage signature data
Templates , Retrieve template information and use templates to create documents
Contacts , Manage contact information for recipients
Data Retrieval , Query document engagement metrics, signing events, and audit logs
Not all operations are available through the API. Some administrative functions remain available only in the GetAccept web interface.
Common HTTP Status Codes
The API uses standard HTTP status codes to indicate request success or failure:
200 OK , Request succeeded; response body contains the requested data
201 Created , Resource was successfully created
400 Bad Request , Your request was malformed or contained invalid parameters
401 Unauthorized , API key is missing, invalid, or expired
403 Forbidden , Your API key lacks permission to access this resource
404 Not Found , The requested resource does not exist
429 Too Many Requests , You have exceeded the rate limit; wait before retrying
500 Internal Server Error , GetAccept experienced a server error; retry after a delay
Error Handling
When an error occurs, the API returns a JSON response with an error code and message explaining what went wrong. Always check the HTTP status code first; then examine the response body for details.
Implement error handling in your integration to gracefully manage failed requests. Log errors for debugging, implement retry logic for transient failures (5xx errors), and alert your team to authentication issues (401/403 errors) that may indicate a compromised or expired API key.
Best Practices for API Integration
Keep API keys secure , Store keys in environment variables or secure secret management systems, never hardcode them in source code or commit them to version control
Use HTTPS only , All API calls must use HTTPS; unencrypted HTTP requests will fail
Implement retries with exponential backoff , If a request fails, wait an increasing amount of time before retrying to avoid overwhelming the API
Monitor rate limits , Track your API usage and adjust request frequency to stay within limits
Validate input data , Ensure all data sent to the API is properly formatted and complete before submission
Log API interactions , Record API requests and responses for debugging and audit purposes
Test in a non-production environment first , Use test data and staging environments to validate your integration before deploying to production
Keep your integration updated , Monitor GetAccept API documentation for deprecations and breaking changes
Common Use Cases
Automating document workflows: Use the API to automatically create and send documents based on triggers from your CRM, HCM, or internal systems. For example, trigger a contract send when an opportunity reaches a specific deal stage.
Integrating with custom tools: Connect GetAccept to proprietary applications, spreadsheet systems, or internal dashboards that don't have a pre-built connector.
Building custom reporting: Retrieve document engagement and signing metrics to build custom analytics dashboards aligned with your business intelligence tools.
Syncing data bidirectionally: Pull signed document data and recipient responses back to your systems of record to ensure all platforms have current information.
Pro-tip: Use GetAccept Automation to connect to 500+ platforms without writing code. If a pre-built connector exists for your tool, it may be faster than building a custom API integration.
Next Steps
For detailed API documentation, code examples, SDKs, and interactive endpoint testing, visit the GetAccept Developer Portal.
To set up webhooks for event-driven integrations (where GetAccept notifies your system when documents are sent or signed), see Webhook settings.
For workflow automation using pre-built connectors to 500+ platforms, refer to Getting Started with GetAccept Automation.
If you're looking to integrate GetAccept with an external service, explore available Integrations settings first to see if a pre-built connector is available.