COMING SOON: A key will be required for commercial access to the API. Please stay tuned for additional information. If you would like to be notified and obtain a key in advance, include your email address in the header of your API requests to our endpoint.

All commercial API users will need to complete a form to request access. For-profit (commercial) entities must purchase access to the API, while non-commercial users can access it at no cost. All users must adhere to the conditions outlined below.

The RepeaterBook API allows developers access to repeater data. The API is based upon JSON to promote machine data discovery.

The API is located at https://www.repeaterbook.com/api. Please so not try to go to this link without the parameters set below, you will receive an error.

1. Personal Use Only:
   • The use of RepeaterBook data is strictly limited to personal use.
   • Prohibited: Incorporating the data into any commercial product or service for sale, distribution, or any other purpose without prior written permission from RepeaterBook.com.
2. Non-Competition Clause:
   • RepeaterBook data and API must not be used in ways that directly or indirectly compete with RepeaterBook’s web or mobile applications.
   • Applications or services that provide similar functionality or replicate RepeaterBook’s offerings are not allowed.
3. No Redistribution Without Permission:
   • The data may not be included in any app, website, or other medium that is distributed beyond immediate personal use without explicit written consent from RepeaterBook.com.
4. API Use Guidelines:
   • The RepeaterBook API must not be used to duplicate the functionality, methods, or presentations already provided by RepeaterBook.
   • Unordered List ItemUse of the API should complement, not replace, the services offered by RepeaterBook.
5. Attribution Requirement:
   • Any application or website utilizing RepeaterBook data must:
     • Clearly acknowledge RepeaterBook as the source of the data.
     • Provide a visible link to RepeaterBook.com.
6. Mapping and Exporting Tools:
   • RepeaterBook provides mapping and data exporting tools for user convenience.
   • Developing tools that replicate these features is not permitted without prior written authorization.

This Agreement governs all content, documentation, code, and related materials provided through the API. By accessing or using the API or any of its content, you acknowledge and accept the terms outlined in this Agreement.

You are authorized to use the RepeaterBook API to develop services or applications that facilitate searching, displaying, analyzing, retrieving, viewing, or otherwise accessing information derived from FCC data.

You are prohibited from modifying or misrepresenting content obtained through the API while attributing it to RepeaterBook as the source.

Your use of the API is subject to certain limitations on access, calls, or usage as outlined in this Agreement or as otherwise communicated by RepeaterBook. If RepeaterBook reasonably determines that you have attempted to exceed or circumvent these limits, your access to the API may be temporarily or permanently suspended. RepeaterBook reserves the right to monitor your API usage to enhance service quality and ensure compliance with this Agreement.

While specific rate limits are not published, they are set to accommodate normal human interactions. Automated processes, particularly those designed to harvest large volumes of data, will be detected. In such cases, the site administrator will be notified, and access to RepeaterBook.com may be restricted or entirely disabled.

When the rate limit is exceeded, the API will return a 429 Error: “Too Many Requests” response. It is the responsibility of the requesting program to cease further requests to the endpoint upon receiving this error. Failure to comply may result in the API endpoint being permanently disabled for the offending program.

You may terminate this Agreement at any time by ceasing all use of the API. RepeaterBook reserves the right, at its sole discretion, to (1) refuse API access if it determines that your use violates any RepeaterBook policy or (2) terminate or deny access to the API, in whole or in part, for any reason, at any time.

Provisions of this Agreement that, by their nature, should survive termination will remain in effect, including but not limited to warranty disclaimers, indemnity obligations, and limitations of liability.

RepeaterBook reserves the right, at its sole discretion, to modify or replace this Agreement, in whole or in part. Your continued use or access to the API after any changes to this Agreement are posted constitutes your acceptance of the updated terms.

In the future, RepeaterBook may offer new services and/or features through the API. Any new features or services will be subject to the terms and conditions of this Agreement.

The API is provided on an “as is” and “as available” basis. RepeaterBook disclaims all warranties, whether express or implied, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, and non-infringement. RepeaterBook makes no guarantees that the API will be free from errors or that access will be continuous, uninterrupted, or secure.

Under no circumstances shall RepeaterBook be liable, whether under contract, negligence, strict liability, or any other legal or equitable theory, for:

1. Special, incidental, or consequential damages;
2. Costs related to the procurement of substitute products or services; or
3. Interruptions in use, loss of data, or corruption of data.

By using the API, you represent and warrant that:

1. Your use of the API will fully comply with the RepeaterBook Privacy Policy, this Agreement, and all applicable laws and regulations.
2. Your use of the API will not infringe upon or misappropriate the intellectual property rights of any third party.

You agree to indemnify and hold harmless RepeaterBook, its contractors, employees, agents, and affiliates from any and all claims, liabilities, damages, and expenses (including reasonable attorney's fees) arising out of your use of the API, including but not limited to any violation of this Agreement.

This Agreement constitutes the entire understanding between you and RepeaterBook regarding its subject matter. Any modifications to this Agreement may only be made by RepeaterBook through the posting of a revised version on this page.

RepeaterBook's failure to exercise or enforce any right or provision of this Agreement shall not constitute waiver of such right or provision.

All information provided through the API is intended to be open data and is free to use for personal, non-commercial purposes. As a public service from RepeaterBook.com, no fees are charged for accessing this API for typical, non-commercial use. However, RepeaterBook reserves the right to charge a fee for commercial use of the API or its data. Any such usage must be explicitly authorized, and terms will be outlined in a separate agreement.

Reasonable rate limits are in place to prevent abuse and ensure equitable access for all users. While the exact rate limits are not disclosed, they are designed to accommodate typical usage generously. If the rate limit is exceeded, the API will return an error response, and requests may be retried once the limit resets, typically within 5 minutes. Proxies are more likely to reach the limit, whereas direct client requests are less likely to be affected.

All public-facing applications using this API must clearly credit RepeaterBook as the source of the data.

Every request, either by browser or application, sends header information whenever you visit any website. For example, a commonly used header called “UserAgent” tells a website what type of device you are using so it can tailor the best experience for you. No private information is shared in a header, which is standard practice for all sites. Developers can override these headers for specific purposes. You can get full details by visiting the header field definitions page at the World Wide Web Consortium site.

A User Agent is required to identify your application. This string can be anything, and the more unique to your application, the less likely it will be affected by a security event. If you include contact information (website or email), we can contact you if your string is associated with a security event. This will be replaced with an API key in the future.

User-Agent: (Name or URL of your app, valid@myemail.com)

Replace the data with your valid data.

Note: API tokens will be required for continued commercial usage on January 6, 2025.

Endpoints have the JSON default format.

• State ID (FIPS)
• Repeater ID
• Frequency
• Input Frequency
• PL/CTCSS Uplink
• PL/CTCSS TSQ Downlink
• Location/Nearest City
• Landmark
• County (US only)
• State
• Callsign
• Use/Membership
• Operational Status
• ARES
• RACES
• SKYWARN
• CANWARN
• Operating Mode
• AllStar Node
• EchoLink Node
• IRLP Node
• WIRES Node
• DMR Capable
• DMR ID
• DMR Color Code
• D-Star Capable
• NXDN Capable
• P-25 Capable
• P-25 NAC
• M17
• M17 CAN
• Tetra Capable
• Tetra MCC
• Tetra MNC
• Yaesu System Fusion Capable
• YSF Digital ID Uplink
• YSF Digital ID Downlink
• YSF DSC
• Analog Capable
• Notes
• Last Update

All repeaters are identified by a combination of the state ID and the repeater ID. The state ID is based on American National Standards Institute (ANSI) Codes for States

• callsign - Repeater callsign
• city - Repeater city
• landmark
• state_id - State / Province
• country - Repeater country
• county - Repeater county
• frequency - Repeater frequency
• mode - Repeater operating mode (analog, DMR, NXDN, P25, tetra)
• emcomm - ARES, RACES, SKYWARN, CANWARN
• stype - Service type. Only required when searching for GMRS repeaters. ex: stype=gmrs

The format is json - JavaScript Object Notation.

• % - will allow wild card searching

examples

• callsign=kd6% - All callsigns beginning with 'kd6'
• callsign=%kpc - All callsigns ending with 'kpc'
• callsign=kd%kpc - All callsigns beginning with 'kd' and ending with 'kpc'
• callsign=%kp% - All callsigns with 'kp' in them

HTTPS example - US and Canada

https://www.repeaterbook.com/api/export.php?country=United%20States&country=Canada

• ATV repeaters are not included

• State ID (FIPS)
• Repeater ID
• Frequency
• Input Frequency
• PL/CTCSS Uplink
• PL/CTCSS TSQ Downlink
• Location/Nearest City
• Landmark
• Region (if available)
• Country
• Callsign
• Use/Membership
• Operational Status
• Operating Mode
• AllStar Node
• EchoLink Node
• IRLP Node
• WIRES Node
• DMR Capable
• DMR ID
• DMR Color Code
• D-Star Capable
• NXDN Capable
• P-25 Capable
• P-25 NAC
• M17
• M17 CAN
• Tetra Capable
• Tetra MCC
• Tetra MNC
• Yaesu System Fusion Capable
• YSF Digital ID Uplink
• YSF Digital ID Downlink
• YSF DSC
• Analog Capable
• Notes
• Last Update

On Repeaterbook.com, repeaters are identified by a combination of the state ID and the repeater ID.

• callsign - Repeater callsign
• city - Repeater city
• landmark
• country - Repeater country
• region- Repeater region (if available)
• frequency - Repeater frequency
• mode - Repeater operating mode (analog, DMR, NXDN, P25, tetra)

• % - will allow wild card searching

examples

• callsign=kd6% - All callsigns beginning with 'kd6'
• callsign=%kpc - All callsigns ending with 'kpc'
• callsign=kd%kpc - All callsigns beginning with 'kd' and ending with 'kpc'
• callsign=%kp% - All callsigns with 'kp' in them

HTTPS example - Switzerland

https://www.repeaterbook.com/api/exportROW.php?country=Switzerland

• ATV repeaters are not included

Various actions of the API can be rate limited. The actual limits are not published. However, if a human user using a browser is querying the API, there should not be any throttling issues. If you receive a rate-limiting message, wait at least 10 seconds and up to 60 seconds to reset the limiter.

The API is not intended for use by non-human-initiated (automated) transactions. If you have a business requirement that requires exceptions to the rate limits, please get in touch with the RepeaterBook administrator for pricing options.

• Add an array of linked repeaters

1/24/2025: Clarified token requirement is for commercial use of the API

1/24/2025: Updated the query term for api/export.php is 'state_id'. It was 'state'. The variable must be the state FIPS code.