Hey @Ricardo,  I don't disagree with you, the reason we're using GET/POST in this particular way is because we modeled after WebSub. I'd like to leave the current use of these HTTP methods as is.  We do have this statement in the overview: >is modeled on the  W3C WebSub RFC , such as its use of GET vs POST interactions and a Hub for managing subscriptions.  And this related callout: >NOTE The spec uses GET vs POST to differentiate between the confirmation/denial of the subscription request and delivering the content. While this is not considered "best practice" from a web architecture perspective, it does make implementation of the callback URL simpler. Since the POST body of the content distribution request may be any arbitrary content type and only includes the actual content of the document, using the GET vs POST distinction to switch between handling these two modes makes implementations simpler. Any concerns? Isaac