...
| URL | Swagger Gui | Swagger JSON | Note |
|---|---|---|---|
https://api-no.drofus.com | API documentation and test it in web GUI | Open API Specification | use for db2.nosyko.no projects |
https://api-eu.drofus.com | API documentation and test it in web GUI | Open API Specification | |
| https://api-ca.drofus.com | API documentation and test it in web GUI | Open API Specification | |
| https://api-us.drofus.com | API documentation and test it in web GUI | Open API Specification | |
| https://api-au.drofus.com/ | API documentation and test it in web GUI | Open API Specification |
For API versions newer than 4.20, urls should contain database and projectId. Ie. when previously getting rooms from http://xxx/api/rooms, now rooms should be read from http://xxx/api/database/projectid/rooms
Authentication
Currently we use basic authentication (username and password). Username is
Providing database and projectId in username
Preferably, database and projectId should be specified in URLs, but we still support providing it in usernames, on the form <db-name>/[project-id/]user-name[/language], where:
...
| Name | Meaning |
|---|---|
| db-name | The database-name as you would enter in dRofus Client |
| project-id | Id of project. Usually '01'. This is optional only if database only contains one project |
| user-name | The name you log on with in dRofus client |
| language | The language you want to see data in. Optional, and default is the language configured for the database |
...
Queries
We model our query-syntax on the OData standard, but currently only support a small subset of it.
...
| Code Block | ||
|---|---|---|
| ||
<http://localhost/api/database/01/rooms?$skip=1&$top=1>; rel=\"next\"> |
...