Status Codes

Overview

Terminal uses HTTP Status Codes

Code	Description	Comments
200	OK	Standard success response
201	Created	Returned on successful entity creation. Returns either an empty response or the created resource.
202	Accepted	Our server accepted the request and may or may not succeed. Requires asynchronous processing. Moneris uses this status code for successful requests that may prompt additional activity outside for Moneris API by your server or a queued process within Moneris.
204	No content	There is no response body.
400	Bad Request	Bad request - unspecific client error indicating that the server cannot process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request). Should also be delivered in case of input payload fails business logic / semantic validation (instead of using status code 422).
401	Unauthorized	Unauthenticated credentials are not valid for the target resource.
403	Forbidden	The user is not authorized to use this resource.
404	Not Found	The resource is not found.
408	Request Timeout	The terminal times out waiting for the resource.
409	Conflict	Request cannot be completed due to conflict with the current state of the terminal.
429	Too Many Requests	The terminal does not consider rate limiting and sent too many requests in a short span.
500	Internal Server Error	A generic error indication for an unexpected server execution problem (here, client retry may be sensible).
503	Service Unavailable	Service is (temporarily) not available (e.g., if a required component or downstream service is not available) — client retry may be sensible. If possible, the service should indicate how long the client should wait by setting the Retry-After header.