> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/order_status.md).

# Slant3D Order Status

Blocks for processing, listing, tracking, and cancelling Slant3D orders.

## Slant3D Cancel Order

### What it is

Cancel an order before production starts

### How it works

This block requests cancellation of an existing order using its public ID, such as `order_id="SLANT_1234567890"`. It returns the provider's status message, or `Order cancelled` when a successful response omits that optional message.

An invalid ID, an order that cannot be cancelled at its current production stage, or a provider failure produces an error. Check the order status before cancelling; failed cancellation requests are not automatically retried.

### Inputs

| Input     | Description                       | Type | Required |
| --------- | --------------------------------- | ---- | -------- |
| order\_id | Slant3D public order ID to cancel | str  | Yes      |

### Outputs

| Output | Description                           | Type |
| ------ | ------------------------------------- | ---- |
| error  | Error message if the operation failed | str  |
| status | Cancellation status message           | str  |

### Possible use case

**Customer Cancellations**: Allow customers to cancel orders through your interface.

**Error Recovery**: Cancel orders placed with incorrect details or specifications.

**Order Management**: Implement cancellation functionality in order management dashboards.

***

## Slant3D Get Orders

### What it is

Get all orders for the account

### How it works

This block collects the public IDs of all orders associated with the Slant3D account. It requests pages of 100 orders and stops at the reported final page, an empty page, or a short page when pagination metadata is absent. An empty account returns `orders=[]`.

Provider failures stop pagination and surface as an error instead of returning a partial list. The output contains IDs such as `SLANT_1234567890`; use Tracking to retrieve an order's status and tracking numbers.

### Outputs

| Output | Description                              | Type       |
| ------ | ---------------------------------------- | ---------- |
| error  | Error message if the operation failed    | str        |
| orders | Public IDs of all orders for the account | List\[str] |

### Possible use case

**Order Dashboard**: Build dashboards showing all orders and their current status.

**Sync Operations**: Regularly sync Slant3D orders with your internal order management system.

**Reporting**: Generate reports on order volume and status distribution.

***

## Slant3D Process Order

### What it is

Submit an approved Slant3D draft to order physical 3D-printed parts for manufacturing and delivery. Uses the order\_id from Estimate Order or Estimate Shipping, charges the connected payment method, and starts production. Run only after the customer approves the quoted order.

### How it works

This block processes an approved, uncharged draft identified by its public `order_id`, for example `order_id="SLANT_1234567890"` from Estimate Order or Estimate Shipping. Processing charges the connected Slant3D payment method and submits the order to production. The output is the processed order ID.

The provider rejects invalid IDs and drafts that cannot be processed, including already-processed orders. If a provider or connection failure prevents confirmation, the block reports an error with the draft ID. Check that order's status before retrying because payment may have completed; processing requests are not automatically retried.

### Inputs

| Input     | Description                                     | Type | Required |
| --------- | ----------------------------------------------- | ---- | -------- |
| order\_id | Uncharged draft order ID from an estimate block | str  | Yes      |

### Outputs

| Output    | Description                           | Type |
| --------- | ------------------------------------- | ---- |
| error     | Error message if the operation failed | str  |
| order\_id | Processed Slant3D public order ID     | str  |

### Possible use case

**Approved Quote Fulfillment**: Process the draft returned by a pricing block after a customer confirms the cost and shipping details.

**Scheduled Production**: Submit an approved draft when its planned manufacturing date arrives.

**Purchase Approval Workflow**: Process a prepared draft after an internal purchaser approves its cost.

***

## Slant3D Tracking

### What it is

Track order status and shipping

### How it works

This block retrieves the current status and available tracking numbers for one public order ID, such as `order_id="SLANT_1234567890"`. Before fulfillment, missing shipment information returns `tracking_numbers=[]`.

Invalid or inaccessible order IDs and provider failures surface as errors. Use the returned status and tracking-number list for order-status pages and shipment notifications.

### Inputs

| Input     | Description                      | Type | Required |
| --------- | -------------------------------- | ---- | -------- |
| order\_id | Slant3D public order ID to track | str  | Yes      |

### Outputs

| Output            | Description                           | Type       |
| ----------------- | ------------------------------------- | ---------- |
| error             | Error message if the operation failed | str        |
| status            | Order status                          | str        |
| tracking\_numbers | Shipment tracking numbers             | List\[str] |

### Possible use case

**Order Status Page**: Display current order status to customers on your website.

**Shipping Notifications**: Get tracking numbers to send shipping notifications to customers.

**Customer Support**: Look up order status quickly for customer service inquiries.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/order_status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.