airSlate WorkFlow API

Name: airSlate WorkFlow API API
Brand: airSlate WorkFlow API
Availability: InStock

★ Only Publicly Available SpecProductivityCollaborationbearer15 EndpointsREST

For Agents

Create and run airSlate Flows, attach documents, and manage organisation users from a single REST API.

Quickstart

Get started with airSlate WorkFlow API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an airSlate flow"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with airSlate WorkFlow API API.

Issue an OAuth 2.0 access token via POST /oauth/token

List and inspect organisations the authenticated client can access

Create, update, and delete Flows scoped to an organisation

Attach documents to a Flow and list all documents in a Flow

Browse available templates that can seed new Flows

GET STARTED

Start building with airSlate WorkFlow API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for airSlate WorkFlow API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for airSlate WorkFlow API, keeping it validated and agent-ready. airSlate is a workflow automation platform that lets organisations build document-driven processes called Flows (or Slates), parametrise them with templates, attach documents, and assign users. The 15 endpoints cover OAuth 2.0 token issuance, organisation lookup, full CRUD on Flows, document attachment, template browsing, and user management. Best suited for HR, legal, finance, and procurement teams that need approvals and document workflows wired into other systems.

Use Cases

Patterns agents use airSlate WorkFlow API API for, with concrete tasks.

★ Document Workflow Provisioning

Create a Flow inside an organisation, seed it from a template, and attach the documents that must be signed or filled. POST /organizations/{organization_id}/flows accepts a Flow definition and POST /organizations/{organization_id}/flows/{flow_id}/documents adds documents one by one. Suitable for HR onboarding, vendor contracts, and legal NDAs.

Create a Flow named 'New Hire Onboarding' under organization 'org-123' and attach the offer letter document

Template-Based Flow Creation

Browse available templates and seed new Flows from them so workflow definitions stay consistent across departments. The Templates resource exposes the catalogue of reusable workflow blueprints; create a Flow with the template_id reference to bootstrap a Flow with predefined steps and document slots.

List templates available in the organisation and create a new Flow seeded from the chosen template

Programmatic Organisation Audit

Inventory all Flows, documents, and users across an organisation by paging through the /organizations/{organization_id}/flows and users endpoints. Useful for compliance audits, monthly process reviews, and migration tooling that needs to enumerate active workflows before changes.

List all Flows under organization 'org-acme' and return a summary of count, names, and updated_at timestamps

Agent Document Workflow via Jentic

An agent kicks off a document workflow by searching Jentic for the create-flow operation, loading the schema, and executing under an OAuth 2.0 bearer token managed by Jentic. The token-issuance step (POST /oauth/token) is also available through Jentic for refresh handling.

Search Jentic for 'create an airSlate flow', load the operation, and execute it under organization_id 'org-acme' with name 'Vendor NDA'

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for airslate workflow api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/oauth/token

Issue an OAuth 2.0 access token

GET

/organizations

List organisations

GET

/organizations/{organization_id}/flows

List Flows in an organisation

POST

/organizations/{organization_id}/flows

Create a Flow

PATCH

/organizations/{organization_id}/flows/{flow_id}

Update a Flow

DELETE

/organizations/{organization_id}/flows/{flow_id}

Delete a Flow

POST

/organizations/{organization_id}/flows/{flow_id}/documents

Attach a document to a Flow

POST

/oauth/token

Issue an OAuth 2.0 access token

GET

/organizations

List organisations

GET

/organizations/{organization_id}/flows

List Flows in an organisation

POST

/organizations/{organization_id}/flows

Create a Flow

PATCH

/organizations/{organization_id}/flows/{flow_id}

Update a Flow

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

airSlate OAuth client credentials are stored encrypted in the Jentic vault. Bearer tokens are issued, refreshed, and rotated transparently so agents never see raw client secrets or long-lived tokens.

Intent-based discovery

Agents search by intent ('create a document workflow', 'attach a document to a flow') and Jentic returns the matching airSlate operation with its organization_id, flow_id, and body schema.

Time to first call

Direct airSlate integration: 3-5 days for OAuth, Flow modelling, and document handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PandaDoc

Document signing and proposal workflows with a richer template designer

Choose PandaDoc when the focus is contract proposals and e-signature; choose airSlate when complex multi-step approval Flows are required

Alternative

Dropbox Sign

Lightweight e-signature API without airSlate's broader workflow primitives

Use Dropbox Sign for simple signature requests; use airSlate when documents must move through an approval Flow

Complementary

Smartsheet

Sheet-based work management that complements airSlate document workflows

Pair Smartsheet with airSlate when project tracking and document approvals share an audience and the team works primarily in spreadsheets

FAQs

Specific to using airSlate WorkFlow API API through Jentic.

Why is there no official OpenAPI spec for airSlate WorkFlow API?

airSlate does not publish a single canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call airSlate WorkFlow API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the airSlate WorkFlow API use?

OAuth 2.0 bearer tokens. Issue a token via POST /oauth/token with client credentials, then pass it as Authorization: Bearer <token>. Through Jentic the client credentials are stored encrypted and tokens are refreshed automatically.

Can I create a Flow from a template?

Yes. List templates via the Templates resource, then create a Flow under an organisation referencing the chosen template_id. The Flow is seeded with the template's predefined steps and document slots so subsequent attach-document calls fill the workflow.

What are the rate limits for the airSlate WorkFlow API?

airSlate applies plan-based limits enforced via HTTP 429 responses. Documented thresholds vary by tier; the docs at docs.airslate.io are authoritative. Treat 429 as a backoff-and-retry signal.

How do I create a Flow through Jentic?

Install with pip install jentic, search for 'create an airSlate flow', load the POST /organizations/{organization_id}/flows operation, and execute with organization_id and the Flow name. Jentic handles the bearer token at execution time.

Can I attach a document to an existing Flow?

Yes. POST /organizations/{organization_id}/flows/{flow_id}/documents attaches a document to the named Flow. List the resulting documents with the matching GET endpoint.