|
@patrickc | |||||
|
(Separately, I *also* love the way that errors -- like the one here -- include a debug URL. In addition to helping the developer fix things, access patterns to those URLs give us practical telemetry about what's causing confusion so that we can make improvements.) twitter.com/patrickc/statu…
|
||||||
|
||||||
|
Ashley Brooks
@aabrooks_
|
25. sij |
|
Curious if you’d be willing to share: does Stripe have a team dedicated to awesome API improvements like this or do teams own their own endpoints/APIs and just stick to specific guidelines?
|
||
|
|
||
|
Mathias Hansen
@MathiasHansen
|
25. sij |
|
That’s super awesome! I haven’t really seen any other API’s implement this before. We did something similar recently with a _warnings key. Would love to borrow this idea and link to relevant docs as well geocod.io/docs/#warnings
|
||
|
|
||
|
Peter Boyer
@ptrbyr
|
24. sij |
|
Great error messages demonstrate the maturity of the team implementing the API. Shows understanding of the API state space, failure modes, empathy for users/non-experts, methodical implementation. 🤗🤗🤗
|
||
|
|
||
|
Patrick Breitenbach
@pbreit
|
24. sij |
|
Shouldn't the RESTfulness of APIs obviate the need for client SDKs (at least on some platforms)?
|
||
|
|
||
|
ColDiv
@ColDiv
|
24. sij |
|
The debug url is a simple but brilliant idea
|
||
|
|
||
|
Anwar Z.
@Zianwar_
|
25. sij |
|
React also does this in a smart way, they display warnings in the console and put a reference to that specific error under the /warnings URL path (for e.g reactjs.org/warnings/speci…)
|
||
|
|
||
|
Victor Teodoro
@vjst
|
25. sij |
|
My jaw drops a little more each day in response to the maturity and beauty of stripe's offers.
I work in payments and stripe has been for many years the gold standard.
|
||
|
|
||