OZEKI HTTP API - Status Codes
The following status codes can be returned to incoming http requests:
Code | Name | Message |
200 | OK | Command successfully executed |
300 | ParseError | Error occured during parsing message: '{0}' |
301 | NotImplementedCommand | Not implemented command: '{0}' |
302 | InvalidParameter | Missing or invalid parameter '{0}' for command '{1}' |
303 | InappropriateCommand | Command '{0}' cannot be used here |
304 | Authentication required | Authentication required |
305 | Authentication failed | Authentication failed, bad username or password |
306 | Forbidden User | User is not allowed to use API in ACL |
307 | ForbiddenAddress | Use API from this address is forbidden |
401 | ApiExtensionUnavailable | API extension '{0}' unavailable, please check configuration or permissions |
402 | CallConnectFailed | Call connect to '{0}' failed with result state '{1}' |
501 | SmsDestinationNotFound | Destination of the SMS is not found |
601 | CallNotFound | Call not found with ID '{0}' |
701 | ConfigNotFound | Configuration for type '{0}' not found |
702 | InvalidConfig | Invalid configuration for type '{0}' |
703 | ConfigAlreadyExists | Extension configuration already exists |
'{0}' and '{1}' are varying parameters depending on the input parameters.
e.g. code 601: Call not found with ID g67th7
More information
- HTTP API commands in Ozeki Phone System PBX
- Notifications of Ozeki Phone System PBX HTTP API
- Status codes of Ozeki Phone System PBX HTTP API
- Response Format of Ozeki Phone System HTTP API
- How to setup HTTP API service in Ozeki Phone System PBX
- How to control the User Authentication with HTTP API
- Learn the correct form of GET and POST HTTP requests