For Agents
Start, inspect, suspend, and resume Oracle BPM 12c process instances and act on human tasks, attachments, and comments over REST.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Oracle BPM Suite REST 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with Oracle BPM Suite REST API API.
List process definitions deployed to Oracle BPM Suite
Start a new process instance from a deployed process definition
Suspend or resume a running BPM process instance
Retrieve the human task list for the authenticated user
GET STARTED
Use for: Start a new instance of a deployed BPM process, List the human tasks assigned to the current user, Suspend a running BPM process instance for review, Resume a previously suspended BPM process instance
Not supported: Does not handle BPMN process modelling, SOA composite deployment, or BAM analytics — use for runtime process and human task operations only.
The Oracle BPM Suite REST API exposes process definitions, running process instances, and human tasks in Oracle BPM Suite 12c so that external systems can drive workflows without using the SOA suite's web console. It supports starting and inspecting process instances, suspending and resuming them, and acting on human tasks including comments and attachments. The surface targets enterprise teams that already run Oracle BPM and want to integrate it with self-service portals, RPA bots, or AI agents.
Add comments and attachments to an in-flight human task
Inspect process instance status and audit trail
Patterns agents use Oracle BPM Suite REST API API for, with concrete tasks.
★ Self-Service Process Initiation
Let a customer-facing portal kick off long-running Oracle BPM processes — credit applications, supplier onboarding, claims intake — without exposing the BPM web console. The REST API accepts a process definition id and a payload, returning the new process instance id that the portal can track.
POST /4.0/processes/{processDefId}/instances with the application payload and store the returned instance id
Human Task Triage in External Tools
Surface Oracle BPM human tasks inside Microsoft Teams, Slack, or a custom inbox so approvers act on them without logging into the BPM workspace. The /4.0/tasks endpoints return tasks for the authenticated user, and the task action endpoints let the integration approve or update them in place.
GET /4.0/tasks for the user, post the list to the chat tool, then POST a task action when the user clicks approve
Process Instance Pause for Investigation
Operations and audit teams can pause a running BPM process instance while they investigate a discrepancy — a misrouted invoice, a flagged customer, a contract under review — and resume it once the issue is resolved. The suspend and resume endpoints work directly against the instance id.
POST /4.0/processes/instances/{instanceId}/suspend, then later POST .../resume after audit sign-off
Agent-Driven BPM Operations via Jentic
An AI assistant for operations leads can list open human tasks, add comments, and start new BPM process instances on demand. Through Jentic the agent works against the BPM REST API without holding raw Basic Auth credentials, using natural-language intents that map to the right endpoints.
Search Jentic for 'list my BPM human tasks', load the GET /4.0/tasks operation, and execute on behalf of the user
20 endpoints — the oracle bpm suite rest api exposes process definitions, running process instances, and human tasks in oracle bpm suite 12c so that external systems can drive workflows without using the soa suite's web console.
METHOD
PATH
DESCRIPTION
/4.0/processes
List process definitions
/4.0/processes/{processDefId}/instances
Start a process instance
/4.0/processes/instances/{instanceId}/suspend
Suspend a running instance
/4.0/processes/instances/{instanceId}/resume
Resume a suspended instance
/4.0/tasks
List human tasks for the user
/4.0/tasks/{taskId}
Get a specific task
/4.0/processes
List process definitions
/4.0/processes/{processDefId}/instances
Start a process instance
/4.0/processes/instances/{instanceId}/suspend
Suspend a running instance
/4.0/processes/instances/{instanceId}/resume
Resume a suspended instance
/4.0/tasks
List human tasks for the user
Three things that make agents converge on Jentic-routed access.
Credential isolation
BPM Suite Basic Auth credentials are stored encrypted in the Jentic vault. Agents authenticate with a scoped Jentic session and the underlying weblogic username and password never reach the model context.
Intent-based discovery
Agents search by intent like 'start a BPM process instance' or 'list my human tasks' and Jentic returns the matching endpoint from the BPM Suite API with its parameter schema.
Time to first call
Direct integration: 3-5 days to wire Basic Auth against WebLogic, model the process and task payloads, and handle suspend/resume edge cases. Through Jentic: under 1 hour from signup to first task action.
Alternatives and complements available in the Jentic catalogue.
Camunda Platform REST API
Open-source BPMN process engine with a similar process and task REST surface
Pick Camunda for greenfield BPMN automation or open-source deployments; pick Oracle BPM Suite when the workflows already live in an Oracle SOA estate.
Kissflow API
SaaS workflow and process automation platform with a hosted task model
Choose Kissflow for SaaS-only workflow automation without on-prem infrastructure; Oracle BPM Suite is the right choice when you already run BPM 12c.
ServiceNow Now Platform API
ITSM and workflow platform commonly used alongside Oracle BPM for ticket-driven processes
Use ServiceNow when the workflow originates from an ITSM ticket or service catalog request; Oracle BPM Suite is for the long-running business process behind it.
Specific to using Oracle BPM Suite REST API API through Jentic.
What authentication does the Oracle BPM Suite REST API use?
HTTP Basic Auth against the BPM Suite weblogic server. The credential is the BPM user the integration runs as. Through Jentic, the username and password are stored encrypted in the vault and the agent gets a scoped session — the raw credentials never enter the model context.
Can I start and pause process instances with the BPM Suite API?
Yes. POST /4.0/processes/{processDefId}/instances starts a new instance from a deployed process definition. POST /4.0/processes/instances/{instanceId}/suspend pauses a running instance and the matching /resume endpoint brings it back online.
How do I act on human tasks through the BPM Suite API?
GET /4.0/tasks returns the human task list for the authenticated user and GET /4.0/tasks/{taskId} returns a specific task. The Task Actions, Task Comments, and Task Attachments tag groups in the spec cover approving, commenting, and attaching files to those tasks.
What are the rate limits for the Oracle BPM Suite REST API?
Rate limits are not declared in the spec because BPM Suite is typically deployed on customer-managed WebLogic infrastructure. Practical limits depend on the cluster sizing and the underlying SOA Suite tuning rather than a vendor-imposed quota.
How do I list BPM human tasks through Jentic?
Install the SDK with pip install jentic, then search for 'list my BPM human tasks'. Jentic returns the GET /4.0/tasks operation with its schema; load it and execute. Sign up at https://app.jentic.com/sign-up.
/4.0/tasks/{taskId}
Get a specific task