api information
We have a simple API that can be used to sceneify URLs. For example, you may choose to create them from a custom application or script, or even from a browser extension.
In order to minimise the impact of spambots and misuse, you will require an API key. The key is simply added to whatever creation requests you send to the API. The API key and access to the API is and will stay completely cost-free.
Please get in touch via our contact page to request a key!
Ok, let's get down to business; to sceneify an URL, you create either a POST or a GET-request to https://scenes.at/c. For example, here is a GET-request:
https://scenes.at/c?link=[url]&alias=[alias]&pwd=[password]&api=[anything]&key=[api-key]
The parameters are as follows (* = mandatory):
| Parameter | Explanation |
|---|---|
| link* | A full URL (including https:// etc.) to sceneify. |
| alias | The alias you want to give the link. If left out or already taken, a new one will be generated for you. Up to 127 characters, consisting only of a-z, 0-9 and -. Reserved internal paths are declined. |
| pwd | Require the visitor to enter this (optional) password. After entering the password, the visitor is taken to the destination URL. |
| api | If the value json is sent in this parameter, the system will return a JSON structure. If no value is set, the full HTML page will be output. With any other non-empty value, it will return a simple text response containing either the created sceneified URL or one of these messages: "Error", "Declined", "Invalid API key.", "Invalid URL." or "Not allowed destination." |
| key* | Your personalized API key. Must be used to sceneify a link from an application that does not generate an HTTP_REFERER. |