Process Street
Process Street is a no-code workflow and process management platform for building, running, and automating recurring team processes as workflows (reusable templates) and workflow runs (checklists). Its REST Public API is organized around resource-oriented URLs, accepts and returns JSON, and covers workflows, workflow runs, tasks, form fields and values, pages, folders, data sets, users, one-off tasks, scheduled workflows, comments, attachments, outgoing webhooks, and incoming (data set + workflow) webhooks. Authentication is via an X-API-KEY header; results paginate through an opaque cursor with HATEOAS next links; and a hosted Model Context Protocol (MCP) server exposes most endpoints as tools for AI agents.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Process Street the way a machine reads it — 35 machine-readable artifacts across 28 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 — Process Street scores 54.2/100 (developing), with a separate agent-readiness read of 64/100 (agent native). 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 Process Street
Each block below is one kind of artifact we hold for Process Street. 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 28
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.
Process Street Attachments API
An attachment is a file uploaded to a task within a workflow run. Use these endpoints to list, upload, and delete task-level attachments.
Process Street Comments API
A comment is a discussion message on a task within a workflow run. Use these endpoints to create, list, update, and delete comments.
Process Street Data Set Incoming Webhooks API
An incoming webhook triggers data set row creation or updates from external systems. Use these endpoints to create, view, update, and delete incoming webhooks for a data set.
Process Street Data Sets API
A data set is a structured collection of records that can be linked to workflow form fields. Use these endpoints to manage data sets and their records.
Process Street File Uploads API
A file upload is a two-step upload for large files. Create one to get an upload URL and a `fileUploadId`, send the file's bytes to that URL, then attach the upload to a target (...
Process Street Folders API
A folder organizes workflows, pages, and other templates within your organization. Use these endpoints to create and manage folders.
Process Street Form Field Values API
A form field value is the data entered into a form field within a workflow run. Use these endpoints to read and update form field values for a specific workflow run.
Process Street Form Fields API
A form field is a data-collection element defined on a workflow template. Use these endpoints to inspect the form fields and their available options on a workflow.
Process Street My Work API
My Work is your personal task inbox — a consolidated view of all tasks and checklist items assigned to you across all workflows. Use these endpoints to list, search, and manage ...
Process Street One-Off Tasks API
A one-off task is a standalone task that can optionally be linked to a workflow run. Use these endpoints to create, view, and manage one-off tasks.
Process Street Page Revisions API
A page revision is a versioned snapshot of a page's content. Use these endpoints to list, inspect, and manage revisions.
Process Street Page Widgets API
A page widget is a content element (text, image, video, file, embed, cross-link, or table) on a page revision. Use these endpoints to create and manage widgets on draft revisions.
Process Street Pages API
A page is a document template for sharing information. Use these endpoints to create and manage pages.
Process Street Scheduled Workflows API
A scheduled workflow is a recurring schedule that automatically creates workflow runs. Use these endpoints to list scheduled workflows and their recurrence rules.
Process Street Tasks API
A task is a step within a workflow run. Tasks can be checked off, assigned to users, and may contain form fields for collecting data. Use these endpoints to view and update task...
Process Street Users API
These endpoints let you list the users in your organization.
Process Street Utilities API
Helper endpoints for testing authentication and checking rate limits.
Process Street Webhooks API
A webhook delivers real-time notifications to your application when events occur in Process Street. Use these endpoints to create and manage webhook subscriptions.
Process Street Workflow Due Date Rules API
A workflow due date rule defines how the checklist-level due date is calculated for workflow runs — either relative to the run's start date or derived from a Date form field val...
Process Street Workflow Incoming Webhooks API
An incoming webhook triggers workflow runs from external systems. Use these endpoints to create, view, update, and delete incoming webhooks for a workflow.
Process Street Workflow Logic Rules API
Workflow logic rules are conditional rules that control the visibility of tasks and form fields within a workflow revision. Use these endpoints to create, view, and manage logic...
Process Street Workflow Revisions API
A workflow revision is a versioned snapshot of a workflow's structure. Use these endpoints to list, inspect, and manage revisions.
Process Street Workflow Runs API
A workflow run is an active instance of a workflow. Each run tracks its own progress, assignees, and form field values as it moves through the process. Use these endpoints to cr...
Process Street Workflow Task Assignment Rules API
A workflow task assignment rule assigns a task template on a draft workflow revision to a specific user (static) or derives assignees from a source such as the workflow run init...
Process Street Workflow Task Due Date Rules API
A task due date rule defines how an individual task's due date is calculated within a workflow run — relative to the run's start/due date, a form field value, or another task. U...
Process Street Workflow Tasks API
A workflow task is a task template within a workflow revision. Use these endpoints to create, view, update, and delete task templates on draft revisions. > 💡 Notes for MCP clien...
Process Street Workflow Widgets API
A workflow widget is a form field or content element on a task within a workflow revision. Use these endpoints to create and manage widgets on draft revisions.
Process Street Workflows API
A workflow is a reusable process template that defines the structure, tasks, and form fields for a repeatable process. Use these endpoints to browse and inspect your organizatio...
Scroll within the panel for all 28 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
process-street-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Process Street Webhooks
ASYNCAPISecurity Posture 4
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 Process Street — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/process-street · machine-readable index on apis.io