Embed Robo Meister as your orchestration layer

Use one orchestration layer for Workflow execution, fallback, and Audit Trail evidence across ERP, MES, WMS, and custom apps.

Book a partner call Get API access View developer quickstart

Developer-first onboarding and docs
Modular adoption—integrate one flow at a time
Built for production-grade, business-critical workflows

Why partner teams choose this layer

Intent-based actions (notify, approve, validate) replace channel-specific steps. Executor auto-match and fallback chain (SaaS, AI, human, device) keep business flows moving with audit-ready evidence.

Physical / Industry 4.0 Track

For MES/WMS/SCM integrators with edge and device execution needs, use the dedicated track page as a shared navigation reference.

Open Industry 4.0 Partner Track

Pick the modules you need—start small, expand later

You can consume modules independently—no all‑or‑nothing rollout.

Data Sync & Mapping

Standardize payloads, mappings, and transformations.

Orders & Documents

Orchestrate document lifecycles and statuses.

Inventory & Stock Movements

Handle adjustments, reservations, and updates.

Production & Shopfloor Flows

Track steps, events, and completions (MES-style).

Warehouse Operations

Picking/packing/shipping orchestration (WMS-style).

Workflow & Approvals

States, rules, validations, and exceptions.

Monitoring & Retries

Trace runs, handle retries, surface failures.

Audit & Reporting

Execution history for audit-friendly operations.

Common scenarios teams ship faster

ERP ↔ WMS: keep orders, inventory, and shipment status consistent in your app
MES ↔ ERP: sync production events, material usage, and completion updates
Multi-system operations: orchestrate workflows across internal tools and external platforms
Modernization: replace brittle point-to-point scripts with reusable API capabilities

Works even when integrations fail

If an API, inbox, or device is unavailable, the Workflow does not stop. Robo Meister routes the step to a safe Fallback path, alerts the right owner, and keeps the Audit Trail complete.

Hybrid execution

Hybrid automation with fallback: AI, people, integrations, and devices work together with audit trails. The platform picks the best Executor for each step and can switch automatically when conditions change.

Terminology

Workflow: an executable business process.
Pack: installable set of workflows, rules, templates, and integrations.
Executor: who or what performs a step (AI, employee, SaaS, or device).
Fallback: automatic switch to another Executor when needed.
Audit Trail: evidence of what happened, when, and why for compliance reviews.

How it works

Choose modules for your workflow
Connect your systems (your apps ↔ Robo Connector API)
Implement your flow with clear states and validations
Operate with confidence using monitoring and predictable retries

curl https://api.robo-meister.com/v1/workflows/run \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"workflow_id":"wf_order_sync","input":{"order_id":"ORD-1024"}}'

What you can call

A practical API surface you can evaluate on day one. Endpoint names below are representative and kept stable during early integration design.

Endpoint	Day-1 purpose
`/workflows/run`	Start a workflow run with validated payload input.
`/workflows/status`	Fetch execution status, progress, and terminal state.
`/documents/validate`	Validate document schema, mappings, and business rules.
`/documents/status`	Track accepted/rejected documents and processing stage.
`/inventory/movements`	Create or list inventory adjustments, reservations, and transfers.
`/production/events`	Ingest MES-style production events and completion signals.
`/warehouse/pickwaves`	Create and monitor pickwave orchestration in warehouse flows.
`/audit/events`	Query immutable execution/audit event history for compliance.

One resource, many integration formats

Robo Meister APIs are not limited to JSON. For selected resources, the same business resource can be returned as data, export, document, or embeddable UI depending on URL suffix or request headers. A client list, order list, document status, or workflow report can be exposed as JSON/XML for system integration, CSV/XLS for operations, PDF for formal reporting, or HTML as an embeddable widget.

Data API

JSON/XML

Exports

CSV/XLS

Documents

PDF

Widgets

HTML

Resource format	Partner use case
`/client/all.json`	Application/API integration
`/client/all.xml`	Legacy or enterprise system integration
`/client/all.csv`	Full export for operations
`/client/all.xls`	Spreadsheet-friendly business view
`/client/all.pdf`	Formal report or document package
`/client/all.html`	Embeddable table/widget for partner portals

Partner benefit

Start with a widget, scale into an API

Partners do not need to build a full frontend on day one. They can embed a Robo Meister HTML representation as a lightweight client, order, or status table inside an iframe with Robo Meister default styling, or load the HTML fragment without styles and apply their own CSS. Later, the same partner can connect to the same resource through JSON/XML endpoints without changing the underlying business resource logic.

Faster proof of concept with a working business view immediately
Lower frontend effort for partner portals and internal tools
Gradual path from iframe or HTML widget to full API integration
Same supported resource logic underneath each representation

Test a resource format in the developer portal

Default response behavior is optimized for real use cases: HTML views keep the existing paginated table behavior, while API/export/report formats such as JSON, XML, CSV, XLS, and PDF keep returning the full filtered list by default. If partners send query filters, page, limit, or pagination controls, those parameters are applied where the supported resource exposes them. Use ?pagination=1 to request paginated responses, ?no-pagination=1 to force the full filtered list, and ?limit=50 to set the pagination size when pagination is enabled.

Implementation in weeks

Week 1

Connect source data and authentication (OAuth + API keys).

Week 2

Run the first workflow in production-like mode and stand up dashboard monitoring.

Week 3

Scale throughput, add workflows, and harden retry/idempotency behavior.

SDKs and quickstarts for faster implementation

Use the SDK matrix to start quickly with supported integrations.

Available now

PHP SDK

composer require robo/robo-connector-sdk

Open on Packagist Package page

Repository SDK

Java SDK

Use the Java SDK module in this repository (Maven/Gradle setup documented in repo docs).

Open Java SDK docs View repository docs

Available now

Python SDK

pip install robo-connector-sdk

Open Python SDK docs View repository docs

SDK coverage aligns with currently supported routes. Production/high-volume access can require approval.

How access works

Public documentation is available without login: /developers and /dev/api.
Use /portal/start?intent=api_partner for login/register and API key setup.
Portal includes API keys, usage/credits, examples, plus slugger/resource tools.
Sandbox/basic access is self-serve where currently enabled; production/high-volume access can require manual approval.
Partner access lifecycle: requested → sandbox_active → production_requested → production_approved (or rejected).

Integration Sprint: ship a working POC in weeks

If you’re hiring because integrations are stuck—or you can’t afford months of trial and error—use a time‑boxed onboarding engagement.

Architecture diagram reviewed with your team and integration owners
OpenAPI contract reviewed and approved for first production workflow
First real flow live (with measurable status transitions and outputs)
Monitoring dashboard with trace IDs, errors, retries, and SLA indicators
Handover document with runbook, ownership, and production rollout checklist

Book the Integration Sprint

Security & ops readiness

OAuth 2.0 scopes per workflow capability (least-privilege by default)
API keys scoped per organisation, with key-level usage and rotation controls
Audit logs for access, execution changes, and policy-relevant events
Retries with idempotency keys to prevent duplicate business operations
Monitoring hooks with trace IDs for cross-system incident diagnosis
Cloud and on-prem deployment patterns available during technical review

Detailed control matrices (scopes, retention, deployment boundaries) are provided in solution design workshops.

Pricing model (early guidance)

Usage-based credits aligned to API calls and workflow complexity.
Onboarding sprint available as a fixed-scope implementation package.
Typical starting range: scoped after discovery call and first endpoint selection.
Credit mapping example: light status checks consume fewer credits than full workflow runs.

Self-serve developer portal for integration partners

The /solution/partner workspace includes a self-serve developer portal where your engineers can get credentials, test endpoints, and monitor API usage without support bottlenecks.

OpenAPI docs + OAuth helper

Browse endpoint references, validate scopes, and generate OAuth-ready snippets from one place.

API keys & token generator

Issue organisation API keys and mint user tokens tied to the selected key with clear expiration controls.

Credit counter

Track consumed and remaining credits in real time, linked to either organisation quotas or API key-level pools.

Open Dev Portal Open Developers Docs

Quota ownership can be switched between organisation-wide billing or API key-level credit buckets depending on your operating model.

Pilot targets disclaimer

Pilot KPI targets are planning assumptions. Reported outcomes are either modeled estimates or measured production values depending on deployment stage and data maturity.

Frequently asked questions

Can we start with a single module?

Yes—Robo Connector API is modular. Start with one workflow, then expand.

How long does a typical POC take?

With the Integration Sprint, teams can validate an end‑to‑end flow in weeks (scope-dependent).

What systems can you connect to?

ERP/MES/WMS and custom line‑of‑business apps. We’ll confirm fit during a short technical call.

Do you replace our integration layer?

You keep control of your business logic. The API provides reusable building blocks commonly required in enterprise workflows.

How is pricing structured?

Typically usage-based, plus optional onboarding packages. We’ll propose the best fit after understanding scope.

Ready to embed Robo Meister as your orchestration layer?

Book a partner call Get API access