2.05.2.05 - 2.05 - Single Message - Teradata Listener

Teradata® Listener™ User Guide

prodname
Teradata Listener
vrm_release
2.05
category
User Guide
featnum
B035-2910-039K

This endpoint is designed to accept a single message and pass it through Listener. No transformation or splitting of the message occurs. Call this endpoint each time you want to send a single message.

Definition

POST https://CLUSTER.DOMAIN/listener/ingestservices/message HTTP/1.1
Authorization: token SOURCE_SECRET_KEY
Content-Type: application/json
Sync: 1
Header Required Sample Value Description
Authorization Required Source Secret key Determines to which source the data is sent.
Sync Optional 1 Requests a UUID from Ingest to ensure Kafka accepted the message. Value must be 1 for synchronous.

Example Request

curl \
  -H "Content-Type: application/json" \
  -H "Authorization: token 0f6fd50e-9515-4730-92c0-2360b5af56d3" \
  -H "Sync: 1" \
  -X POST -d '{"testing":"123"}' \
  -i \
  https://CLUSTER.DOMAIN/listener/ingestservices/message HTTP/1.1

Example Response

HTTP/1.1 201 Created
Content-Type: application/json
{"uuid":"15183245f6e0242ac11000000"}

Response Codes

Code Description
201 Message successfully received.
401 Authorization header not found.
500 Message body could not be read or Kafka could not be reached.
502 Bad Gateway.
503 Service unavailable.
504 Gateway timeout.
See the system administrator for frequent responses of 502, 503, or 504. You may need to scale up ingest services or check to see if ingest services are up and running.