Publish message
POST/messages/publication
Publishes a single message. Messages are published to specific partitions computed from their correlation keys. The endpoint does not wait for a correlation result. Use the message correlation endpoint for such use cases.
Request
- application/json
Body
required
The name of the message.
The correlation key of the message.
Timespan (in ms) to buffer the message on the broker.
The unique ID of the message. Only useful to ensure only one message with the given ID will ever be published (during its lifetime).
variables objectnullable
The message variables as JSON document.
Additional properties allowed.
The tenant of the message sender.
Responses
- 200
- 400
- 500
The message was published.
- application/json
- Schema
- Example (from schema)
Schema
The key of the message
The tenant ID of the message.
{
"messageKey": 0,
"tenantId": "string"
}
The provided data is not valid.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
An internal error occurred while processing the request.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}