Subscribe to updates in The Mercure protocol

What this operation does

Subscribe to updates

• GETReads datamercure.local/.well-known/mercure

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which The Mercure protocol operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other The Mercure protocol operations

• Publish an updatePOST · changes data
• Active subscriptionsGET · reads data
• Active subscription for the given topic and subscriberGET · reads data
• Active subscriptions for the given topicGET · reads data

All 5 The Mercure protocol operations

Questions

Can HumDay subscribe to updates in The Mercure protocol?

Yes. This operation is published in The Mercure protocol's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my The Mercure protocol account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in The Mercure protocol.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your The Mercure protocol account.

Where this came from

Read from a published API description for The Mercure protocol at raw.githubusercontent.com/dunglas/mercure/main/spec/openapi.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.