API or database
When to call the InternetData API and when to download its databases: freshness, latency, volume, what each answers and what each costs.
Both carry the same data. They differ in where the lookup runs.
| API | Databases | |
|---|---|---|
| Where it runs | Our servers, one request per lookup | Yours, in memory |
| Latency | A few tens of milliseconds, plus the network | Microseconds |
| Freshness | Our current data | As of your last download; most rebuild daily |
| What it answers | Every field your plan includes, in one answer | One dataset per file, joined by you |
| Pricing | A plan's monthly lookups | A license per database |
| Best for | Sign-ups, logins, checkouts and other single decisions | Logs, analytics, firewalls and very high volume |
Most integrations start with the API and move a high-volume path to a database later. The SDKs and the databases each have a quickstart.