EventHubQ

Connectivity

This page is your production connectivity cockpit (SSO, APIs, AWS SES + scanners, SMS). Most actions require a one-time CONNECTIVITY_ADMIN_KEY.

HomeBillingAPI Swagger

Config (public)

{
  "auth": {
    "authority": "https://76983185-a73d-4820-b842-ee6f054f2308.ciamlogin.com/76983185-a73d-4820-b842-ee6f054f2308/v2.0",
    "knownAuthority": "76983185-a73d-4820-b842-ee6f054f2308.ciamlogin.com",
    "clientId": "3f02f0a1-d75c-4849-8527-f831aca41f6d",
    "scopes": [
      "api://4178a05b-d580-4ee0-be61-333272f51f74/eventhubq.read",
      "api://4178a05b-d580-4ee0-be61-333272f51f74/eventhubq.write"
    ]
  },
  "api": {
    "eventHubQBaseUrl": "https://eventhubqapi0.azurewebsites.net",
    "tenantHeaderName": "X-Tenant-Id"
  },
  "billing": {
    "identityBillingBaseUrl": "https://softtelidentitybillingapi.azurewebsites.net"
  },
  "stripe": {
    "publishableKeySet": true
  }
}

Connectivity Admin Key

Set CONNECTIVITY_ADMIN_KEY in Vercel env vars. Enter the same value here to use the email/SMS/scanner test endpoints.

EventHubQ API health

Not checked
—

/v1/me (token + API)

Requires login
—

SoftTelIdentityBillingApi

Not checked
—

AWS STS (credentials)

Not checked
—

AWS SES quota

Not checked
—

AWS SES send test email

Sends a single test email (restricted by env).
—

Text scan (AWS Comprehend)

Validates the scanner connectivity (template body).
—

Image scan (AWS Rekognition)

Scans an image already stored in your S3 bucket.
—

Upload a test image to AWS_S3_BUCKET, then paste its key here.

Template URL allowlist (engine)

Pre-validates that templates contain only allowlisted links.
—

Set optional env LINK_ALLOWLIST_DOMAINS (comma separated).

SMS send (Azure Communication Services)

Sends a single test SMS (restricted by env).
—

AWS S3 presign (PUT)

Creates a presigned PUT URL (connectivity test).
—

Next steps

  • Put all secrets in Vercel env vars (server-side). Only NEXT_PUBLIC_* are exposed to the browser.
  • After connectivity is stable, we move email/SMS sending + scanning into the EventHubQ API (server-side), leaving the web app as UI only.
  • For production: remove/disable these connectivity endpoints or rotate CONNECTIVITY_ADMIN_KEY.