Crosser Control Center API
Agent-ready OpenAPI document · curated by JenticIOTDevice Managementbearer16 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Authenticate, manage edge nodes, deploy data flows, and query events on Crosser Control Center installations.
Use for: I need to log in to a Crosser Control Center instance and get a token, Deploy a Crosser flow to a specific edge node, List all resources defined in our Crosser tenant, Get the current user's profile from Crosser
Not supported: Does not handle on-edge flow execution, raw industrial protocol drivers, or message-broker delivery - use for Crosser Control Center management operations only.
Jentic publishes the only available OpenAPI specification for Crosser Control Center API, keeping it validated and agent-ready. The Crosser Control Center is a low-code edge analytics and integration platform that orchestrates data flows across industrial edge nodes. The REST API authenticates users with JWT bearer tokens, manages resources and resource versions, registers and removes edge nodes, queries events, and deploys flow definitions out to edge fleets. It also covers identity provider secret management for self-hosted deployments.
Install Jentic One Beta
Connect the Crosser Control Center API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crosser Control Center 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%2Fcrosser.io%2Fcrosser" | 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%2Fcrosser.io%2Fcrosser" | 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 Crosser Control Center API.
Authenticate users against Crosser Control Center and obtain a JWT bearer token via /api/authentication/login
Register and delete edge nodes used to run Crosser flows in industrial environments
Deploy a flow definition to a specific edge node fleet via the deploy endpoint
Manage resource versions including data upload, draft creation, and version delete
Query events with filtering, pagination, and sorting to monitor edge activity
Rotate identity provider secrets for federated authentication setups
Use Cases
Patterns agents use Crosser Control Center API for, with concrete tasks.
★ Edge Node Lifecycle Automation
Automate provisioning and decommissioning of Crosser edge nodes by calling POST /api/edgenodes when new hardware comes online and DELETE /api/edgenodes/{id} when nodes are retired. This keeps the Control Center inventory in sync with the physical fleet without manual UI clicks, which matters at scale across hundreds of industrial sites. The pattern fits cleanly into a provisioning pipeline that already manages credentials and network configuration.
Create a new Crosser edge node for site SE-Stockholm-3 and verify it shows up in GET /api/edgenodes
Flow Deployment Pipeline
Push a new version of a data integration flow out to production edge nodes by calling POST /api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy. A CI/CD job builds a flow definition, registers it via resources endpoints, then deploys to the targeted edge nodes - replacing manual export/import in the Crosser UI. This shortens the gap between flow design and production rollout to minutes.
Deploy flow definition flowdef-42 with flow ID flow-100 to the production edge node group and confirm a successful response
Edge Event Monitoring and Audit
Pull recent Crosser events with GET /api/events using filter, pagination, and sort parameters to drive an internal observability dashboard or to feed an SIEM. Operations teams use this to detect node disconnects, deploy failures, and authentication issues without logging into the Crosser UI for every site. The endpoint is well-suited to scheduled polling and incremental sync.
List the last 100 Crosser events filtered to deploy failures across the production environment in the last 24 hours
AI Agent Industrial Operator Assistant
An AI agent helps an operator manage a Crosser Control Center fleet through Jentic. The agent searches for the crosser_deploy_flow operation, loads its schema, and executes against the operator's vaulted JWT credential. This lets a natural-language assistant trigger a flow deploy or pull recent events without the operator opening the web console.
Use the Jentic SDK to log in to Crosser, fetch the last 50 events for the production fleet, and summarise any deploy failures
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for crosser control center api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/api/authentication/login
Login with email and password
GET
/api/users/me
Get current user information
GET
/api/resources
List all resources
POST
/api/edgenodes
Create a new edge node
GET
/api/events
List events with filtering, pagination, and sorting
POST
/api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy
Deploy a flow to edge nodes
POST
/api/authentication/login
Login with email and password
GET
/api/users/me
Get current user information
GET
/api/resources
List all resources
POST
/api/edgenodes
Create a new edge node
GET
/api/events
List events with filtering, pagination, and sorting
POST
/api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy
Deploy a flow to edge nodes
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Crosser Control Center by hand means resolving your instance host, calling /api/authentication/login for a JWT, and re-authenticating when the token expires. Through Jentic you install once, import Crosser from the API Directory, store the login credentials once, and your agent calls it.
Permission scoping
Crosser puts the flow definition and flow ids in the deploy URL path (/api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy), so a rule can pin the agent to deploying the flows you allow. You choose the operations it may call, so creating edge nodes is not included unless you add that operation.
Credential isolation
Your Crosser credentials and resulting JWT are stored once, encrypted, by your own Jentic One instance, and the login exchange and Authorization header are handled at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'deploy a flow to a Crosser edge node' or 'list Crosser events', and Jentic returns the matching Crosser 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 Crosser Control Center API through Jentic.
Why is there no official OpenAPI spec for Crosser Control Center API?
Crosser does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crosser Control Center API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Crosser Control Center API use?
The API uses JWT bearer-token authentication. Clients first POST credentials to /api/authentication/login to receive a token, then attach it as Authorization: Bearer on subsequent calls. Through Jentic the credentials are stored encrypted in the vault and the token exchange is handled at request time.
How do I deploy a flow to edge nodes through Jentic?
Search Jentic for 'deploy a Crosser flow', load the operation schema for POST /api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy, and execute with the flow definition ID, flow ID, and target edge node group. Jentic injects the bearer token automatically.
Can I list and filter Crosser events through the API?
Yes. GET /api/events supports filtering, pagination, and sorting parameters so you can pull only the events you need, for example deploy failures in the last hour, without paging through the whole history.
How many endpoints does the Crosser Control Center API expose?
Sixteen endpoints across authentication, users, resources, resource versions, edge nodes, events, flow deployments, and identity provider secrets management.
Is the base URL fixed or per-instance?
The base URL uses an instance variable (https://{instance}.crosser.io) so each customer's Control Center has its own subdomain. The default value in the spec is 'app', and you can override it when configuring the integration.
Can I limit what my agent is allowed to do with the Crosser Control Center API?
Yes. Jentic One runs on infrastructure you host, so your own rules decide which Crosser operations and credentials the agent may use. You pick the operations it can call, so read-only tasks like listing events with GET /api/events or fetching the current user stay separate from write actions, and creating edge nodes with POST /api/edgenodes is only available if you add that operation. Because Crosser puts the flow and flow-definition IDs in the deploy path (/api/flowdefinitions/{flowDefinitionId}/flow/{flowId}/deploy), a rule can pin the agent to deploying only the flows you allow.
GET STARTED