canonical: https://jentic.com/apis/wayfront.com/wayfront

# Wayfront API

With Wayfront, how you sell and deliver services is no longer the bottleneck. We unify your process, automate and remove steps, and help clients find what they need. The API exposes 62 endpoints secured with bearer authentication.

## For AI agents

Programmatically mark task as complete, mark task as incomplete. Covers 62 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Mark task as complete
- Create a coupon
- List all coupons
- Retrieve a coupon
- Update a coupon
- Delete a coupon

## Use cases

### Developer Tools Operations

Use the Wayfront API to perform developer tools operations programmatically. The API provides 62 endpoints covering core functionality including mark task as complete, mark task as incomplete, create a coupon.

Example prompt: Call POST `/order_tasks/{task}/complete` to mark task as complete

### Automated Tasks Management

Automate tasks operations by combining multiple Wayfront API endpoints. Agents can mark task as incomplete and then create a coupon in a single workflow.

Example prompt: Call DELETE `/order_tasks/{task}/complete` to mark task as incomplete, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wayfront 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 bearer tokens manually.

Example prompt: Search Jentic for 'mark task as complete', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/order_tasks/{task}/complete` | Mark task as complete |
| DELETE | `/order_tasks/{task}/complete` | Mark task as incomplete |
| POST | `/coupons` | Create a coupon |
| GET | `/coupons` | List all coupons |
| GET | `/coupons/{coupon}` | Retrieve a coupon |
| PUT | `/coupons/{coupon}` | Update a coupon |
| DELETE | `/coupons/{coupon}` | Delete a coupon |
| POST | `/form_data` | Create a filled form field |

## Key resources

- **Tasks** — Tasks
- **Coupons** — Coupons
- **Filled Form Fields** — Filled Form Fields
- **Invoices** — Invoices
- **Logs** — Logs

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 43 / 100
  - Developer Experience & Jentic Compatibility: 73 / 100
  - AI-Readiness & Agent Experience: 62 / 100
  - Agent Usability: 92 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/wayfront.com/wayfront/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 the Wayfront API by hand means learning its bearer auth, resolving your workspace URL into the host, and handling responses yourself. Through Jentic you install once, import the Wayfront API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Wayfront puts the resource id in the URL path (`/coupons/{coupon}`, `/order_tasks/{task}/...`), so a rule can pin your agent to one coupon or task and nothing else. You choose the operations it may call, so destructive ones like coupon deletion or removing a task completion are not included unless you add them.
- **Credential handling:** Your Wayfront token 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 'mark an order task complete' or 'create a coupon', and Jentic returns the matching Wayfront operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Wayfront API use?

The Wayfront API uses a Bearer token in the Authorization 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 mark task as complete with the Wayfront API?

Yes. Use the POST `/order_tasks/{task}/complete` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wayfront 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 mark task as complete through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'mark task as complete'. Jentic returns the matching Wayfront API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wayfront API have?

The Wayfront API exposes 62 endpoints covering tasks, coupons, filled form fields operations.

### Can I limit what my agent is allowed to do with the Wayfront API?

Yes. Because you run Jentic One yourself, you decide which Wayfront operations your agent may call, so you can allow it to complete order tasks or list coupons while leaving out destructive calls like DELETE `/coupons/{coupon}` or removing a task completion. Wayfront puts the resource id directly in the URL path, such as `/coupons/{coupon}` and `/order_tasks/{task}/complete`, so your rules can pin the agent to a single coupon or task and nothing else. The Wayfront bearer token stays with your own instance and is injected only for the operations you have permitted.