Visual Radio Assist already integrates with a lot of the most used radio automation softwares (
Link Radio Automation ). But it could happen that we missed yours, luckily integrating is quick and easy with the generic automation link integration. This way you can enable your client to work with Visual Radio after your next update.
Link Radio Automation ). But it could happen that we missed yours, luckily integrating is quick and easy with the generic automation link integration. This way you can enable your client to work with Visual Radio after your next update.Looking for a complete and future-proof integration that works best for your radio automation software? Check out the Connecting with AutomationLink documentation for all steps to create a custom integration.
Generic JSON Request
Make the following request to push your automation data to the VRA Core API (hostname 
Network Connectivity
core.vra.local or the LAN VRA machine IP). Network Connectivity jsonPOST http://core.vra.local:3002/alink/generic Content-type: application/json { "id": "{MessageID}", "timestamp": "{MessageTimestamp}", "current": [ { "id": "{ID}", "artist": "{Artist}", "title": "{Title}", "timestamp": "{Start time}", "position": "{Start position / In point}", "duration": "{Duration}", "type": "{Type}", "category": "{Category}", "meta_1": "{Meta Field 1}", "meta_2": "{Meta Field 2}" } ], "upcoming": [ { "id": "{ID}", "artist": "{Artist}", "title": "{Title}", "timestamp": "{Start time}", "position": "{Start position / In point}", "duration": "{Duration}", "type": "{Type}", "category": "{Category}", "meta_1": "{Meta Field 1}", "meta_2": "{Meta Field 2}" }, { "id": "{ID}", "artist": "{Artist}", "title": "{Title}", "timestamp": "{Start time}", "position": "{Start position / In point}", "duration": "{Duration}", "type": "{Type}", "category": "{Category}", "meta_1": "{Meta Field 1}", "meta_2": "{Meta Field 2}" } ] }
{Fields} description
Handling character encoding
The Core API is only able to process correctly encoded and parsable UTF-8 payloads in the provided Content-type. This means that special characters (often used in artist/title strings) MUST be encoded in the way that the content format describes. Otherwise the payload won’t be processed in the AutomationLink.
Interesting characters in
JSON or XML payloads for example: & " ’ < > / $ , ;More info