Crosser Control Center API

Name: Crosser Control Center API API
Brand: Crosser Control Center API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer16 EndpointsREST

For Agents

Authenticate, manage edge nodes, deploy data flows, and query events on Crosser Control Center installations.

Quickstart

Get started with Crosser Control Center API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy a flow to a Crosser edge node"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Crosser Control Center API API.

Authenticate users against Crosser Control Center and obtain a JWT bearer token via /api/authentication/login

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

GET STARTED

Start building with Crosser Control Center API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Crosser Control Center API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Crosser Control Center API 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

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Crosser email/password and the resulting JWT bearer token are stored encrypted in the Jentic vault. Agents receive scoped execution tokens, and Jentic handles the login exchange and Authorization header injection so raw credentials never enter the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'deploy a flow to a Crosser edge node' or 'list Crosser events' and Jentic returns the matching Control Center operation with its input schema, removing the need to read Crosser's user guide.

Time to first call

Direct Crosser integration: 1-2 days for JWT login flow, edge node management, and deploy automation. Through Jentic: a few hours — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cronitor API

Cronitor monitors the scheduled jobs that may sync data to Crosser edge fleets

Pair Cronitor with Crosser to verify scheduled flow deploys and data sync jobs actually fired.

Complementary

Cron-job.org API

cron-job.org schedules recurring HTTP calls that can hit Crosser deploy or events endpoints

Use cron-job.org to schedule a recurring Crosser events poll when an agent doesn't have its own scheduler.

Complementary

crowd.dev API

crowd.dev tracks community signals while Crosser handles industrial edge data integration

Use crowd.dev for community data ingestion patterns; Crosser handles the OT/edge side of the same data fabric.

FAQs

Specific to using Crosser Control Center API 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 at https://app.jentic.com/sign-up.

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.