Process St Process Street API
60
AI ReadinessAI-Aware (B-)60/100
Official vendor OpenAPI document · agent-readyProductivityTask ManagementapiKey44 EndpointsREST
For Agents
Create workflow runs, manage checklist tasks, collect form field data, and track process completion for repeatable business operations and SOPs.
Use for: I need to start a new workflow run from a template, I want to mark a task as complete in a running checklist, List all active workflow runs and their completion status, Get the form field values submitted for a specific workflow run
Not supported: Does not handle project management timelines, Gantt charts, or resource scheduling - use for checklist-based workflow execution and SOP tracking only.
The Process Street API enables programmatic management of workflows, workflow runs, tasks, form fields, comments, data sets, and webhooks across 44 endpoints. It supports creating and tracking checklist-based processes, assigning tasks to team members, collecting structured data through form fields, and automating workflow triggers via webhooks for repeatable business operations.
Install Jentic One Beta
Connect the Process Street API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Process Street API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprocess.st%2Fprocess-street" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprocess.st%2Fprocess-street" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Process Street API.
Create and manage workflow runs from predefined checklist templates
Assign and track individual task completion within running workflows
Collect structured data through configurable form fields attached to workflow steps
Import and manage records in data sets for reference during workflow execution
Configure webhooks to trigger external actions on workflow and task state changes
Add comments to workflow runs for team collaboration and audit trails
Manage task-level and workflow-level assignees for accountability tracking
Use Cases
Patterns agents use Process Street API for, with concrete tasks.
★ Employee Onboarding Automation
Automate new employee onboarding by programmatically creating workflow runs from onboarding templates. The Process Street API allows agents to initiate a checklist run, assign tasks to HR staff and managers, populate form fields with employee details, and track completion across all onboarding steps. Each run maintains an audit trail of who completed which step and when.
Create a workflow run from the onboarding template workflow ID, assign the first three tasks to the hiring manager's email, and set the start date form field to today's date
Compliance Process Tracking
Ensure regulatory compliance by running standardized checklists and collecting required evidence through form fields. The API enables agents to trigger compliance workflows on schedule, verify that all mandatory steps have been completed with required form data filled, and export completion records for audit purposes. Webhook notifications alert when processes fall behind schedule.
Retrieve all workflow runs for the monthly compliance template, check which runs have incomplete required tasks, and list the overdue task names and assignees
Data Collection Workflows
Use workflow form fields as structured data collection points within multi-step processes. The API supports uploading files to form fields, reading submitted values, and importing reference data into data sets. Agents can validate that all required form fields are populated before allowing workflow progression, and extract collected data for downstream processing.
Get all form field values for a specific workflow run using GET /workflow-runs/{workflowRunId}/form-fields and verify that no required fields have null values
AI Agent Workflow Orchestration
Enable AI agents to manage operational processes end-to-end through Jentic by discovering and executing Process Street operations. Agents can create workflow runs, monitor task progress, collect form data, and trigger follow-up actions based on checklist completion - all without hardcoding API paths or managing API key rotation.
Search Jentic for 'create a workflow run', load the operation schema, and execute to start a new checklist run from a specified workflow template ID
Key Endpoints
44 endpoints — the process street api enables programmatic management of workflows, workflow runs, tasks, form fields, comments, data sets, and webhooks across 44 endpoints.
METHOD
PATH
DESCRIPTION
POST
/workflow-runs
Create a new workflow run from a template
GET
/workflow-runs/{workflowRunId}/tasks
List all tasks in a workflow run
PUT
/workflow-runs/{workflowRunId}/tasks/{taskId}
Update task status in a workflow run
GET
/workflow-runs/{workflowRunId}/form-fields
Get form field values for a workflow run
GET
/workflows
List all workflow templates
POST
/webhooks
Create a webhook subscription
POST
/data-sets/{dataSetId}/records/import
Import records into a data set
GET
/workflow-runs/{workflowRunId}/assignees
List assignees for a workflow run
POST
/workflow-runs
Create a new workflow run from a template
GET
/workflow-runs/{workflowRunId}/tasks
List all tasks in a workflow run
PUT
/workflow-runs/{workflowRunId}/tasks/{taskId}
Update task status in a workflow run
GET
/workflow-runs/{workflowRunId}/form-fields
Get form field values for a workflow run
GET
/workflows
List all workflow templates
POST
/webhooks
Create a webhook subscription
POST
/data-sets/{dataSetId}/records/import
Import records into a data set
GET
/workflow-runs/{workflowRunId}/assignees
List assignees for a workflow run
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Process Street API
- AI-Aware (B-)60/100
78
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability50
Security60
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
78
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
14%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
18%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
60
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
60%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Process Street API by hand means setting its API key header, targeting public-api.process.st/api/v1.1, and mapping workflow runs, tasks, and form fields yourself. Through Jentic you install once, import Process Street from the API Directory, store the key once, and your agent calls it.
Permission scoping
Process Street puts the workflow run id in the URL path (/workflow-runs/{workflowRunId}/tasks), so a rule can pin your agent to a specific workflow run: it can read and update tasks within that run. You choose the operations it may call, so a write like importing data set records is not included unless you add it.
Credential isolation
Your Process Street API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'start a workflow checklist' or 'update a task in a run', and Jentic returns the matching Process Street operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Process Street API through Jentic.
What authentication does the Process Street API use?
The Process Street API uses an API key passed in the request header. You generate the key from your Process Street account settings. Through Jentic, the API key is stored encrypted in the credential vault and injected into requests automatically.
Can I create workflow runs programmatically with the Process Street API?
Yes. POST to /workflow-runs creates a new run from an existing workflow template. You specify the workflow ID and can optionally set initial assignees. The run starts immediately with all template tasks available for completion.
What are the rate limits for the Process Street API?
The Process Street API applies rate limits per API key. Requests that exceed the limit receive a 429 response with a Retry-After header. The standard limit is sufficient for most automation use cases including CI/CD-triggered workflow creation.
How do I track task completion in a workflow run through Jentic?
Search Jentic for 'list workflow tasks', load the schema for GET /workflow-runs/{workflowRunId}/tasks, and execute with your run ID. The response includes each task's completion status, assignee, and due date. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.
Can I collect form data through the Process Street API?
Yes. GET /workflow-runs/{workflowRunId}/form-fields retrieves all form field values for a run. You can also upload files to file-type form fields using POST /workflow-runs/{workflowRunId}/form-fields/{formFieldId}/upload. Form fields support text, dates, file uploads, and dropdown selections.
Does the Process Street API support webhooks?
Yes. POST /webhooks creates a subscription that fires on workflow run and task events. You specify the target URL and event types. This enables real-time integration with downstream systems when tasks are completed or workflow runs finish.
Can I limit what my agent is allowed to do with the Process Street API?
Yes. Because you run Jentic One yourself, your own rules decide which Process Street operations and credentials the agent may use. Since Process Street puts the workflow run ID in the URL path, such as /workflow-runs/{workflowRunId}/tasks, you can pin the agent to a specific run so it only reads and updates tasks within it. You also choose the exact operations it may call, so a write like importing data set records via /data-sets/{dataSetId}/records/import stays off unless you grant it.
GET STARTED