# Firma

## Docs

- [Get company information](https://docs.firma.dev/api-reference/v01.16.00/company/get-company-information.md): Retrieve information about the authenticated company
- [Partially update company information](https://docs.firma.dev/api-reference/v01.16.00/company/partially-update-company-information.md): Update specific company fields. Only provided fields will be updated. At least one field must be provided.
- [Update company information](https://docs.firma.dev/api-reference/v01.16.00/company/update-company-information.md): Update all company details. This is a full replacement operation requiring all fields except icon_url.
- [Create signing request custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/create-signing-request-custom-field.md): Create a new custom field definition for a signing request
- [Create template custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/create-template-custom-field.md): Create a new custom field definition for a template
- [Create workspace custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/create-workspace-custom-field.md): Create a new custom field definition for a workspace
- [Delete signing request custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/delete-signing-request-custom-field.md): Soft-delete a custom field definition from a signing request
- [Delete template custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/delete-template-custom-field.md): Soft-delete a custom field definition from a template
- [Delete workspace custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/delete-workspace-custom-field.md): Soft-delete a custom field definition
- [List signing request custom fields](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/list-signing-request-custom-fields.md): Get all custom field definitions for a signing request
- [List template custom fields](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/list-template-custom-fields.md): Get all custom field definitions for a template
- [List workspace custom fields](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/list-workspace-custom-fields.md): Get all custom field definitions for a workspace
- [Update workspace custom field](https://docs.firma.dev/api-reference/v01.16.00/custom-fields/update-workspace-custom-field.md): Update an existing custom field definition
- [Add company domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/add-company-domain.md): Add a new email domain for the company. This initiates the domain verification process. After creation, you must: 1. Add a TXT record to your DNS with the verification token 2. Call POST /company/domains/{id}/verify-ownership to verify domain ownership 3. Call POST /company/domains/{id}/finalize to…
- [Add workspace domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/add-workspace-domain.md): Add a new email domain for a specific workspace. This initiates the domain verification process. After creation, you must: 1. Add a TXT record to your DNS with the verification token 2. Call POST /workspace/{workspace_id}/domains/{id}/verify-ownership to verify domain ownership 3. Call POST /workspa…
- [Delete company domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/delete-company-domain.md): Remove a domain from the company. Cannot delete the primary domain if it's the only domain.
- [Delete workspace domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/delete-workspace-domain.md): Remove a domain from the workspace. Cannot delete the primary domain if it's the only domain.
- [Finalize domain setup](https://docs.firma.dev/api-reference/v01.16.00/email-domains/finalize-domain-setup.md): Finalize domain setup by registering with the email provider. This returns the DNS records (SPF, DKIM, DMARC) that must be added to enable email sending. Can only be called after domain ownership is verified.
- [Finalize workspace domain setup](https://docs.firma.dev/api-reference/v01.16.00/email-domains/finalize-workspace-domain-setup.md): Finalize domain setup by registering with the email provider. This returns the DNS records (SPF, DKIM, DMARC) that must be added to enable email sending. Can only be called after domain ownership is verified.
- [Get company domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/get-company-domain.md): Retrieve details of a specific company domain including verification status and DNS records
- [Get workspace domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/get-workspace-domain.md): Retrieve details of a specific domain in a workspace including verification status and DNS records
- [List company domains](https://docs.firma.dev/api-reference/v01.16.00/email-domains/list-company-domains.md): List all email domains configured for the company (domains on the protected/default workspace). These domains are used as the default sending domain for all workspaces.
- [List workspace domains](https://docs.firma.dev/api-reference/v01.16.00/email-domains/list-workspace-domains.md): List all email domains configured for a specific workspace. These domains are used for sending signing request emails from this workspace.
- [Set primary domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/set-primary-domain.md): Set a domain as the primary sending domain for the company. Only fully verified domains (domain_status=1) can be set as primary.
- [Set primary workspace domain](https://docs.firma.dev/api-reference/v01.16.00/email-domains/set-primary-workspace-domain.md): Set a domain as the primary sending domain for the workspace. Only fully verified domains (domain_status=1) can be set as primary.
- [Verify DNS records](https://docs.firma.dev/api-reference/v01.16.00/email-domains/verify-dns-records.md): Verify that all required DNS records (SPF, DKIM, DMARC) are properly configured. Call this after adding all DNS records from the finalize step. Once verified, the domain is ready for sending emails.
- [Verify domain ownership](https://docs.firma.dev/api-reference/v01.16.00/email-domains/verify-domain-ownership.md): Verify domain ownership by checking the TXT record. Call this after adding the verification TXT record to your DNS. DNS propagation may take up to 48 hours, but typically completes within minutes.
- [Verify workspace domain DNS records](https://docs.firma.dev/api-reference/v01.16.00/email-domains/verify-workspace-domain-dns-records.md): Verify that all required DNS records (SPF, DKIM, DMARC) are properly configured. Call this after adding all DNS records from the finalize step. Once verified, the domain is ready for sending emails.
- [Verify workspace domain ownership](https://docs.firma.dev/api-reference/v01.16.00/email-domains/verify-workspace-domain-ownership.md): Verify domain ownership by checking the TXT record. Call this after adding the verification TXT record to your DNS. DNS propagation may take up to 48 hours, but typically completes within minutes.
- [Create or update company email template](https://docs.firma.dev/api-reference/v01.16.00/email-templates/create-or-update-company-email-template.md): Create or update a company-level email template for a specific type. Company templates are used as defaults for workspaces without workspace-specific templates.
- [Create or update workspace email template](https://docs.firma.dev/api-reference/v01.16.00/email-templates/create-or-update-workspace-email-template.md): Create or update a custom email template for a specific type. If a template already exists for this type, it will be updated. A warning is returned if the template body does not contain {{signing_link}}.
- [Delete company email template](https://docs.firma.dev/api-reference/v01.16.00/email-templates/delete-company-email-template.md): Delete a company-level email template. Workspaces will fall back to the built-in default template for this type.
- [Delete workspace email template](https://docs.firma.dev/api-reference/v01.16.00/email-templates/delete-workspace-email-template.md): Delete a custom email template. The workspace will revert to using the company-level or default template for this type.
- [Get default email templates](https://docs.firma.dev/api-reference/v01.16.00/email-templates/get-default-email-templates.md): Retrieve the built-in default email templates for a specific language. These are the templates used when no custom company or workspace templates are configured.
- [Get email template placeholders](https://docs.firma.dev/api-reference/v01.16.00/email-templates/get-email-template-placeholders.md): Retrieve the list of available placeholders that can be used in email templates. Placeholders are replaced with actual values when emails are sent.
- [Get workspace email template](https://docs.firma.dev/api-reference/v01.16.00/email-templates/get-workspace-email-template.md): Retrieve a specific email template by type for a workspace
- [List company email templates](https://docs.firma.dev/api-reference/v01.16.00/email-templates/list-company-email-templates.md): Retrieve all custom email templates at the company level. Company templates serve as defaults for all workspaces that don't have workspace-specific templates.
- [List workspace email templates](https://docs.firma.dev/api-reference/v01.16.00/email-templates/list-workspace-email-templates.md): Retrieve all custom email templates for a workspace
- [Generate JWT token for embedding templates](https://docs.firma.dev/api-reference/v01.16.00/jwt-management/generate-jwt-token-for-embedding-templates.md): Creates a JWT token for embedding a template with 24-hour expiration. This is the standard endpoint for JWT generation.
- [Generate JWT token for signing request](https://docs.firma.dev/api-reference/v01.16.00/jwt-management/generate-jwt-token-for-signing-request.md): Generate a JWT token for embedding a signing request editor. JWT expires after 7 days.
- [Revoke a signing request JWT token](https://docs.firma.dev/api-reference/v01.16.00/jwt-management/revoke-a-signing-request-jwt-token.md): Revoke a previously generated JWT token for a signing request, preventing it from being used for embedded editing
- [Revoke Template JWT Token](https://docs.firma.dev/api-reference/v01.16.00/jwt-management/revoke-template-jwt-token.md): Revoke a previously generated JWT token, preventing it from being used for template embedding. This is the standard endpoint for revoking template JWTs.
- [Create document (Legacy)](https://docs.firma.dev/api-reference/v01.16.00/legacy/create-document-legacy.md): **DEPRECATED**: Use `/signing-requests` instead. Legacy endpoint for creating a new signing request.
- [List documents legacy](https://docs.firma.dev/api-reference/v01.16.00/legacy/list-documents-legacy.md)
- [Cancel a signing request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/cancel-a-signing-request.md): Cancels a signing request that hasn't been completed yet. Can only cancel requests that have been sent and are not already finished or cancelled.
- [Comprehensive Update Signing Request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/comprehensive-update-signing-request.md): Perform comprehensive updates to a signing request including properties, recipients, fields, and reminders. Cannot update after signing request has been sent, completed, or cancelled. All sections are optional but at least one must be provided.
- [Create and Send Signing Request (Atomic)](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/create-and-send-signing-request-atomic.md): Create and immediately send a signing request in a single atomic operation. This endpoint combines the functionality of POST /signing-requests and POST /signing-requests/{id}/send.
- [Create Signing Request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/create-signing-request.md): Create a new signing request either from a PDF document (document-based) or from an existing template (template-based). For document-based creation, allow_editing_before_sending is automatically set to true. For template-based creation, properties are inherited from the template and can be overridde…
- [Download Signing Request Document](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/download-signing-request.md): Retrieve a download URL for a signing request's signed document. For completed signing requests, returns the final signed PDF. For in-progress signing requests where partial download is enabled, returns a URL to the partially-signed document generated at the time of the last signer's completion.
- [Get embedded signing request data (JWT authenticated)](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-embedded-signing-request-data-jwt-authenticated.md): Retrieve signing request data when using embedded editor. Requires JWT authentication obtained from `/jwt/generate-signing-request`. Returns the complete signing request including fields, recipients, and reminders.
- [Get Signing Request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-signing-request.md): Retrieve a specific signing request by ID
- [Get signing request audit trail](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-signing-request-audit-trail.md): Retrieve the complete audit trail for a signing request, combining admin actions (created, edited, sent, cancelled) and signer actions (viewed, signed, declined, downloaded). Events are sorted chronologically.
- [Get signing request fields](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-signing-request-fields.md): Retrieve all fields for a specific signing request with their values
- [Get signing request reminders](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-signing-request-reminders.md): Retrieve all reminders scheduled for a specific signing request
- [Get signing request users](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/get-signing-request-users.md): Retrieve all recipients/users for a specific signing request
- [List Signing Requests](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/list-signing-requests.md): Retrieve a paginated list of signing requests
- [Partially Update Signing Request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/partially-update-signing-request.md): Update signing request properties, a single recipient, OR a single field. Cannot update multiple entity types in one request. Cannot update after signing request has been sent, completed, or cancelled.
- [Resend signing request to specific recipients](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/resend-signing-request-to-specific-recipients.md): Resends signing request notifications to one or more recipients who are currently eligible to sign. For requests with signing order enabled, can only resend to recipients at the current active order. Cannot resend to recipients who have already signed.
- [Save embedded signing request (JWT authenticated)](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/save-embedded-signing-request-jwt-authenticated.md): Save changes to a signing request when using embedded editor. Requires JWT authentication obtained from `/jwt/generate-signing-request`.
- [Send embedded signing request (JWT authenticated)](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/send-embedded-signing-request-jwt-authenticated.md): Send a signing request to recipients when using embedded editor. Requires JWT authentication obtained from `/jwt/generate-signing-request`. The signing request must have at least one recipient and all required fields must be configured.
- [Send signing request](https://docs.firma.dev/api-reference/v01.16.00/signing-requests/send-signing-request.md): Send a signing request to all recipients via email. This triggers email delivery and sets the sent_on timestamp.
- [Comprehensive Template Update](https://docs.firma.dev/api-reference/v01.16.00/templates/comprehensive-template-update.md): Comprehensive update of template including properties, users, fields, and reminders. Supports user deletion with field reassignment or deletion. All sections are optional but at least one must be provided.
- [Create Template](https://docs.firma.dev/api-reference/v01.16.00/templates/create-template.md): Create a new template with a base64-encoded PDF document. The API automatically extracts the page count from the document.
- [Delete a template](https://docs.firma.dev/api-reference/v01.16.00/templates/delete-a-template.md): Soft delete a template by ID. This marks the template as deleted but retains the data.
- [Duplicate template into signing request](https://docs.firma.dev/api-reference/v01.16.00/templates/duplicate-template-into-signing-request.md): Creates a new signing request by duplicating an existing template, including all fields, users, reminders, and settings.
- [Get Template](https://docs.firma.dev/api-reference/v01.16.00/templates/get-template.md): Retrieve a specific template by ID
- [Get template fields](https://docs.firma.dev/api-reference/v01.16.00/templates/get-template-fields.md): Retrieve all fields configured for a specific template
- [Get template reminders](https://docs.firma.dev/api-reference/v01.16.00/templates/get-template-reminders.md): Retrieve all reminders configured for a specific template
- [Get template users](https://docs.firma.dev/api-reference/v01.16.00/templates/get-template-users.md): Retrieve all recipients/users associated with a specific template
- [List Templates](https://docs.firma.dev/api-reference/v01.16.00/templates/list-templates.md): Retrieve a paginated list of templates
- [Partially Update Template](https://docs.firma.dev/api-reference/v01.16.00/templates/partially-update-template.md): Update template properties, a single user, OR a single field. Cannot mix multiple entity types in one request. Use PUT for comprehensive updates including users, fields, and reminders.
- [Replace template document](https://docs.firma.dev/api-reference/v01.16.00/templates/replace-template-document.md): Replaces the PDF document of an existing template while preserving all field placements. The replacement document must have the same page count and matching page dimensions (within 1pt tolerance) as the original.
- [Create Webhook](https://docs.firma.dev/api-reference/v01.16.00/webhooks/create-webhook.md): Create a new webhook
- [Delete a webhook](https://docs.firma.dev/api-reference/v01.16.00/webhooks/delete-a-webhook.md): Soft delete a webhook by ID. This marks the webhook as deleted but retains the data.
- [Get Webhook](https://docs.firma.dev/api-reference/v01.16.00/webhooks/get-webhook.md): Retrieve a specific webhook by ID
- [Get webhook secret rotation status](https://docs.firma.dev/api-reference/v01.16.00/webhooks/get-webhook-secret-rotation-status.md): Returns information about the current webhook secret including rotation status and expiry of old secret if applicable.
- [Get Workspace Webhook Secret Status](https://docs.firma.dev/api-reference/v01.16.00/webhooks/get-workspace-webhook-secret-status.md): Returns the status of a workspace webhook secret including creation date, rotation date, and grace period status.
- [List Webhooks](https://docs.firma.dev/api-reference/v01.16.00/webhooks/list-webhooks.md): Retrieve a paginated list of webhooks
- [Rotate webhook signing secret](https://docs.firma.dev/api-reference/v01.16.00/webhooks/rotate-webhook-signing-secret.md): Generates a new webhook signing secret for the company. The old secret remains valid for 7 days to allow graceful migration. Rate limited to 1 request per minute.
- [Rotate Workspace Webhook Secret](https://docs.firma.dev/api-reference/v01.16.00/webhooks/rotate-workspace-webhook-secret.md): Generates a new webhook signing secret for a workspace. The old secret remains valid for 7 days.
- [Test a webhook](https://docs.firma.dev/api-reference/v01.16.00/webhooks/test-a-webhook.md): Send a test payload to the webhook URL to verify it's working correctly
- [Update Webhook](https://docs.firma.dev/api-reference/v01.16.00/webhooks/update-webhook.md): Update an existing webhook
- [Get workspace settings](https://docs.firma.dev/api-reference/v01.16.00/workspace-settings/get-workspace-settings.md): Retrieve workspace settings
- [Update workspace settings](https://docs.firma.dev/api-reference/v01.16.00/workspace-settings/update-workspace-settings.md): Update workspace settings
- [Create a new workspace](https://docs.firma.dev/api-reference/v01.16.00/workspaces/create-a-new-workspace.md): Create a new workspace for the authenticated company. All workspaces are created as non-protected by default. The protected status can only be set during company account creation.
- [Expire pending API keys](https://docs.firma.dev/api-reference/v01.16.00/workspaces/expire-pending-api-keys.md): Immediately expires all pending API keys (those with expires_at set) for a workspace. Useful after verifying that the new key works correctly. Cannot be used on protected workspaces. Rate limited to 1 request per minute.
- [Get a workspace](https://docs.firma.dev/api-reference/v01.16.00/workspaces/get-a-workspace.md): Retrieve a specific workspace by ID including its API key
- [List workspaces](https://docs.firma.dev/api-reference/v01.16.00/workspaces/list-workspaces.md): Retrieve a paginated list of workspaces for the authenticated company
- [Partially update a workspace](https://docs.firma.dev/api-reference/v01.16.00/workspaces/partially-update-a-workspace.md): Update specific workspace fields. Only the name can be updated via API. The protected field is read-only and can only be set during company account creation.
- [Regenerate workspace API key](https://docs.firma.dev/api-reference/v01.16.00/workspaces/regenerate-workspace-api-key.md): Regenerates the API key for a workspace. Sets 24-hour expiration on existing active keys and creates a new key. Cannot be used on protected workspaces. Rate limited to 1 request per minute.
- [Update a workspace](https://docs.firma.dev/api-reference/v01.16.00/workspaces/update-a-workspace.md): Update an existing workspace's information. This is a full replacement operation requiring the name field.
- [API Changelog](https://docs.firma.dev/guides/api-changelog.md): A comprehensive changelog of all API versions and their changes
- [API Versioning](https://docs.firma.dev/guides/api-versioning.md): Learn how the Firma API handles versioning, deprecation, and breaking changes
- [Audit Trail](https://docs.firma.dev/guides/audit-trail.md): Track every action on a signing request for compliance and reporting.
- [API Authentication & JWT Tokens](https://docs.firma.dev/guides/authentication.md): Learn how to authenticate API requests with API keys and use JWT tokens for embedded template and signing request editors
- [Integrate Firma with Base44](https://docs.firma.dev/guides/base44-integration.md): Add legally binding e-signatures to any Base44 app using backend functions or a workspace-level OpenAPI integration.
- [Integrate Firma with Bolt.new](https://docs.firma.dev/guides/bolt-new-integration.md): Add legally binding e-signatures to any Bolt.new app using Next.js API routes, Netlify serverless functions, or Supabase Edge Functions.
- [Integrate Firma with Cloudflare](https://docs.firma.dev/guides/cloudflare-integration.md): Add legally binding e-signatures to Cloudflare Workers or Pages apps using the Firma API.
- [Complete Setup Guide](https://docs.firma.dev/guides/complete-setup-guide.md): This comprehensive guide shows you how to build and launch a complete e-signature workflow inside your own application using Firma.dev. We'll cover everything from account setup to embedded signing, workspace management, templates, and credit-based billing.
- [Workspaces](https://docs.firma.dev/guides/creating-workspaces.md): Workspaces let you create isolated environments for each of your customers or business units. Every workspace has its own templates, documents, and envelope usage—so teams stay separate without extra effort.
- [Integrate Firma with Cursor](https://docs.firma.dev/guides/cursor-integration.md): Add legally binding e-signatures to any project using Cursor's AI features and the Firma API.
- [Embeddable signing](https://docs.firma.dev/guides/embeddable-signing.md): Embed the signing experience into your product so signers can complete documents without leaving your app.
- [Embeddable signing request editor](https://docs.firma.dev/guides/embeddable-signing-request-editor.md): Embed the signing request editor in your product with secure JWT authentication.
- [Embeddable template editor](https://docs.firma.dev/guides/embeddable-template-editor.md): Embed the template editor in your product with secure JWT authentication.
- [Localization](https://docs.firma.dev/guides/localization.md): Firma supports 7 languages out of the box with automatic language detection, per-user persistence, and embed-friendly overrides.
- [Integrate Firma with Lovable](https://docs.firma.dev/guides/lovable-integration.md): Add legally binding e-signatures to any Lovable app using Edge Functions, Supabase, and webhooks.
- [MCP Integration](https://docs.firma.dev/guides/mcp.md): Connect Firma to AI assistants like Claude, ChatGPT, Cursor, GitHub Copilot, and more using the Model Context Protocol (MCP)
- [Integrate Firma with Mocha](https://docs.firma.dev/guides/mocha-integration.md): Add legally binding e-signatures to any Mocha app using AI-generated backend functions and the Firma API.
- [Platform Updates](https://docs.firma.dev/guides/platform-updates.md): A timeline of new features, improvements, and changes to the Firma platform
- [Rate Limits](https://docs.firma.dev/guides/rate-limits.md): Firma.dev is designed for very high volume e-signing API usage. Each Firma.dev account may have unlimited workspaces with unlimited API keys, providing horizontal scalability. All API endpoints are rate-limited to ensure fair usage and system stability. Rate limits are enforced per API key (this mea…
- [Integrate Firma with Replit](https://docs.firma.dev/guides/replit-integration.md): Add legally binding e-signatures to any Replit app using backend routes, Replit Secrets, and Replit Agent.
- [Sending a signing request](https://docs.firma.dev/guides/sending-signing-request.md): How to create and send signing requests to recipients.
- [Integrate Firma with Supabase](https://docs.firma.dev/guides/supabase-integration.md): Add legally binding e-signatures to any Supabase application using Edge Functions, Postgres, and webhooks.
- [Integrate Firma with v0](https://docs.firma.dev/guides/v0-integration.md): Add legally binding e-signatures to any v0 app using Next.js route handlers and environment variables.
- [Webhooks](https://docs.firma.dev/guides/webhooks.md): Implement secure webhook integrations to receive real-time event notifications from Firma.
- [White Labeling](https://docs.firma.dev/guides/white-labeling.md): Configure custom email domains, disable Firma emails, and create a fully branded signing experience for your customers.

## OpenAPI Specs

- [openapi-v01.16.00](https://docs.firma.dev/api-reference/v01.16.00/openapi-v01.16.00.json)
- [openapi-v01.15.03](https://docs.firma.dev/api-reference/v01.15.03/openapi-v01.15.03.json)
- [openapi-v01.15.02](https://docs.firma.dev/api-reference/v01.15.02/openapi-v01.15.02.json)
- [openapi-v01.15.01](https://docs.firma.dev/api-reference/v01.15.01/openapi-v01.15.01.json)
- [openapi-v01.15.00](https://docs.firma.dev/api-reference/v01.15.00/openapi-v01.15.00.json)
- [openapi-v01.14.00](https://docs.firma.dev/api-reference/v01.14.00/openapi-v01.14.00.json)
- [openapi-v01.13.00](https://docs.firma.dev/api-reference/v01.13.00/openapi-v01.13.00.json)
- [openapi-v01.12.01](https://docs.firma.dev/api-reference/v01.12.01/openapi-v01.12.01.json)
- [openapi-v01.12.00](https://docs.firma.dev/api-reference/v01.12.00/openapi-v01.12.00.json)
- [openapi-v01.11.00](https://docs.firma.dev/api-reference/v01.11.00/openapi-v01.11.00.json)
- [openapi-v01.10.00](https://docs.firma.dev/api-reference/v01.10.00/openapi-v01.10.00.json)
- [openapi-v01.09.00](https://docs.firma.dev/api-reference/v01.09.00/openapi-v01.09.00.json)
- [openapi-v01.08.00](https://docs.firma.dev/api-reference/v01.08.00/openapi-v01.08.00.json)
- [openapi-v01.07.00](https://docs.firma.dev/api-reference/v01.07.00/openapi-v01.07.00.json)
- [openapi-v01.06.00](https://docs.firma.dev/api-reference/v01.06.00/openapi-v01.06.00.json)
- [openapi-v01.05.00](https://docs.firma.dev/api-reference/v01.05.00/openapi-v01.05.00.json)
- [openapi-v01.04.00](https://docs.firma.dev/api-reference/v01.04.00/openapi-v01.04.00.json)
- [openapi-v01.03.00](https://docs.firma.dev/api-reference/v01.03.00/openapi-v01.03.00.json)
- [openapi-v01.02.00](https://docs.firma.dev/api-reference/v01.02.00/openapi-v01.02.00.json)
- [openapi-v01.01.00](https://docs.firma.dev/api-reference/v01.01.00/openapi-v01.01.00.json)
- [openapi-v01.00.02](https://docs.firma.dev/api-reference/v01.00.02/openapi-v01.00.02.json)
- [openapi-v01.00.01](https://docs.firma.dev/api-reference/v01.00.01/openapi-v01.00.01.json)