Orders

Managing orders using API endpoints

Overview of Simplio3D API Orders Endpoints

The Simplio3D API provides a set of endpoints that allow users to manage orders efficiently. Among these endpoints, the GET /orders/{orderId} endpoint is specifically designed to retrieve detailed information about a particular order by its unique ID. This enables users to monitor and track individual orders, ensuring they have access to up-to-date status and details of their transactions.

For more information on utilizing the Orders endpoints, please refer to the API documentation for additional details and examples.

GET /orders/{orderId}

GET Endpoint: Retrieve an Order by ID

Endpoint URL

GET open-api/v1/orders/{orderId}

Description

Retrieve detailed information about a specific order using its unique identifier.

Path Parameter

  • orderId: The unique identifier for the order you wish to retrieve.

Response

  • 200 OK: Successfully retrieved the order details.

  • 404 Not Found: No order was found with the provided ID.

  • 500 Internal Server Error: An error occurred on the server.

Example Request

Example Response

Get order by ID

get
/api/open-api/v1/orders/{id}

Get a specific order by ID.

Authorizations
AuthorizationstringRequired

Enter token in format (Bearer <your_token>)

Path parameters
idinteger · int64Required

ID of the order

Responses
200

Order retrieved successfully

No content

get
/api/open-api/v1/orders/{id}

No content

POST /orders

POST Endpoint: Create a New Order

Endpoint URL

POST /orders

Description

This endpoint allows you to create a new order in the system.

Request Headers

  • Content-Type: application/json

  • Authorization: Bearer <token>

Request Body

Response

  • 200 OK: Order created successfully

  • 400 Bad Request: Invalid input data

  • 401 Unauthorized: Missing or invalid authentication token

Example

Create a new order

post
/api/open-api/v1/orders

Create a new order.

Authorizations
AuthorizationstringRequired

Enter token in format (Bearer <your_token>)

Body
pricenumberRequired

Configurator total amount

Example: 3400
customer_detailsstringRequired

Customer details in JSON format

Example: {'First Name':'Jhon','Last Name':'Smith','Company':'Google Inc.','Address':'Wall Street'}
configurator_summarystringRequired

Configurator summary in JSON format

Example: {'Catalog':'Teacup classic','Material':'Glossy white','Quantity':'230'}
configurator_snapshotstring · binaryOptional

Configurator snapshot image file

configurator_print_mapstring · binary[]Optional

Array of print map image files

Responses
post
/api/open-api/v1/orders

GET /orders

GET Endpoint: Fetch All Orders

Endpoint URL

Description

This endpoint retrieves a comprehensive list of all orders in the system, allowing users to manage and review order details efficiently.

Query Parameters

  • status (optional): Filter orders by their status (e.g., pending, completed).

  • limit (optional): Limit the number of orders returned.

  • offset (optional): Specify the starting point for the list of orders returned.

Headers

  • Authorization: Bearer token required for authentication.

Response

  • 200 OK: Successfully retrieved the list of orders.

    • Content: JSON array of order objects, each containing:

      • order_id: Unique identifier for the order.

      • customer_name: Name of the customer.

      • total_amount: Total amount of the order.

      • status: Current status of the order.

      • created_at: Timestamp of order creation.

    Example Request

    Example Response

    Error Responses

    • 401 Unauthorized: Authentication failed; token missing or invalid.

    • 500 Internal Server Error: An error occurred on the server.

Fetch all orders

get
/api/open-api/v1/orders
Authorizations
AuthorizationstringRequired

Enter token in format (Bearer <your_token>)

Query parameters
per_pageintegerOptional

Number of results per page

Example: 25
pageintegerOptional

Number of page

Example: 2
order_bystringOptional

Field to sort orders by

Example: created_at
orderstring · enumOptional

Sort order (asc or desc)

Example: descPossible values:
configurator_idintegerOptional

Filter orders by specific configurator ID

Example: 127
start_datestring · dateOptional

Filter orders created after this date

Example: 2024-01-01
end_datestring · dateOptional

Filter orders created before this date

Example: 2024-12-31
Responses
200

Successful response

application/json
get
/api/open-api/v1/orders

Last updated

Was this helpful?