canonical: https://jentic.com/apis/services.ordertime.com/services-ordertime

# Services Ordertime Order Time REST API

Order Time is a powerful inventory control and order management platform. The REST API allows creating, modifying, deleting, and querying records including customers, items, quotes, sales orders, and ship docs. The API exposes 47 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a part item, list part items. Covers 47 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create a Part item
- List Part items
- Get a Part item
- Update a Part item
- Delete a Part item

## Use cases

### E-Commerce Operations

Use the Order Time REST API to perform e commerce operations programmatically. The API provides 47 endpoints covering core functionality including create a part item, list part items, get a part item.

Example prompt: Call POST /partitem to create a part item

### Automated Items Management

Automate items operations by combining multiple Order Time REST API endpoints. Agents can list part items and then get a part item in a single workflow.

Example prompt: Call GET /partitem to list part items, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Order Time REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create a part item', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/partitem` | Create a Part item |
| GET | `/partitem` | List Part items |
| GET | `/partitem/{id}` | Get a Part item |
| PUT | `/partitem/{id}` | Update a Part item |
| DELETE | `/partitem/{id}` | Delete a Part item |
| POST | `/customer` | Create a Customer |
| GET | `/customer` | List Customers |
| GET | `/customer/{id}` | Get a Customer |

## Key resources

- **Items** — Manage inventory items
- **Customers** — Manage customers
- **Sales Orders** — Manage sales orders
- **Sales Order Lines** — Manage sales order line items
- **Quotes** — Manage quotes

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/services.ordertime.com/services-ordertime/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Order Time by hand means setting the X-API-Key header on every request and handling its part-item, customer, and sales-order calls yourself. Through Jentic you install once, import Order Time from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Order Time puts the record id in the URL path (`/customer/{id}`, `/partitem/{id}`), so a rule can pin your agent to reading and updating specific records. You choose the operations it may call, so a record delete via DELETE is not included unless you add it.
- **Credential handling:** Your Order Time API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a part item' or 'look up a customer', and Jentic returns the matching Order Time operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Order Time REST API use?

The Order Time REST API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a part item with the Order Time REST API?

Yes. Use the POST /partitem endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Order Time REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a part item through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a part item'. Jentic returns the matching Order Time REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Order Time REST API have?

The Order Time REST API exposes 47 endpoints covering items, customers, sales orders operations.

### Can I limit what my agent is allowed to do with the Order Time REST API?

Yes. Because you self-host Jentic One, your own rules decide which Order Time operations and credentials the agent may use, so you can allow read and update calls while withholding others. Since Order Time puts the record id in the URL path, such as `/customer/{id}` and `/partitem/{id}`, you can pin the agent to reading and updating specific records. Destructive calls like DELETE `/partitem/{id}` are not available to the agent unless you explicitly add them.