Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What’s your API’s “Time To 200”?

shkspr.mobi

Post reply on HN
Print view View original

81–90 of 90 posts

Re: What’s your API’s “Time To 200”?

#81

Post by StavrosK »

256DEV wrote: post #59
Kiro wrote: post #39

Earlier quoted context omitted.

> I'm not sure how I could further improve the current flow Remove 1 and 2.

So I actually do have a version of my API that doesn't require any sign up at all for the users that prefer this! You can see it here: https://www.exchangerate-api.com/docs/free That said, as much as some users want an open endpoint with zero authentication there are many others who want an actual account, commercial support, high availability, more features etc. These users are also the ones that pay for development…

Yes but you can let users sign up with their API token at any later time.

Re: What’s your API’s “Time To 200”?

#82

Post by SomeInterwebDev »

bpicolo wrote: post #72
SomeInterwebDev wrote: post #71

Zero for us at http://api.case.law because most of our endpoints don't require registration. Getting case text does require fast free registration, though.

Thanks for the link - this is super cool! I definitely plan to explore.

Yay! Reach out through the contact form/email with any questions! The docs are at: https://case.law/docs/

Re: What’s your API’s “Time To 200”?

#83

Post by awalias »

At Supabase we have tracked “Time to first query” from the start, which includes things like signing up, provisioning a database, creating a schema, adding supabase-js to your app, and querying your data for the first time

We generalised it over time to “time to value” for anything that isn’t onboarding/data-fetching

Re: What’s your API’s “Time To 200”?

#84

Post by sagarpatil »

256DEV wrote: post #67
raverbashing wrote: post #64

Is there anyone that does API management as a service? Something that would consolidate account, tokens, billing, tracking, firewalling etc of an API? Somewhere where one could plug their api and monetize it easily?

RapidAPI. You can consume multiple API's from one account and as a developer it's a good way to monetize an API if there isn't too much competition in your niche. Not sure what you mean by firewalling but RapidAPI does authenticate their requests to your endpoint so as a developer you can do access control in this way.

Yep. Can vouch for RapidAPI.

Re: What’s your API’s “Time To 200”?

#85

Post by simonw »

I frequently evaluate APIs. If you want me to use your API, getting me to a point where I've seen it actually running against some data that I typed in is really important. So give me an API explorer, rate-limited by IP, that lets me click an example link from your documentation and see an actual response.

Re: What’s your API’s “Time To 200”?

#86

Post by aszen »

dragonwriter wrote: post #35
aszen wrote: post #26

Earlier quoted context omitted.

famous example of this, are most of the aws api's that because of their signing features and hashes can really only be called sanely from an sdk. such a pain to debug, i'm not sure why they have such signing features. is it for security

> is it for security Yes. EDIT: specifically, it is do intercepting a request doesn’t allow you to issue new requests.

Isn't that what https provides. Or were the APIs creates before https was popular

Re: What’s your API’s “Time To 200”?

#87

Post by vishwajeetv »

seanp2k2 wrote: post #54
Spivak wrote: post #24

Earlier quoted context omitted.

Looking at you literally all of AWS .

To be fair, it’s not like the GCP APIs are much easier to use. It’s probably the right thing for infra and payment services to have a higher bar for API security, plus they’re hugely complex and usually used as an SDK. That said, I haven’t been very impressed with the Google API dev experience. Example: I was just trying to post some timing data to Google Analytics via Go, and the documented example didn’t work in ad…

If you are trying to pass custom json to GA, simply you can't do that. You would have to use Firebase analytics to send custom JSON. For GA, all the data that is passed must fall under these types, categories, actions, labels (and value)

Re: What’s your API’s “Time To 200”?

#88

Post by stkdump »

256DEV wrote: post #25

I've put a fair amount of work into getting this exact time as low as possible for my exchange rates API [1]. I've noticed slightly better conversion each time I've taken a major step out of the process. I've specifically eliminated some of the steps this article cites in its example of a tedious flow - for instance I changed user accounts to be confirmed by default and then only disable them retroactively if a user…

For a more professional look, use higher res or vector graphics. Parts of the page (including the fixed header) look blurry, even on my phone with a relatively moderate by todays standards 1024px wide screen. I might be very particular about this, but I find it almost painful to look at the page for this reason.

Re: What’s your API’s “Time To 200”?

#89

Post by j16sdiz »

aszen wrote: post #86
dragonwriter wrote: post #35

Earlier quoted context omitted.

> is it for security Yes. EDIT: specifically, it is do intercepting a request doesn’t allow you to issue new requests.

Isn't that what https provides. Or were the APIs creates before https was popular

The use case is different.

For example, S3. S3’s authentication scheme allow you create a limited used download link and passing to a untrusted user

Re: What’s your API’s “Time To 200”?

#90

Post by treve »

dylan604 wrote: post #37
treve wrote: post #28

Earlier quoted context omitted.

Or even better: allow me to paste the url in a browser and get a meaningful result.

How does that work for authenticated requests?

The same way you would build any login system for a browser application.
Post reply on HN