What’s your API’s “Time To 200”?
shkspr.mobi
What’s your API’s “Time To 200”?
1–10 of 90 posts
Re: What’s your API’s “Time To 200”?
#2It always boggles my mind when I try to use a new API and I have to jump through a hundred hurdles to start using it.
Let me use your service and start paying you!
In the ocean of bad APIs out there I'll pick yours if you can offer:
1. An easy process to onboard
2. Good documentation
3. Usage based pricing
Re: What’s your API’s “Time To 200”?
#3It always boggles my mind when I try to use a new API and I have to jump through a hundred hurdles to start using it. Let me use your service and start paying you! In the ocean of bad APIs out there I'll pick yours if you can offer: 1. An easy process to onboard 2. Good documentation 3. Usage based pricing
If you have some kind of pricing model I understand the basic email validation and possibly getting a payment method up-front. It's too easy to program around a simple usage cap.
Re: What’s your API’s “Time To 200”?
#4It always boggles my mind when I try to use a new API and I have to jump through a hundred hurdles to start using it. Let me use your service and start paying you! In the ocean of bad APIs out there I'll pick yours if you can offer: 1. An easy process to onboard 2. Good documentation 3. Usage based pricing
Maybe we should collect some good and bad examples here. Personally I dislike the onboarding situation at Twilio, their documentation is good though. Mailjet has good documentation and decent onboarding.
Re: What’s your API’s “Time To 200”?
#5It always boggles my mind when I try to use a new API and I have to jump through a hundred hurdles to start using it. Let me use your service and start paying you! In the ocean of bad APIs out there I'll pick yours if you can offer: 1. An easy process to onboard 2. Good documentation 3. Usage based pricing
If you have some kind of pricing model I understand the basic email validation and possibly getting a payment method up-front. It's too easy to program around a simple usage cap.
Having a fake/temporary/nonpersistent/whatever-makes-sense instance one can quickly test in swagger or similar tools just to get a feel would be nice, though.
Re: What’s your API’s “Time To 200”?
#6“Time to 200”? Why not “Zero to 200”? Feels closer to the car simile
Re: What’s your API’s “Time To 200”?
#7“Time to 200”? Why not “Zero to 200”? Feels closer to the car simile
Lots of people don't drive cars. I figured most programmers would be familiar with "Time To Live" (TTL).
Re: What’s your API’s “Time To 200”?
#8I like to think that we’re doing okay with geocod.io, but I would seriously love some feedback. Should we automatically generate your first API key? Make docs more prominent? Anything else?
Re: What’s your API’s “Time To 200”?
#9“Time to 200”? Why not “Zero to 200”? Feels closer to the car simile
Lots of people don't drive cars. I figured most programmers would be familiar with "Time To Live" (TTL).
I thought it was a reference to “Time to Interactive”.
https://web.dev/interactive/
Re: What’s your API’s “Time To 200”?
#10“Time to 200”? Why not “Zero to 200”? Feels closer to the car simile
Lots of people don't drive cars. I figured most programmers would be familiar with "Time To Live" (TTL).
0-100, as a concept, maps closer to your idea. I knew about TTL, but didn't make the connection until you pointed it out.