30-day free trial on all Orbit apps — no credit card required
Start trialEdge API Gateway turns any Orbit BPI process flow into a callable API endpoint — with consumer management, per-key rate limits, IP allowlists, real-time traffic logs, and auto-generated developer docs included.
30-day free trial · No credit card required
Any process flow becomes a public or partner-scoped REST endpoint
Rate limits, quotas, and IP rules enforced individually per consumer
Every API call logged — timestamp, consumer, status, latency, payload
OpenAPI developer docs generated from endpoint definitions
Trusted by integration teams worldwide
What Edge API Gateway gives you
From the first endpoint to the hundredth consumer — Edge API Gateway handles security, policy, and observability so your BPI flows stay clean.
01 — Dynamic Endpoints → REST APIs
Turn any Orbit BPI process flow into a callable REST API in seconds. Define the path, method, and target flow — the gateway handles auth, routing, and request validation before the flow ever runs.
02 — Consumer Management & API Keys
Model every external caller as a consumer — link them to a trading partner or enterprise application in your TPM address book. Issue multiple named API keys per consumer so production and staging stay separate, and revoke individual keys without touching the others.
03 — Endpoint Policies
Every endpoint gets its own policy set. Cap requests per minute and daily quota at both the endpoint and consumer level. Enforce IP allowlists, max payload sizes, allowed content types, and idempotency keys — no middleware code required.
04 — Real-Time Traffic Monitoring
Watch every API call as it happens. The traffic log shows the endpoint, consumer, HTTP method, response code, latency, and source IP for each request. Filter by status (200, 429, 500), consumer, or time range. The dead-letter queue captures failed calls so nothing disappears silently.
Auto-generated
Every endpoint you define in Edge API Gateway automatically becomes a browsable documentation page for your consumers. They get schema views, curl examples, status code explanations, and a try-it interface — without a single line of documentation YAML from your side.
How it connects
Edge API Gateway sits at the boundary between the outside world and your Orbit BPI process flows. External partners, client apps, and internal services call the gateway URL. The gateway checks the API key, enforces the policy, and fires the process flow. BPI maps, transforms, and routes the payload — just like any other trigger.
External caller hits the gateway URL
With their API key in the Authorization header.
Gateway validates key, consumer, and policy
Rate limit, quota, IP allowlist, payload guard — in milliseconds.
BPI process flow executes
Source connection → mapping → target connection, same as any other trigger.
Response returned, call logged
Visible in Traffic Monitor. Failures go to the dead-letter queue.
Dynamic Endpoints
Process flow triggers
Orbit BPI
Mapping & orchestration
Orbit Monitoring
Transaction visibility
90-second tour
Watch how to expose a BPI process flow as a REST endpoint, issue an API key, set a rate-limit policy, and call the API — all from within the Orbit platform.
These are the questions teams ask when evaluating API gateway solutions for enterprise integration, B2B API exposure, and policy-controlled external access to internal process flows.
An Edge API Gateway sits at the perimeter of your integration platform, exposing internal process flows and services as secure, policy-controlled REST endpoints. ORBIT Edge API Gateway ties directly into BPI process flows, so you can expose any integration as an API without building a separate service layer.
Each endpoint can have its own policy: requests per minute, daily quota, IP allowlist, max payload size, allowed content types, and idempotency key requirements. Consumer-level overrides let you give premium partners higher limits without changing the base policy.
Yes. ORBIT Edge API Gateway lets you create consumers (mapped to trading partners or enterprise applications) and issue multiple named API keys per consumer. Keys can expire, be revoked, and carry their own rate limits.
Yes. Every call is logged with timestamp, endpoint, consumer, HTTP method, response code, latency, and IP address. A dead-letter queue captures failed calls for investigation. Request body logging can be set to FULL, REDACTED, or NONE per policy.
Yes. ORBIT Edge API Gateway automatically generates an OpenAPI-compatible developer documentation portal from your endpoint definitions. Consumers get a browse-and-try interface with curl examples, request/response schemas, and status code explanations.
Start a free trial, expose a BPI process flow as an API endpoint, issue your first consumer API key, and watch the first call land in the traffic log — in under 30 minutes.
Cookies and browser updates
We use cookies for analytics. Accepting will also ask your browser whether CINTAP can send product updates.