Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:syces:api_hidden [2015/08/05 10:19] co |
en:syces:api_hidden [2016/09/13 09:31] (current) co |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== SyCes API ====== | ====== SyCes API ====== | ||
| + | === Requirements === | ||
| + | Only regular clients can use the API. Furthermore you require an api-key. We will also store a default tariff and the default type of username if you specify them. | ||
| + | |||
| === Protocol === | === Protocol === | ||
| - | Our SyCes-API uses the JSON-RPC protocol, version 2.0. | + | Our |
| JSON-RPC (JavaScript Object Notation Remote Procedure Call) is a simple remote procedure call protocol encoded in JSON. | JSON-RPC (JavaScript Object Notation Remote Procedure Call) is a simple remote procedure call protocol encoded in JSON. | ||
| - | You must call the API via HTTPS. | + | You must call the [[en: |
| === Usage === | === Usage === | ||
| Line 27: | Line 30: | ||
| === Authentication === | === Authentication === | ||
| - | You need to a valid sessionid | + | You need to a valid token for any api call. It can be retrieved by calling the authenticate-method. |
| - | === Example | + | === Examples |
| - | request { " | + | request { " |
| - | result for valid credentials { " | + | result for valid credentials { " |
| result for invalid credentials { " | result for invalid credentials { " | ||
| + | |||
| + | === Example using curl === | ||
| + | curl -i -k -H " | ||