eSignatures.io integration: operations for AI agents
eSignatures.io connects to Type.com as an integration. This page lists the 24 operations documented for Claude and Codex in Type.com: 7 read, 10 write, 7 destructive.
About eSignatures.io
eSignatures.io provides a platform for sending and signing mobile-friendly contracts over the web.
Categories: Documents & Forms
How to connect eSignatures.io to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
24 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
24 operations listed.
Contracts
- Read
Contracts - Query
Returns the contract details, including information about the signers and any values entered by the signers. Rate Limiting and Limited Data: It is important to avoid repeatedly 'polling' contract information through the API. We recommend using Webhook notifications to stay updated on contract statuses instead. Contracts older than two weeks may not return complete data in the response, and frequent polling can lead to blocked requests. To stay updated on contract statuses, we recommend using Webhook notifications. Documented Response field: Description: id: The unique ID for the contract.; status: Status of the contract: draft , sent , signed or withdrawn .; title: The unique title of the contract; metadata: Custom metadata attached to the contract request.; source: The origin of the contract, e.g., api , ui or zapier; test: Whether the contract is a test ( yes ); contract_pdf_url: When the contract is signed, the finalized PDF can be accessed via this url. Expires in 3 days following the request. (As part of the json response, this string will be JSON encoded, and simple copy paste of the URL won't work); labels: The Assigned list of labels. The Labels are shown on the Dashboard UI and they are searchable. They help with grouping the contracts.; signers: List of signers; signers:id: Unique ID for the signer.; signers:name: Name of the signer.; signers:email: Signer's email address.; signers:mobile: Signer's mobile number.; signers:company_name: Company name of the signer.; signers:sign_page_url: UniqueThe unique URL for the signer's signing page. This can be embedded in an iframe using embedded=yes .; signers:signer_field_values: Values provided by the signer for Signer fields, like Text fields, Dropdowns, or file uploads. These fields must be defined in the template editor..
GET /api/contracts/{contract_id} - Read
Contracts - Content - Query
Returns the content of the contract. Documented Response field: Description: contract_id: The unique ID of the contract.; markdown: Content of the contract in markdown format (see Extended markdown syntax below)..
GET /api/contracts/{contract_id}/content - Read
Contracts - Placeholder fields - Query
Returns the Placeholder field values currently assigned to the contract. Documented Response field: Description: placeholder_fields: placeholder_key: The placeholder key (without curly braces), e.g. interest_rate .; placeholder_fields: replace_with_text: Plain text used to replace the Placeholder field.; placeholder_fields: replace_with_markdown: Markdown content used to replace the Placeholder field.; placeholder_fields: replace_with_template: When the placeholder field specifies a template this endpoint always returns [template content].
GET /api/contracts/{contract_id}/placeholder_fields - Write
Contracts - New
This request generates a contract and, by default, sends it to the signers via the chosen communication channels to collect their signatures. Documented Parameter: Required: Description: template_id: yes: Specifies which template to use for the contract. The template_id is displayed when editing the template.; title: no: Unique title for the contract (defaults to template title if not specified). Visible in emails, documents, and dashboard pages.; locale: no: Language setting for the signer page and emails. Available locales are cz da de el en en-GB es fi fr hr hu id it ja nl no pl pt ro rs sk sl sv vi zh-CN zh-TW; metadata: no: Custom data that can be attached to the contract.; expires_in_hours: no: Sets the expiry time (in hours) for the contract.; custom_webhook_url: no: Custom URL for webhook notifications, overrides the default URL specified in your API settings.; assigned_user_email: no: Assigns one of your eSignatures.com users to manage the contract and receive notifications.; labels: no: Assigns specific labels to the contract. Labels are displayed on the dashboard and are searchable, making it easier to group contracts.; test: no: When yes , it marks the contract as a 'demo' with no fees charged for sending it.; save_as_draft: no: When yes , it saves the contract as a draft for further editing via the UI, instead of sending it.; signers: yes: List of individuals required to sign the contract.; signers: name: yes: Name of the signer.; signers: email: cond: Email address of the signer.; signers: mobile: cond: Mobile number of the signer. Non-US numbers must start with the country code, e.g., +61....; signers: company_name: no: Signer's company name.; signers: signing_order: no: Defines the sequence in which signers will receive the contract. Signers with the same number will be notified simultaneously.; signers: auto_sign: no: When yes , automatically adds the signer's signature to the document when set to yes . Only applicable for your own signature, not for clients.; signers: signature_request_delivery_methods: no: Defines how the signature request will be delivered (options: email , sms ). An empty list skips sending the request. Default is calculated.; signers: signed_document_delivery_method: no: Preferred delivery method for the signed document ( 'email' , 'sms' , '' ). Default is calculated. Note: Delivering the final document is legally required in most regions.; signers: multi_factor_authentications: no: Multi-factor authentication methods for signers (options: sms_verification_code , email_verification_code , photo_id ). Requires corresponding email/mobile contact details. Configurable on the Settings page: require MFA before open or before signing.; signers: redirect_url: no: URL where the signer will be redirected after signing.; placeholder_fields: no: Used to replace text placeholders in the template, e.g., {{interest_rate}}. Can be replaced with text or formatted content (see the Advanced placeholder fields section below).; placeholder_fields: placeholder_key: no: The key that corresponds to the placeholder text in the template, e.g., {{interest_rate}}.; placeholder_fields: replace_with_text: no: Text to replace the placeholder field.; placeholder_fields: replace_with_markdown: no: Markdown content to replace the placeholder field (see Extended markdown syntax for inserting Signer fields).; placeholder_fields: replace_with_template: no: Replace the Placeholder field with one of your template's full content.; signer_fields: no: Pre-fills fields that the signer must complete.; signer_fields: signer_field_id: no: The "Signer field ID" in the template editor for the given Signer input field.; signer_fields: default_value: no: Default value for the input field (Use 1 to tick radio buttons and checkboxes, YYYY-mm-dd for dates).; emails: signature_request_subject: no: The subject line of the email sent to collect signatures.; emails: signature_request_text: no: The body text of the email sent to signers. Use __FULL_NAME__ to insert the signer's name dynamically.; emails: final_contract_subject: no: The subject of the email sent with the final signed contract.; emails: final_contract_text: no: The body text of the email sent with the final signed contract. Use __FULL_NAME__ to insert the signer's name dynamically.; emails: cc_email_addresses: no: Email addresses to CC when sending the signed PDF contract.; emails: reply_to: no: Custom 'reply-to' address for emails (defaults to your support email if not specified).; custom_branding: no: Enables a fully branded signing flow, with a mandatory storage link retained in the PDF footer.; custom_branding: company_name: no: Custom company name displayed as the sender.; custom_branding: logo_url: no: Custom logo URL (recommended PNG size: 400px).. Documented Response field: Description: status: queued; contract:id: The unique ID for the contract.; contract:title: The unique title assigned to the contract.; contract:metadata: Custom metadata attached to the contract request.; contract:source: The origin of the contract, e.g., api , ui or zapier; contract:test: Whether the contract is a test ( yes ) or a live contract ( no ).; contract:signers:id: Unique ID for the signer.; contract:signers:name: Name of the signer.; contract:signers:email: Signer's email address.; contract:signers:mobile: Signer's mobile number.; contract:signers:company_name: Company name of the signer.; contract:signers:sign_page_url: The unique URL for the signer's signing page. It can be embedded in an iframe by appending embedded=yes . The link remains active until the contract expires. For additional identity verification, a 6-digit verification code is recommended..
POST /api/contracts - Write
Contracts - Send draft
Sends a draft contract to signers to collect their signatures. Only applicable to contracts with a status of draft . Note: POST /api/contracts can create and send a contract in one step, so a separate draft + send isn't required. Use this endpoint to send a contract already saved as a draft. Documented Response field: Description: status: 'queued'.
POST /api/contracts/{contract_id}/send_draft - Write
Contracts - PDF preview
Generates a PDF preview of the contract and sends a contract-pdf-generated Webhook notification with a direct URL to the PDF once it's ready. Documented Response field: Description: status: 'queued'.
POST /api/contracts/{contract_id}/generate_pdf_preview - Write
Contracts - Signers - Add
Signers can be added to contracts using this API endpoint. Note: Adding a new signer does not automatically send an email with the contract. Documented Parameter: Required: Description: name: no: Name of the signer; email: no: Email address of the signer; mobile: no: Mobile number of the signer. Non-US mobile numbers must start with the country code, eg +44....; company_name: no: Company name for the signer; signature_request_delivery_methods: no: Defines how the signature request will be delivered (options: email , sms ). An empty list skips sending the request. Default is calculated.; signed_document_delivery_method: no: Preferred delivery method for the signed document ( email , sms ). Delivery is legally required in most regions. Default is calculated.; multi_factor_authentications: no: Multi-factor authentication methods for signers (options: sms_verification_code , email_verification_code , photo_id ). Requires corresponding email/mobile contact details. Configurable on the Settings page: require MFA before open or before signing.; redirect_url: no: URL where the signer will be redirected after signing.. Documented Response field: Description: status: 'success'.
POST /api/contracts/{contract_id}/signers - Write
Contracts - Signers - Update
The contact details of a signer can be updated through this API request. Note: The contract is not automatically emailed when the signer's information is updated. Documented Parameter: Required: Description: name: no: Name of the signer; email: no: Email address of the signer; mobile: no: Mobile number of the signer. Non-US mobile numbers must start with the country code, eg +44....; company_name: no: Company name for the signer; signature_request_delivery_methods: no: Defines how the signature request will be delivered (options: email , sms ). An empty list skips sending the request. Default is calculated.; signed_document_delivery_method: no: Preferred delivery method for the signed document ( email , sms ). Delivery is legally required in most regions. Default is calculated.; multi_factor_authentications: no: Multi-factor authentication methods for signers (options: sms_verification_code , email_verification_code , photo_id ). Requires corresponding email/mobile contact details.; redirect_url: no: URL where the signer will be redirected after signing.. Documented Response field: Description: status: 'updated'.
POST /api/contracts/{contract_id}/signers/{signer_id} - Write
Contracts - Signers - Resend sign request
Documented Response field: Description: status: 'queued'.
POST /api/contracts/{contract_id}/signers/{signer_id}/send_contract - Destructive
Contracts - Withdraw
Withdrawn contracts can no longer be signed, and signed contracts cannot be withdrawn. Withdrawing a contract does not delete any related information; the contract details can still be queried. Documented Response field: Description: status: 'withdrawn'.
POST /api/contracts/{contract_id}/withdraw - Destructive
Contracts - Content - Update
Updates the contract content. Documented Parameter: Required: Description: dry_run: no: When yes , performs a dry run (no changes are saved).; edits: yes: List of Markdown edit operations applied to the contract content. Each edit finds existing content and replaces it with new Markdown.; edits:find_markdown: yes: Markdown content to find. By default this matches text literally, including line breaks, so only the exact text you provide is replaced (e.g. 'including weekends' replaces just that phrase). As a special case, if the value is exactly a heading followed by a trailing newline (e.g. '## Payment Terms\n'), the match expands to that heading plus all content beneath it up to the next heading, replacing the whole section. Set to blank ('') to replace the entire contract content.; edits:replace_with_markdown: yes: Markdown content to insert in place of the matched content. Set to blank ( "" ) to remove the matched content..
POST /api/contracts/{contract_id}/content - Destructive
Contracts - Signers - Delete
Documented Response field: Description: status: 'queued'.
POST /api/contracts/{contract_id}/signers/{signer_id}/delete - Destructive
Contracts - Placeholder fields - Update
Updates the Placeholder field values for an unsigned contract. Only the Placeholder fields included in the request are updated. Each Placeholder field can be replaced with plain text, Markdown content, or the full content of one of your templates. Documented Parameter: Required: Description: placeholder_fields: yes: List of Placeholder fields to update.; placeholder_fields: placeholder_key: yes: The key that corresponds to the placeholder text in the template, e.g. {{interest_rate}} .; placeholder_fields: replace_with_text: no: Plain text to replace the Placeholder field.; placeholder_fields: replace_with_markdown: no: Markdown content to replace the Placeholder field.; placeholder_fields: replace_with_template: no: Template ID of the template whose full content should replace the Placeholder field.. Documented Response field: Description: status: updated.
POST /api/contracts/{contract_id}/placeholder_fields
Templates
- Read
Templates - Query
Returns the details of a specific template, including the Placeholder fields and signer fields. Documented Response field: Description: template_id: The unique ID of the template.; title: The title of the template.; created_at: The date and time the template was created.; placeholder_fields: List of Placeholder fields in the template.; signer_field_ids: List of the Signer field ID-s assigned to Signer fields in the template..
GET /api/templates/{template_id} - Read
Templates - List
Returns a list of available templates. Documented Response field: Description: template_id: The unique ID of the template.; title: The title of the template..
GET /api/templates - Read
Templates - Content - Query
Returns the content of the template. Documented Response field: Description: template_id: The unique ID of the template.; markdown: Content of the template in markdown format (see Extended markdown syntax below)..
GET /api/templates/{template_id}/content - Read
Templates - Collaborators - List
Returns the list of Collaborators. Documented Response field: Description: template_collaborator_id: The ID of the collaborator; template_id: The ID of the template; name: The name of the collaborator; email: The email address of the collaborator; template_collaborator_editor_url: URL to access the template editor (can be embedded into an iframe using the embedded=yes parameter)..
GET /api/templates/{template_id}/collaborators - Write
Templates - New
Creates a new template. Documented Parameter: Required: Description: title: yes: The title of the new template.; markdown: yes: Defines the content of the new template (see Extended markdown syntax for inserting Signer fields).; labels: no: Optional labels assigned to the template and its contracts. Labels help organize and group templates and contracts..
POST /api/templates - Write
Templates - Update
Updates the template. Documented Parameter: Required: Description: title: no: The title the new template.; labels: no: Optional labels assigned to the template and its contracts. Labels help organize and group templates and contracts..
POST /api/templates/{template_id} - Write
Templates - Duplicate (and customize)
Duplicates an existing template and allows for content customization using Placeholder fields. Documented Parameter: Required: Description: title: yes: The title for the new template.; placeholder_fields: no: Customizes the content of the new template by replacing Placeholder fields from the source template.; placeholder_fields: placeholder_key: no: The placeholder_key is the text between the curly brackets in the source contract template. Eg: {{business_name}}; placeholder_fields: replace_with_text: no: Replace the Placeholder field in the new template with simple text.; placeholder_fields: replace_with_markdown: no: Markdown content to replace the placeholder field within the original template (see Extended markdown syntax for inserting Signer fields).; placeholder_fields: replace_with_template: no: Replace the Placeholder field in the new template with one of your existing template's full content.; target_secret_token: no: The API Secret token of another account, if the new template should be assigned to that other account..
POST /api/templates/{template_id}/duplicate - Write
Templates - Collaborators - Add
Adds a collaborator who can edit the template. The link to the editor can be used as a standalone page, or it can be embedded into an iframe by adding the embedded=yes URL parameter. Documented Parameter: Required: Description: name: no: The name of the collaborator; email: no: The email of the collaborator. Email invitation is sent when provided.. Documented Response field: Description: template_collaborator_id: The ID of the collaborator; template_id: The ID of the template; name: The name of the collaborator; email: The email of the collaborator; template_collaborator_editor_url: URL to access the template editor (can be embedded into an iframe using the embedded=yes parameter)..
POST /api/templates/{template_id}/collaborators - Destructive
Templates - Delete
Deletes the template.
POST /api/templates/{template_id}/delete - Destructive
Templates - Content - Update
Updates the template content. Documented Parameter: Required: Description: dry_run: no: When yes , performs a dry run (no changes are saved).; edits: yes: List of Markdown edit operations applied to the template content. Each edit finds existing content and replaces it with new Markdown.; edits:find_markdown: yes: Markdown content to find. By default this matches text literally, including line breaks, so only the exact text you provide is replaced (e.g. 'including weekends' replaces just that phrase). As a special case, if the value is exactly a heading followed by a trailing newline (e.g. '## Payment Terms\n'), the match expands to that heading plus all content beneath it up to the next heading, replacing the whole section. Set to blank ('') to replace the entire contract content.; edits:replace_with_markdown: yes: Markdown content to insert in place of the matched content. Set to blank ( "" ) to remove the matched content..
POST /api/templates/{template_id}/content - Destructive
Templates - Collaborators - Remove
Removes the collaborator's permission to edit the template.
POST /api/templates/{template_id}/collaborators/{template_collaborator_id}/remove
No operations match.
See How connections work for access and permissions, or browse all integrations.