BrandMeister User API keys

This article was originally published on 03/2018 and has been updated on 08/2022 to add key versions.

What are users API keys ?

Any BrandMeister user can generate an API key. A key is a long string of characters that is unique to a Brandmeister user account. This digital key allows a third-party application to read and update the data on the corresponding Brandmeister Account (such as your list of hotspots, repeaters, your static talkgroups, etc.).

API keys were first introduced in Brandmeister in 2018, as API v1. In August 2022, developers improved the API features and created API v2, which changed the keys format. API keys created after 2022/08/19 are in v2 format. Keys created prior to this date are in v1 format.

Will API v1 be retired?

To ensure a smooth transition, API v1 keys created prior to 2022/08/19 will still be working for several months. They are no longer visible in the user’s self-care account, but they are still active.

While there is no set date for retiring API v1, we strongly encourage everyone to upgrade their keys to API v2 as soon as possible.

What does an API key look like?

An API v1 key is a 128-character string. For example:

MWaztB3EcHWBEW@D$2gb89Y2kvvE4leSr.33Gey74d0IYVSKU58YGMSFmPHD.Q1fECUkIcj7E4leSr.33Getkjshdf987ywe2irligr908SFIdlsfkj08934sasdlveg

The most recent API v2 key is a longer character string known as a JSON Web Token. For example:

jh7KJSAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiIxIiwianRpIjoiOWVjYjBhODRmYTAwODdkNjQ2YmNmNWJlMGJjMGEyZDQ0YmUxNGFkNDllNmM5OWNhM2NkNTcyNjViOGNjYjJmN2ZlNThlYzI1MjNhZWM2YTQiLCJpYXQiOjE2NjA5MzI0NjIuMDI5NzEyLCJuYmYiOjE2NjA5MzI0NjIuMDI5NzE1LCJleHAiOjQ4MTY2MDYwNjIuMDA3OTIyLCJzdWIiOiIxOTIiLCJzY29wZXMiOltdfQ.PnoQ3LkPeuV1TW1Hggn-D7Lloq3TRIB0bHEXTC3Ck1zXDqJRXvjf74sSJ01RSCDCOEAzyDW8eYDjguswGOjMmJ3Lp0IPAcSU7yZY3cjz7NNuFbiqllyV_jXYoBybU-FzSEuoEl3Nx6kbO6iNb_IoDrdloRxVtEDsQJ8Q27FouzMcf3lSxriwmC3tVv2V5phqzJlT-DyL0QLgZaRyDnRdxJtq6yLW5EPUAK6uAHRANCs_wbeSAKVZmqC6ycLJ0ZfIvbUBr7312HP8u2kInh1vcpnNczWyoc7FsjcZjBYrMskt7zRds051a_KqoP8uzUUSS9ZZSxrd_KDozUQ6CiWSB7nCc96B4KLY4CCpJq50I1RSnxrg4Pamj8b8abdO6O5yGakUDrp0t1jMONhOb_B9SlyNgy55SxY2ZC0Q9h3MNC1fxw_rKd73wWjD1SWsW2SI1iaAZA6ewLbn5xPpHvUlVtNri0ZO2oPfdn_1nRImCAwlYKt4LbUKmAFp-vgshMknVlVwutDNQ815y9M3F994Za_OghmAylUaWDextUh6Kx4eYAZuNnB6OphDwS08dWUZOe7MEMBH1OM2Sw_GbbjGPiS82pUDqPZzkfjs5ghFS1CfAu1BB8Teh0wgLqevWaN7VLJWOSSgl9-IOAdSSphmH0yprWbuZHPNyWq1HDY_eEI

Why using an API key?

You can enter your API key in a third-party software or hardware appliance to read and manage the information within your Brandmeister account (including repeaters, hotspots, talkgroups configuration, etc.).  Using an API key allows you to keep your SelfCare username and password confidential and to have granular control over each key you provide to others.

The API key is completely unrelated to your SelfCare password. If you change your SelfCare password, the keys you have generated are still valid.

At any time you can Revoke a key, and any person or application with this key will no longer be able to access the information and features of your Brandmeister account.

How to generate and revoke my user API keys?

To generate an API key, follow these steps:

  • Login to your BrandMeister SelfCare account using a web browser, and authenticate using your callsign and password.

BrandMeister SelfCare Login Page

  • Click on your callsign or avatar at the top of the screen, and select “Profile Settings”

BrandMeister SelfCare CallSign Profile Settings

  • Click on the “API Keys” button in the Security Settings section

BrandMeister SelfCare Security Settings API Keys

  • This is where your existing keys (if any) will be displayed. Click “Add” to create a new key.

BrandMeister SelfCare add API key

  • Provide a name for your API key.
    You can create as many keys as you’d like. It is therefore recommended to generate one key per application you will use, and name the key accordingly. The name has no impact on the key, it is just a label utilized in the SelfCare to help you remember which key is which.

  • The next screen will display the API key. If you are using a mobile app, chances are that you can just take a photo of the key within the app and you are done. Otherwise you may copy/paste the key into the application directly.

This is the only time the key code and barcode will be visible. Once you click “OK” only the key name will be available in your list. There is no need to keep a copy of your key somewhere, considering that you can always revoke and generate a new key.

BE EXTREMELY CAREFUL TO WHOM YOU GIVE YOUR KEY TO, AND WHERE YOU SAVE YOUR KEY.  THE KEYS ALLOW A COMPLETE AND FULL ACCESS TO ALL THE FEATURES OF YOUR PERSONAL SELF-CARE. THIS INCLUDES REPEATER/MASTER SYSOP FUNCTIONS!

  • After clicking “OK” you will be sent back to the list of API keys, with the ability to revoke a key if needed.

Why not just provide my SelfCare account credentials?

Your password is confidential and should never be given to others. Providing a separate key to each third-party allow you better control: if you provided your account password, each time you want to change the password you will have to go back to each third party to update it. With the API keys, you can change your SelfCare account password or revoke a key without affecting all other keys you have already provided.

Are there any existing applications using user API keys?

There are currently three developers we have worked with to develop the first applications leveraging user API keys:

Pi-Star (MW0MWZ)

Pi-Star is a custom, pre-configured SD Card image for the Raspberry Pi, built on Raspbian Linux. It includes software stacks by G4KLX, MMDVMHost / DStarRepeater, and associated tools & programs.

Its built-in dashboard now includes the ability to make changes to users’ BrandMeister configuration, by leveraging the use of APIs.

Documentation

Repeater Reader (DO1JG)

Repeater Reader is a small JAVA program that creates visibility and management options for the selected repeater or hotspot. It will also get support for controlling the repeater through APIs.

The BrandMeister team wishes to thank all application developers for making all of this happen!

Helpdesk platform for BrandMeister users and repeater sysops support

Should you need support in utilizing the BrandMeister DMR network, support to BrandMeister users, the team has put together a commercial-grade platform that combines bug tracker, documentation and ticketing.

The ticketing platform is accessible in English at this address: https://support.brandmeister.network/servicedesk/customer/portals

(you will also find this link at the bottom of the brandmeister.network website, by clicking on the word “Support”).

A team of hams is watching the ticket queue to assist you, respond to your questions, escalate possible bugs and organize feature requests.

Support’s answers can turn into knowledge documents, which will show up as possible answers as you type your question for the support.

So the more this platform is being use, the more help it will provide to the entire user community!

Talkgroup traffic exchange between BrandMeister Master and IPSC2 servers

A couple of months ago Artem/Brandmeister and Kurt/IPSC2 have worked together to create a new protocol to interconnect BrandMeister Master Servers and IPSC2 servers, for the purpose of exchanging TalkGoup traffic: OpenBridge.

Since version 20180610,  BrandMeister master servers can be interconnected with IPSC2 servers to exchange talkgroup content. Talkgroup numbers are configured on both sides, and traffic goes both ways with the ability to have traffic on multiple TalkGroups at the same time.

While you can check for the presence of an OpenBridge connection on a BrandMeister master’s status page, the protocol does not include any connection-establishment, nor keep-alive.

If you have an IPSC2 server and would like to interconnect it with the BrandMeister network, please contact the BrandMeister Master Server of your country (or the closest one if there are none in your country) to request the connection.

LastHeard Back-end Redesign

The BrandMeister database back-end for the last-heard application has been completely redesigned, bringing more speed and storage.  You can now enjoy a much more responsive last-heard with 30 rows history, and a near-instant call statistics and contact export !

The last-heard back-end is now powered by MongoDB: 3 configuration servers, 2 query servers, and 4 shards !

We want to sincerely thank Daniel – YO5DSG and Cafe Gratis Sports Club – YO5KFG for their contribution of all resources involved in this new backend platform.

 

Support for NXDN reflectors and NXCore

Support for NXDN (NX-REF and NXCORE) has been added in the latest version of BrandMeister DMR Master Server.  Master server administrators can assist you in setting up a gateway.

Here are important considerations to know about the NXDN implementation.

NXDN protocol

Keep in mind that unlike DMR, the ID numbers on NXDN are limited to a 16-bit value.  Everything above 65519 will not be recognized.

BrandMeister Server

BrandMeister does not do any ID translation between DMR<->NXDN :

*  When you receive NXDN traffic on BrandMeister, the original NXDN IDs will be showing up as the source and the talkgroup.

* When you transmit on a BrandMeister talkgroup that is bridged with NXDN, only the last 16-bits of your DMR ID will be kept and used as a the source on the NXDN network.

There is also no translation between the two systems Talkgroup IDs. Only Talkgroup numbers between 91 and 65519 are supported.

BrandMeister currently only supports the ICOM implementation of NXDN.

BrandMeister has implemented private calling support for NXDN, but at this point neither NX-REF or NXCORE have implemented this feature on their end.

NXCORE

NXCORE only supports 1 concurrent call (half duplex). This means that if several people are transmitting on a talkgroup connected to an NXcore, only one transmission will go through, and all others will be discarded until the gateway path becomes available.

You will not be able to setup multiple NXCORE on the same server to the same BrandMeister master server (by using different port numbers for example). NXCORE recognizes a BrandMeister master server as a repeater; and NXCORE identify repeaters by IP only (not by ID, not by IP/PORT).

Some statistics about unique IDs using BrandMeister and selfcare accounts

We ran database query over the past 6 months and have seen that more than 54,000 unique DMR IDs have been utilizing the BrandMeister network. That’s more than half the number of IDs assigned by DMR-Marc !

As of today, 16,000 unique users have created a Self-Care BrandMeister account . (per call-sign; some call-signs might have several DMR IDs)

Thank you all for your continuous support for the BrandMeister DMR network!

New BrandMeister master server in mainland China

We are very excited to announce that a new BrandMeister master server 4601 is now operational in mainland China. This has been made possible with the help of Michael BD7MQB.

The  server is hosted at the multi-carrier Alibaba Cloud, offering low latency and fast data transfer to all users in mainland China.

For any assistance or further information, please check the BrandMeister China Wiki page, or check the QQ group 欢迎加入BM China 服务器讨论群,群号码:327069058.

It’s BrandMeister 2nd Birthday !

Today, November 24th marks the second birthday of the BrandMeister DMR Network project!

Two years ago, BrandMeister revolutionized DMR HAM Radio by offering a uniform experience: any talkgroup accessible from any repeater or hotspot; the support for private calls; an audio web streaming server for all talkgroups, an easy to use web interface for repeater owners to do their own configuration, an interconnection with c-Bridges, D-Star reflectors, YSF reflectors, and the Wires-X network;  and a convenient wiki documentation.

Since then the core software and the back-end architecture have had several optimizations phases, and the implementation of the latest software technologies to ensure a fast network with high-audio-quality. New and unique feature have been added on a regular basis, such as repeater alerts,  repeater and hotspots passwords, Air Security,  a full APRS/GPS implementation for all common terminals, etc. Continue reading “It’s BrandMeister 2nd Birthday !”

Talkgroups numbers below 90, Clusters and Reflectors

As you may know, Talkgroups below 90 are reserved and do not route between BrandMeister master servers. Traffic stays within repeaters on the master. As of version 20171029-191416, the talkgroups below 90 should not be configured as static for any repeater.

For cluster usage, BrandMeister recommends to use Talkgroup 2 and Talkgroup 8.

Reflectors use TalkGroup 9 on Timeslot 2.

Abell R-80 Repeater is now supported by BrandMeister

The Abell R-80 DMR repeaters are now supported by BrandMeister master servers running version 20171029-191416 or later.

The R-80 is a 25W/50W repeater, available in VHF and UHF version, covering ham radio bands.

Important warning: before you go purchase this repeater, note that the manufacturer did not implement private voice calls, data calls, nor CSBK. Only voice will work (no GPS , APRS, SMS, Radio-Check, Talker-Alias, etc.) until the manufacturer implements it.