Notifications and queues

Manage topic and queue records, send SMTP-backed email, and understand which delivery paths are simulated.

Open Notifications and Queueing

Work with the console

  1. Open Notifications and Queueing and select Topics, Queues, or Templates.
  2. Create the required resource, review its settings, and use its returned resource ID for API requests.
  3. For topics, configure and confirm subscriptions before publishing. For queues, send a small message and inspect the receive result.
  4. Inspect the returned delivery results and the actual recipient or destination before relying on a notification.

Delivery availability

  • POST /api/notifications/send calls the configured SMTP mail service for email. Check deliveryResults; an accepted response can still contain a channel failure.
  • The SMS and push branches of that endpoint simulate delivery. Its webhook branch records a simulated result without making an HTTP delivery request.
  • The topic publish endpoint creates message records and simulates delivery-state changes. DELIVERED on that path is not evidence that a recipient received a message.

Queue behavior

Send stores a message record. Receive selects SENT records, marks them RECEIVED, and returns message identifiers, body, attributes, and a receipt handle. Use the queue ID returned by the create or list request.

The receive handler accepts maxMessages (1–10) and waitTimeSeconds (0–20), but reads immediately. Saved delay, FIFO, deduplication, retention, visibility, and encryption settings do not establish SQS-equivalent processing guarantees. Do not rely on automatic visibility-timeout redelivery or a per-message DELETE API shown in older examples.

SMTP email example

Configure SMTP on the deployment before sending. The recipient can be provided in routing.email or override.email; otherwise the endpoint uses the authenticated account email. Supply the message object inside the message field.

{
  "message": {
    "subject": "Connection check",
    "text": "A test from Genorbex"
  },
  "routing": {
    "method": "single",
    "channels": [
      "email"
    ],
    "email": "recipient@example.com"
  }
}

API endpoints

Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.

GET /api/notification-queueing/topics

Lists visible topic records.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

POST /api/notification-queueing/messages/publish

Creates topic message records and simulates their delivery states.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

Example JSON body

{
  "topicId": "YOUR_TOPIC_ID",
  "message": "Connection check"
}

GET /api/notification-queueing/queues

Lists accessible queue records.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

POST /api/notification-queueing/queues

Creates a queue record with required attributes.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

Example JSON body

{
  "name": "example-queue",
  "attributes": {}
}

POST /api/notification-queueing/queues/{queueId}/send

Enqueues a message record.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

Example JSON body

{
  "messageBody": "Connection check"
}

POST /api/notification-queueing/queues/{queueId}/receive

Reads SENT records and marks them RECEIVED.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

Example JSON body

{
  "maxMessages": 1,
  "waitTimeSeconds": 0
}

POST /api/notifications/send

Sends configured SMTP email or executes the simulated channel branches; inspect deliveryResults.

Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.

Need help with your setup? Visit the Help Center or contact Genorbex.