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.
Manage topic and queue records, send SMTP-backed email, and understand which delivery paths are simulated.
Open Notifications and Queueing
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.
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"
}
}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.
Lists visible topic records.
Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.
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"
}Lists accessible queue records.
Authentication: Account token or API key accepted by the cloud-service guard, with access to the selected resource.
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": {}
}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"
}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
}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.