stacks-blockchain-api icon indicating copy to clipboard operation
stacks-blockchain-api copied to clipboard

Published 20 hours ago • verified publisher icon hirosystems

Updating stacks webhook routes

Open lgalabru opened this issue 4 years ago • 4 comments

What's our take on updating the API routes and go with something more REST compliant? /new_mempool_tx -> /mempool_tx/new /new_block-> /block/new /new_burn_block -> -> /burn_block/new

I was also thinking about maybe prefixing these endpoints with stacks or something (so stacks/blocks/new, etc). Thoughts?

lgalabru avatar Nov 25 '20 18:11 lgalabru

@zone117x is this still relevant?

agraebe avatar Apr 12 '21 23:04 agraebe

I agree with @lgalabru that the paths names could be improved, but pretty low priority

zone117x avatar Apr 13 '21 09:04 zone117x

this seems related to #744

agraebe avatar Sep 13 '21 15:09 agraebe

It appears the overall API nouns/verbs, primitives, and naming conventions could benefit from an uplift. This could feed into major refactoring, though, and we have to carefully navigate, not breaking the existing APIs. That would be to keep the old APIs (but deprecate them) and open up the newly refreshed API endpoints.

All that to say, it is not impacting the end-users or directly adds value yet. Agree with @zone117x to keep this on the back burner for now.

sabbyanandan avatar Mar 04 '22 19:03 sabbyanandan