> [!info] Available for all versions of SPX GC --- > [!example]- GET v1.1.2 ```http://192.168.1.3:5660/api/v1/version``` Returns SPX version info > --- > [!example]- GET v1.0.14 ```http://192.168.1.3:5660/api/v1/feedproxy?url=https://feeds.bbci.co.uk/news/rss.xml&format=xml``` > A proxy endpoint for passing feed data from CORS protected datasources. (If you need to pass url parameters use `%26` instead of `&` to separate them). --- >[!example]- POST v1.3.0 ``` http://192.168.1.3:5660/api/v1/feedproxy``` >A POST version of the feedproxy endpoint. This endpoint is a helper for outgoing GET or POST requests requiring custom headers, such as `Authorization` or similar. Data is passed to the helper in the `body` of the POST request, in which `url` is the actual URL of the external endpoint. If the body contains a `postBody` -object, it will be passed to the outgoing API request as `body`. See principle in the example below, or search SPX Knowledge Base for more info with keyword `feedproxy`. >``` json >// Stringified JSON >{ > "url": "https://api.endpoint.com/requiring/customheaders/", > "headers": { > "key1": "my first value", > "key2": "second value" > }, > "postBody": { > "info": "If postBody is found, the outgoing request will be done using POST method, otherwise as GET." > } >} --- > [!example]- GET v1.1.0 ```http://192.168.1.3:5660/api/v1/panic``` > Force clear to all output layers without out-animations. (Note, this does NOT save on-air state of rundown items to false, so when UI is reloaded the items will show the state before panic was triggered.) This is to be used for emergency situations only and not as a normal STOP command substitute. --- ## Read Next - [[Documentation/Control Interfaces/REST/Control api|Control API]] - UI control endpoints - [[Documentation/Control Interfaces/REST/Server api|Server API]] - Automation endpoints - [[Documentation/Control Interfaces/REST/Overview of SPX API|API Overview]] - Complete API guide