# Pub Sub ## Publish a message to a given topic This endpoint lets you publish data to multiple consumers who are listening on a ```topic```. Dapr guarantees at least once semantics for this endpoint. ### HTTP Request ```http POST http://localhost:/v1.0/publish// ``` ### HTTP Response codes Code | Description ---- | ----------- 200 | Message delivered 500 | Delivery failed ### URL Parameters Parameter | Description --------- | ----------- daprPort | the Dapr port pubsubname | the name of pubsub component. topic | the name of the topic > Note, all URL parameters are case-sensitive. ```shell curl -X POST http://localhost:3500/v1.0/publish/pubsubName/deathStarStatus \ -H "Content-Type: application/json" \ -d '{ "status": "completed" }' ``` # Optional Application (User Code) Routes ## Provide a route for Dapr to discover topic subscriptions Dapr will invoke the following endpoint on user code to discover topic subscriptions: ### HTTP Request ```http GET http://localhost:/dapr/subscribe ``` ### URL Parameters Parameter | Description --------- | ----------- appPort | the application port ### HTTP Response body A json encoded array of strings. Example: ```json [ { "pubsubname": "pubsub", "topic": "newOrder", "route": "/orders" } ] ``` > Note, all subscription parameters are case-sensitive. ## Provide route(s) for Dapr to deliver topic events In order to deliver topic events, a `POST` call will be made to user code with the route specified in the subscription response. The following example illustrates this point, considering a subscription for topic `newOrder` with route `orders` on port 3000: `POST http://localhost:3000/orders` ### HTTP Request ```http POST http://localhost:/ ``` > Note, all URL parameters are case-sensitive. ### URL Parameters Parameter | Description --------- | ----------- appPort | the application port path | route path from the subscription configuration ### Expected HTTP Response An HTTP 200 response with JSON encoded payload body with the processing status: ```json { "status": "" } ``` Status | Description --------- | ----------- SUCCESS | message is processed successfully RETRY | message to be retried by Dapr DROP | warning is logged and message is dropped For empty payload responses in HTTP 2xx, Dapr assumes `SUCCESS`. The HTTP response might be different from HTTP 2xx, the following are Dapr's behavior in different HTTP statuses: HTTP Status | Description --------- | ----------- 2xx | message is processed as per status in payload (`SUCCESS` if empty; ignored if invalid payload). 404 | error is logged and message is dropped other | warning is logged and message to be retried ## Message Envelope Dapr Pub/Sub adheres to version 1.0 of Cloud Events. ## Related links * [How to consume topics](https://github.com/dapr/docs/tree/master/howto/consume-topic) * [Sample for pub/sub](https://github.com/dapr/quickstarts/tree/master/pub-sub)