New 42-day free trial Get it now
Smarty

Take charge of your API usage with Smarty’s key management features

API key management with Smarty
Updated November 4, 2025
Tags
API key management with Smarty

Ever wondered, “Where did all my lookups go?!” Without proper API management, you may burn through your lookups quicker, experience runaway code, and encounter unexpected usage.

That’s why Smarty created usage by key (included in all annual plans) and limit by key (included in some plans; you can add them by contacting sales) for its APIs.

Why key management matters

Common API usage challenges (problems to solve):

  • Unexpected spikes in lookups
  • Difficulty tracking specific key usage
  • Which keys are calling which Smarty license
  • Need for better control over API consumption
  • Difficulty allocating Smarty lookups across an organization

With Smarty's key management features, you gain more control by having better visibility of your usage, eliminating the element of surprise (you know, the bad kind, like when you’re suddenly out of lookups).

Usage by key

Usage by key is a report that allows you to track lookup usage per key, providing insights into individual key activity and Smarty license access. It helps you monitor and manage API consumption per key, optimize costs, detect anomalies (like runaway code), and allocate resources effectively. 

Usage by key is included in every Smarty annual subscription for every API product.

To access usage reports by key

  1. Log in to your Smarty account and navigate to the API Key section.
  2. Locate the “Usage by Key” button, select a single key or all keys, a date range, and export the report.

You can run a usage report showing every key to see which lookups are used and when. 

The report includes the key, label, license, day (per hour), and look-ups (count per hour). It lets you see how you’re using/consuming Smarty APIs for reporting and investigating.

Limit by key

By setting a limit on a key, you can enhance your security. Instead of creating multiple accounts to manage lookup limits, you can set a limited number of lookups per key and manage them all from one place. The account owner can modify, remove, or reset the limit at any time, so you’re always in control.

Limit by key may already be included in your plan(s) (if it is, you’ll see the button titled "Add Limit"). If you want to add the limit by key capability, contact your Customer Success Manager or Account Executive. 

With limit by key, you can also set lookup caps to prevent overuse. That means:

  • No more runaway code eating up your lookups
  • No more partners or team members going overboard
  • No more surprises—just total control

You should always get what you pay for. Smarty’s API management features, usage by key, and limit by key, give you more control and better visibility, so there are no more surprises. Your teams are going to love you. 

Learn more

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly
Arrow Icon
SDK authors live in a permanent tug-of-war:Users want a simple constructor they can paste and ship. Maintainers want room to grow without breaking everybody’s build on the next release. That second part matters a lot right now, because a lot of people are still relatively early in their software careers. Approximately one in three developers has coded professionally for four years or less. That matters because unclear or fragile APIs disproportionately hurt newer developers—they don’t have scars yet.
Ambiguous address matches: What they are and why compliance teams should care
Arrow Icon
If you’ve ever run into an address that seems to exist in more than one place, congratulations—you’ve discovered the world of ambiguous address matches. They’re the Schrödinger’s cat of location data: valid, yet potentially two distinct locations. This blog will focus on a few key things: What are ambiguous address matches?Why ambiguous address matches matter for compliance and customer serviceHow to handle matches with address ambiguityWhy you should inform your customers of ambiguous address matchesOur final thoughts on ambiguous address matchesWhat are ambiguous address matches?An ambiguous address match occurs when an entered address resolves to two or more valid locations with slight but meaningful differences.
Smarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocoding
Arrow Icon
OREM, UT, Jan 27, 2026—Smarty®, an expert in address data intelligence, today announced a three-part release designed to help organizations turn messy, fast-changing location data into operational confidence. The January 2026 bundle introduces: 1) A brand-new parcel dataset, 2) Expands provisional address programs into core U. S. products, and 3) Upgrades Smarty’s International Geocoding engine—giving organizations more precision and more usable signals for automation at scale. “Address data is never ‘done.

Ready to get started?