Congratulations on your launch, and for providing a public utility :-) I would love to see metrics on how hard the wild Internet makes your python and PG work,

Congratulations on your launch, and for providing a public utility :-) I would love to see metrics on how hard the wild Internet makes your python and PG work, if you wanted to create /stats.html one day in the future It wasn't clear if you wanted commentary here, or via your contact form, so ... I was surprised that the JWT is being sent as a POST param, instead of its more traditional place in an Authorization header Kind of related, kind of not: I was also surprised to see the API request include the accountId in the URI when it's present in the JWT -- is that an implementation concession allowing a future where one AccountId (from the auth perspective) is able to control multiple "{accountId}" URIs? Definitely related to that: I was surprised to see the QueuesList response send back what I presume is the same accountid that was present in the URI, repeated for every QueueName I think the MessageReceive example copy-pasted the "MessageBody" field from its MessageSend friend, and the MessageDelete example is missing its "ReceiptHandles" that is mentioned in the description Good luck on your adventure!