Process Request

The Wonder API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Authentication

Every API request uses a consistent signature algorithm, which protects your API requests against man-in-the-middle attacks and malicious tampering.

Add request ID

The Request ID is a critical parameter for tracking the status of API requests. We recommend that you add the UUIDV4 header X-Request-ID to every API request. Later, you can provide the Request ID to the technical support team for further assistance.

Pagination and data filtering

List APIs such as Get Customers and Get Orders follow the same design rules for data filtering and pagination called Advanced Query DSL. Unless there are special reasons, no additional explanations will be provided in the interface documentation.

Errors

Standard HTTP status codes are followed for responses. A successful request will return 200; 400 indicates invalid parameters; 500 indicates an internal server error.

Error Codes defined each module error codes details.

Error response body example

{
    "code" : "E000002",
    "message" : "Invalid Credential Format."
}

Timestamp

Unless otherwise specified, the time format shall comply with RFC 3339 in both requests and responses.