Frequently Asked Questions

FFL Bridge is an API, embeddable widget, and WooCommerce plugin for adding verified FFL dealer selection to checkout. Customers search by ZIP code and choose an eligible receiving dealer.

The nationwide directory is built from official ATF Federal Firearms License records. Checkout search is a separate, narrower network that requires an active dealer, transfer acceptance, and a current verified license record.

The directory covers nationwide ATF license records, including dealer, pawnbroker, manufacturer, and other license types. Checkout search is narrower because a dealer must also accept transfers and have a current verified license on file.

No. FFL Bridge is built for online firearms retailers and e-commerce platforms. You don't need your own FFL to use the API. Your customers use it to find a licensed dealer near them to receive their purchase.

There are three supported paths: a drop-in browser widget, the REST API for custom workflows, and the maintained WooCommerce plugin. Browser widgets use domain-restricted publishable keys; backend and plugin integrations use private server keys.

WooCommerce has a maintained plugin. Custom storefronts can use the REST API or, where the platform permits custom JavaScript, the origin-bound browser widget. Confirm your platform allows the required checkout customization before choosing the widget path.

Yes. Browser keys require at least one allowed domain and are limited to dealer search. Server keys are private credentials for backend and plugin integrations and can also use optional domain restrictions.

Yes. You can add multiple domains to a single API key, or create separate API keys for each site. There's no per-site fee. Your usage is metered by total API calls across all keys, not by how many sites you run.

Yes. The widget is fully responsive and works on phones, tablets, and desktops. The map and dealer list adapt to the available screen size.

The widget supports maintained dark and light themes. For a fully custom presentation, use the REST API and render the selection interface in your own storefront.

Search uses geographic pre-filtering and distance calculations, but FFL Bridge does not publish an unverified latency guarantee. Measure the preview and production API from your own storefront region before setting a checkout performance budget.

You can search by ZIP code, city/state, or exact lat/lng coordinates. Additional filters include radius (default 25 miles), limit (number of results), and whether the dealer accepts transfers.

Include your API key in the Authorization header as "Bearer YOUR_KEY" or in the X-API-Key header. API keys are never accepted in a query parameter.

Rate limits depend on your plan. Free tier: 100 calls/day (hard limit). Paid plans have daily call allowances; private server keys can continue with overage, while browser keys stop at the allowance. Usage resets at midnight UTC each day, and there are no per-second burst limits.

On the free tier, requests are blocked after the daily limit. On paid plans, private server-key calls continue and are recorded for usage-based billing at the published plan rate. Browser-key calls stop at the allowance and never create overage charges.

FFL Bridge is deployed on managed application and database infrastructure. Any contractual availability commitment must be documented in a signed service agreement; the public plans do not currently advertise an uptime SLA.

Yes. The free tier includes 100 API calls per day with full access to the widget and API. It's great for development, testing, or very low-volume sites. No credit card required.

Starter ($29/mo) includes 1,000 calls/day, Growth ($79/mo) includes 10,000 calls/day, and Pro ($199/mo) includes 100,000 calls/day. Paid server-key calls above the included allowance use the overage rate shown on the live pricing page; browser keys stop at the allowance.

No. Pricing is based on total daily API calls, not the number of sites. You can use your account on as many websites as you want.

Yes. No contracts, no cancellation fees. Cancel from your dashboard and you'll retain access through the end of your billing period.

Not yet, but we're considering it. Reach out if you're interested and we can work something out.

Monthly. We pull the latest ATF FFL records and reconcile them against our database. Expired, revoked, or surrendered licenses are automatically deactivated.

Yes. Dealers can register on FFL Bridge to claim their profile, add transfer fees, update contact info, and mark whether they accept public transfers. Claimed profiles are verified against ATF records.

The widget sends a ZIP code (or location) to our API and receives dealer results. We don't collect personal information from your customers. API call logs include the requesting domain, IP, and query parameters for usage tracking, but no customer PII.

FFL Bridge is a dealer lookup tool, not a compliance platform. We help customers find licensed dealers, but the actual transfer, Form 4473, and background check are handled by the receiving FFL dealer as required by law. Our data comes directly from the ATF's public FFL records.

Use the contact page for account and integration support. Any response-time or availability commitment must be documented in a signed agreement rather than inferred from the public plans.

Yes. Full API docs with endpoints, parameters, response schemas, and code examples are available at fflbridge.com/docs.

Use the contact form or email us at support@fflbridge.com. We'll verify against ATF records and update our database. Dealers can also claim their listing to manage their own information.