Integration

GetAccept integration

GetAccept is a sales document and e-signature platform. Create documents from templates or uploaded files, send them for signature (GetAccept emails real recipients and a signature can be legally binding), forward, remind, recall or delete them, fill fields, and read status, recipients, events, audit log, page tracking, pricing tables and comments; manage webhook subscriptions, contacts, products and document custom data; read templates, users, teams, folders, videos and statistics. Not exposed: recipients' personal signing links, sealing and sending to chosen recipients, manual signing, revisions and versions, previews, pricing-table edits, attachment, video and archive uploads, email and communication templates, entity custom data settings, knowledge bases, user and team administration, sessions, devices and subscription test deliveries. Authentication is OAuth 2.0 (authorization code); GetAccept API support issues the OAuth client, and commercial use needs a GetAccept API package.

Connect GetAccept How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in GetAccept.Built from the 66 GetAccept tools below, on the connection you add once.

What you can do with GetAccept

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Custom data, 5 operations

add_document_custom_dataAdd document custom dataPOSTAdd a custom data property to a document. The property must already be defined in the entity custom data settings. Custom data properties capture information that the default document properties do not cover.
delete_document_custom_dataDelete document custom dataDELETEDelete a custom data property from a document. The property is no longer available for the document. A `customDataId` that names no custom data property of the document also returns 204.
get_document_custom_dataGet document custom dataGETReturns one custom data property of a document: its key, value_type (string, number, boolean or setValues), value and localized names.
list_document_custom_dataList document custom dataGETGet all custom data properties for a document. Properties inherited from the template when the document was created are included; properties added to the template afterwards do not appear on documents that already exist.
update_document_custom_dataUpdate document custom dataPUTSets a new value for a custom data property of a document; the value must match the property's type.

Document, 5 operations

create_documentCreate documentPOSTCreates a document for e-signature from a template, uploaded files or a file URL, with its recipients. It stays a draft until send_document, unless is_automatic_sending is true: GetAccept then emails the recipients, now or at scheduled_sending_time.
get_documentGet documentGETReturns one document: status, value, type, tags, recipients with their status, sender, dates, settings and, on request, pages, statistics and attachments.
list_documentsList documentsGETLists documents (contracts and proposals sent for e-signature) with sort, owner scope, external id and status filters such as signed, active, expired or won: name, status, value, recipients, owner and dates.
recall_or_delete_documentRecall or delete documentDELETERecalls a sent document (it stays, with status recalled), or permanently deletes one that was never sent or is already recalled. Deleting a sent document takes two calls; the delete cannot be undone.
update_documentUpdate documentPUTUpdates a document. A draft accepts external_id, is_private, value, sign_redirect and block_recipient_invite; past draft it accepts value, contract dates, tags, is_private, sign_redirect and block_recipient_invite. Anything else is refused.

Subscription, 5 operations

create_subscriptionCreate subscriptionPOSTCreates a webhook subscription: GetAccept will POST the chosen event (document signed, viewed, sent...) to target_url. event is required here: without it GetAccept would delete a global subscription.
delete_subscriptionDelete subscriptionDELETEDelete a single subscription. Only admin users may delete a global subscription.
get_subscriptionGet subscriptionGETReturns one webhook subscription (as a one-element list, empty when the id is unknown): id, event, status, host label and global flag. Target URL and payload are not returned.
list_subscriptionsList subscriptionsGETLists webhook subscriptions visible to the user (their own and the entity's global ones): id, event, status (1 active, -1 disabled), host label and global flag. Target URL and payload are not returned.
update_subscriptionUpdate subscriptionPATCHReplaces a webhook subscription and sets it active: send event, target_url and every field to keep. Left out, global becomes false (a global one turns personal), payload and notification_email are cleared. Admins only for global ones.

Product, 4 operations

create_productCreate productPOSTCreates a product in the product library (name, description, SKU, price, tax, currency and locale) for use in pricing tables. Returns the product.
delete_productDelete productDELETEThis call will delete an existing product from your product library. Deleted products are permanently removed from the product library and can no longer be used in pricing tables.
list_productsList productsGETThis call will return a list of products for your entity. You can filter, sort, and paginate the results using query parameters. The `description` field and text-type `product_property_fields` values are returned as markdown.
update_productUpdate productPUTThis call will update an existing product. All fields are optional, so only provide the fields you want to update.

Contact, 3 operations

create_contactCreate contactPOSTCreates a contact for reuse as a document recipient; email or mobile is required. Returns the contact id.
delete_contactDelete contactDELETEDeletes a contact from the entity's contact list.
list_contactsList contactsGETLists the entity's contacts (people saved as recipients) with search, status filter, sort and paging: name, email, mobile, phone, company and title. Personal data.

Field, 3 operations

list_document_fieldsList document fieldsGETGet a list of fields for a document or template. Can be used both before and after a document has been signed.
list_template_fieldsList template fieldsGETGet a list of fields for a template.
populate_document_fieldsPopulate document fieldsPUTUpdate fields in a document. Each field is identified by either `id` or `name`, and the two cannot be mixed in the same request. Fields can no longer be populated once a recipient has signed or approved the document.

User, 3 operations

get_userGet userGETReturns one user of the entity: name, email, phone, title, role, status, teams, language and time zone.
list_team_usersList team usersGETGet a list of the users in a specific team. Only admin users can view team users.
list_usersList usersGETGet a list of users for the authenticated entity, including pending and inactive users. Inactive users are listed after users with other statuses.

Attachment, 2 operations

list_attachmentsList attachmentsGETLists the attachment library of the entity (files and links that can be added to documents in create_document attachments): id, title, type, description and URL.
list_document_attachmentsList document attachmentsGETLists the attachments of a document or template: title, type, description, file or external URL, and which recipients can access them.

Comment, 2 operations

create_document_commentCreate document commentPOSTPosts a message in the document's chat as the authenticated user (the chat is shared with the document's recipients) and returns the comment id.
list_document_commentsList document commentsGETLists the chat comments of a document with the sender of each (name, email) and its text and time.

Event, 2 operations

list_document_eventsList document eventsGETLists the events of a document (sent, viewed, signed, rejected...) with the person, their company and the time; a rejection carries the reason given. Personal data.
list_subscription_eventsList subscription eventsGETRetrieve every `document.*` event that can be subscribed to. Each entry carries the `value` to pass as `event` when creating a subscription and a human-readable `name`. The `comment.*` events are also valid `event` values but are not listed here.

Folder, 2 operations

get_folderGet folderGETUse a folder id to show the current path and, for a template folder, its subfolders. An archive folder returns only its path.
list_foldersList foldersGETYou can list and get details of existing folders in GetAccept. Folders are used to structure archived documents and templates. This call returns only top-level folders: the top-level folders of the template library and the root archive folder.

Latest, 2 operations

get_latest_documentGet latest documentGETReturns the most recent document of the entity, of any status, or the latest signed one with filter=signed: status, value, recipients, sender and dates.
list_latest_commentsList latest commentsGETLists the most recent chat comment of each document, newest first, with the document and the commenter's name and email.

Recipient, 2 operations

list_document_recipientsList document recipientsGETLists the recipients of a document: name, email, mobile, role (signer, approver or cc), status, company, title and signing order. Their personal signing links are not returned.
recall_document_signerRecall document signerDELETERecalls a signer: their role becomes cc, so they can only view the document. A recipient who already signed cannot be recalled, and recalling the last signer still to sign completes the document as signed.

Statistic, 2 operations

get_my_statisticsGet my statisticsGETReturns the authenticated user's document statistics for the current and previous period: sent, active, signed, won, expired and hot documents, hit rate, estimated value and deal time.
get_user_statisticsGet user statisticsGETGet statistics for the user `{id}`. Every figure except `performers`, which ranks the top users of the whole entity, covers only documents owned by `{id}`.

Template, 2 operations

get_templateGet templateGETReturns one template: name, type, value, tags, owner, settings and dates.
list_templatesList templatesGETLists document templates of the root folder, of one folder (folder_id) or of all folders (showall=true): id, name, type, tags, owner, and page, field and role counts.

Video, 2 operations

get_videoGet videoGETGet a specific video based on its video id.
list_videosList videosGETGet the videos of the entity that the authenticated user owns or that are published, newest first.

Document type, 1 operation

list_document_typesList document typesGETGet every document type, also called contract type, configured for the entity of the authenticated user, active and inactive. Pass an active type's `type` when you create a document.

Download, 1 operation

download_documentDownload documentGETReturns a temporary download URL for the document's PDF, best once it is signed. The URL of a signed document expires after 1 hour, of other documents after 5 minutes.

Expiration, 1 operation

update_document_expirationUpdate document expirationPOSTSets a new expiration date (in the future) for a document, and optionally notifies its recipients.

External, 1 operation

get_document_by_external_idGet document by external idGETReturns the document created with a given external id (your own reference, such as a CRM deal id): status, value, recipients, sender and dates.

Forward, 1 operation

forward_documentForward documentPOSTForwards a document to a new person by email or mobile number: they are added as a CC recipient, or receive a signer's signature rights when transfer is true.

Log, 1 operation

list_document_logList document logGETReturns the detailed audit log of a document: each action with the person's name and email, device or reason, and the IP address, city and country it came from. Personal data.

Lost, 1 operation

mark_document_as_lostMark document as lostPOSTMarks a document as lost (a deal not won): its status becomes lost. Calling it again on a lost document has no effect.

Me, 1 operation

get_current_userGet current userGETGet the details of the authenticated user, including the entities the user has access to.

Notification, 1 operation

list_notificationsList notificationsGETList notifications for the current user. Returns an empty array when the user has no documents or no notifications match the request.

Page, 1 operation

list_document_pagesList document pagesGETGet a list of pages for a document. Can be used both before and after a document has been sent or signed.

Pricing table, 1 operation

list_document_pricing_tablesList document pricing tablesGETReturns the pricing tables of a document: name, sections with their rows, currency settings and summary totals.

Property, 1 operation

list_product_propertiesList product propertiesGETThis call will return a list of product properties for your entity. Product properties are custom fields that can be assigned to products.

Reminder, 1 operation

send_document_reminderSend document reminderPOSTSends a reminder now to recipients of a sent document: an email to the recipient_ids given or to those who have not opened or not signed it, an SMS with text, or a video (video_id). An email with no ids and no filter reminds nobody.

Role, 1 operation

list_template_rolesList template rolesGETLists the recipient roles of a template (such as Customer or Sales rep) with their ids and default contact details; pass a role id or name per recipient in create_document.

Send, 1 operation

send_documentSend documentPOSTSends a draft document: GetAccept emails every recipient a unique link to view and sign it, which can be legally binding. Sending is asynchronous; get_document_status says when it is sent.

Status, 1 operation

get_document_statusGet document statusGETGet the current status of a document. `rejection_reason` is the reason the recipient gave when rejecting the document; it is `null` when the document is not rejected or no reason was given.

Tag, 1 operation

list_tagsList tagsGETGet every tag defined for the entity of the authenticated user. Responds with `204 No Content` when the entity has no tags.

Team, 1 operation

list_teamsList teamsGETGet a list of the current teams for the entity. Teams with no members are not listed, so an entity whose teams are all empty returns 204 with no body.

Tracking, 1 operation

list_document_page_trackingList document page trackingGETGet the time each recipient has spent on every page of a document, in seconds. The page level `page_time` is the total across all recipients, and `recipients` breaks it down per recipient.

Upload, 1 operation

upload_fileUpload filePOSTUploads one file (a stored file, or a public URL GetAccept downloads), max 20 MB, and returns a file_id for create_document file_ids. Files expire after 48 hours and are deleted once used.

Use GetAccept from Claude Code, Cursor or Codex

Connect GetAccept in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its GetAccept operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect GetAccept

Create your workspace
Sign up free. Nothing to install.
Connect GetAccept once
Add your GetAccept connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.