How to define WRAPI-only stations

Owned by Support Triage, created
Last updated: May 03, 2023 by Bill Best
2 min read

Some territories have a requirement to publish stations to the WRAPI for the display of certain stations in cars - but these stations currently don’t have audio URLs.

We have some special business rules in place to support this particular setup:

  • API users that are tagged as “Automotive” are allowed access to stations that have no streams

  • You can also set up specific Station/User groups that control which users can see which stations

To have WRAPI only stations with no streams, you will need to follow the steps below.

 Instructions

  1. Create the station as normal in my.radioplayer.org - upload branding assets and so on for the station as usual. Take care which groups the station is added to when it is created - for instance, you might not want it to be in the MobileAPI group, as this station should not be available to apps. Alternatively you might want to add it to the RadioDNS group, which will mean that the WRAPI will make the station available by its SI.XML file

  2. You do not need to define any streams for the WRAPI-only station. However, you do need to define bearers.

  3. In Admin Settings, set the WRAPI-only station to “Discoverable”.

4. Publish the station.

5. If you didn’t do this when the station was created, you will then have to ensure that the WRAPI user can see the new station. In Germany, this is managed via the CAR group WRAPI_4Car_only. Make sure to add the station to this Group:

The WRAPI user is a member of this group, so can see this station.

If your territory does not have a CAR group then inform the Radioplayer Helpdesk for advice - and also inform the Radioplayer Helpdesk if you create a CAR group for your territory.

The station will then be added to the WRAPI when it next polls the APIs for stations.

Checking API response

You can test that the station is being returned correctly by running the following query:

https://core-search.radioplayer.org/276/metadata/api/v2/services/

(Replacing 276 with your country’s territory code)

Use the credentials of the WRAPI user to authenticate this request. You can see these by looking at the wrapi@radioplayer.org user in the Radioplayer Cloud CMS; the password is this user’s API key.