airSlate
airSlate is a document workflow automation holding company whose product family covers no-code workflow automation (altaFlow, formerly airSlate WorkFlow), electronic signature (signNow), PDF editing and form filling (pdfFiller and DocHub), legal forms (US Legal Forms), landing pages (Instapage), and an AI-powered marketing intelligence platform. Developer APIs are exposed primarily through the signNow and pdfFiller product lines; WorkFlow / altaFlow surfaces automation bots and integrations rather than a broad public REST API.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles airSlate the way a machine reads it — 25 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — airSlate scores 36.4/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile airSlate
Each block below is one kind of artifact we hold for airSlate. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
airSlate WorkFlow (altaFlow)
No-code document workflow automation platform (recently rebranded as altaFlow). Supports building workflows that combine forms, contracts, bots, and integrations across CRM and ...
signNow API
REST API for signNow, airSlate's electronic signature product. Covers documents, signatures, templates, users, groups, fields, and webhooks. Supports OAuth 2.0 with production b...
pdfFiller API
REST API for pdfFiller, covering document upload and conversion, form filling, templates, and e-signature flows. Used to embed PDF editing and form workflows into third-party ap...
DocHub
Cloud PDF editor that integrates with Google Workspace. Provides editing, signing, and sharing of PDFs from inside Google apps. Programmatic access is primarily via Google Works...
US Legal Forms
Online catalog of 85,000+ state-specific legal forms. Consumer and SMB product; no public developer API.
Instapage
Landing page builder and personalization platform. Offers REST endpoints for account integration via the Instapage developer surface.
airSlate Marketing Intelligence Platform
AI-powered automation platform for end-to-end marketing operations. Positioned as a vertical AI product rather than a developer API.
airSlate Document Fields API
The Document Fields API from airSlate — 3 operation(s) for document fields.
airSlate Document Groups API
The Document Groups API from airSlate — 4 operation(s) for document groups.
airSlate Documents API
The Documents API from airSlate — 7 operation(s) for documents.
airSlate Embedded API
The Embedded API from airSlate — 3 operation(s) for embedded.
airSlate Folders API
The Folders API from airSlate — 2 operation(s) for folders.
airSlate Invites API
The Invites API from airSlate — 5 operation(s) for invites.
airSlate OAuth API
The OAuth API from airSlate — 1 operation(s) for oauth.
airSlate Smart Fields API
The Smart Fields API from airSlate — 1 operation(s) for smart fields.
airSlate Templates API
The Templates API from airSlate — 4 operation(s) for templates.
airSlate Users API
The Users API from airSlate — 3 operation(s) for users.
airSlate Webhooks API
The Webhooks API from airSlate — 2 operation(s) for webhooks.
Scroll within the panel for all 18 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
airSlate signNow REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Airslate Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Airslate Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for airSlate — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/airslate · machine-readable index on apis.io