| name | repairshopr-item |
| description | Manage part orders (items) in RepairShopr - track parts procurement |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"technicians, parts managers, administrators","api":"GET /items"} |
What I do
I manage part orders (items) in RepairShopr. Items track parts that need to be ordered, received, or are in transit. They are typically created from tickets when parts are needed. I can list items with various filters.
When to use me
Use this when:
- Tracking parts that need to be ordered for repairs
- Viewing the status of part orders (ordered, received, pending)
- Searching for specific parts by ticket number or query
- Managing parts inventory workflow
How to use
Required API base URL:
VITE_REPAIRSHOPR_SUBDOMAIN
VITE_REPAIRSHOPR_API_KEY
Permission: "Parts Orders - List/Search" required.
List Items (GET /items)
Optional parameters:
completed (boolean) - Filter to only completed part orders
query (string) - Search query
page (integer) - Page number (50 results per page)
Example call:
const result = await skill({ name: "repairshopr-item" }, {
completed: false,
query: "screen",
page: 1
})
Response includes:
items array with part order objects containing:
id, ticketnum, description
parturl - URL where part was ordered
status fields: ordered_on, received_on, trackingnum
price, quantity, product_id
ticket_id, user_id
from_location_id, destination_location_id
logistic_state - shipping state
created_at, updated_at
Important
- Items are primarily read-only via this endpoint; creation happens through tickets
completed filter helps find items that have been received
query performs partial matching across item fields
- No create/update/delete operations are available on the
/items endpoint itself
Related skills
repairshopr-ticket - Items are typically created from tickets when parts are needed
repairshopr-product - For product catalog information
repairshopr-purchase-order - For vendor purchase orders