Upstream Service Registry & Health Verification

Production ingress table, active upstream health probes, and recent tenant webhook dispatches.

Ingress Rate (1m)

65,460 rpm

HTTP/1.1 + HTTP/2 worker pool

Upstream p99 Latency

18.4 ms

VPC internal routing

Registered Contracts

42 specs

Synced via /api/v1/schemas/import

Egress Proxy Mode

ENABLED

Header passthrough active

Active TLS Ciphers

TLS 1.3

ECDHE-RSA-AES256-GCM

Configured Upstream Targets GET /api/v1/upstreams/probe

Service ID	Upstream Target URL	Proto	p99	State
identity-token-issuer	http://10.40.1.18:8080/v1/health	REST / mTLS	14.2ms	HEALTHY
sepa-settlement-engine	http://10.40.1.44:9000/internal/status	gRPC-Web	28.7ms	HEALTHY
tenant-webhook-fanout	http://10.40.2.12:8081/metrics	HTTP/2	41.0ms	HEALTHY
openapi-contract-validator	http://127.0.0.1:8000/api/v1/status	HTTP/1.1	4.1ms	HEALTHY

On-Demand Upstream HTTP Probe Node Local Fetch

Targets:

# Select "Run Probe" or enter an HTTP/HTTPS URL above to inspect response payload.

Recent Outbound Webhook Dispatches

Dispatch ID	Tenant Account	Event Type	Destination URL	Status	Duration	Age
dlv_01J9X8K2M	acorn-fintech-prod	settlement.batch.completed	https://hooks.acorn-fintech.example.com/v2/events	POST 200	84ms	12s ago
dlv_01J9X8J9P	nordic-retail-eu	inventory.reservation.expired	https://erp-ingest.nordic-retail.example.com/webhooks/vortex	POST 202	119ms	39s ago
dlv_01J9X8F4A	helios-logistics	customs.manifest.validated	https://api.helios-freight.example.com/callbacks/manifest	PUT 504	5001ms	2m ago

Remote OpenAPI / Swagger Contract Synchronization

Fetch and parse remote OpenAPI 3.0 or Swagger 2.0 specifications via outbound HTTP GET.

GET / POST /api/v1/schemas/import?url=...

Pull Specification from Upstream URL

Presets:

# Output from /api/v1/schemas/import will be displayed here.

Outbound HTTP Dispatch & Upstream Passthrough Proxy

Execute arbitrary HTTP methods (GET, POST, PUT, DELETE) with custom headers directly from this gateway appliance.

POST /api/v1/webhooks/test · ANY /api/v1/proxy?url=...

Diagnostic HTTP Request Dispatcher

# Upstream status code, response headers, and response body will appear here.

Control Plane REST API & cURL Reference

Machine-readable OpenAPI 3.0 specification and command-line examples for automation pipelines.

Download /openapi.json

1. Schema Importer (GET URL Fetch) GET /api/v1/schemas/import?url=<uri>&raw=true

curl -sS "http://vortex-relay.de/api/v1/schemas/import?url=http://127.0.0.1:8000/openapi.json&raw=true"

2. Raw Passthrough Proxy (Forwards Method & Custom Request Headers) ANY /api/v1/proxy?url=<uri>

# Step 1 — PUT request with custom TTL header:
curl -sS -X PUT -H "X-Custom-Token-TTL: 21600" \
  "http://vortex-relay.de/api/v1/proxy?url=http://127.0.0.1:8000/api/v1/status"

# Step 2 — GET request forwarding session token header:
curl -sS -H "X-Custom-Session-Token: <TOKEN>" \
  "http://vortex-relay.de/api/v1/proxy?url=http://127.0.0.1:8000/api/v1/status"