Authentication is managed using HTTP authentication. Every request must include the Authorization HTTP header. Use your API token as the username, and X (or some otherwise bogus text) as the password (only the API token is used for authenticating API requests)
Token can be generated and revocated from the web interface of the WebServices.
Example using the authentication through curl:
curl -H 'Accept: application/json' -u 653638dc733afce75130303fe6e6010f63768af0:X https://dashboard.munic.io/api/v2/:api_endpoint
curl -H 'Accept: application/json' -H 'Content-type: application/json' -u 653638dc733afce75130303fe6e6010f63768af0:X https://dashboard.munic.io/api/v2/:api_endpoint -d '{JSON data}'
Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the
pageparameter.
| Resource | Description |
|---|---|
| GET /api/v2/tickets | List of tickets |
| GET /api/v2/tickets/:id | Get a specific ticket |
| POST /api/v2/tickets | Create a new ticket |
| PUT /api/v2/tickets/:id | Update ticket |
| PUT /api/v2/tickets/:id/close | Close a ticket |
| DELETE /api/v2/tickets/:id | Delete a ticket |
| GET /api/v2/tickets/:id/acks | Get the users with dashboard notification with a specific Ack status for a ticket |