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

# Showdigs API

API for Showdigs property showing and listing management platform. The API exposes 16 endpoints secured with bearer authentication.

## For AI agents

Programmatically check location coverage, list all units. Covers 16 operations with bearer authentication.

## Scope

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

## Capabilities

- Check location coverage
- List all units
- Get specific unit
- Create listing for unit
- Update listing

## Use cases

### E-Commerce Operations

Use the Showdigs API to perform e commerce operations programmatically. The API provides 16 endpoints covering core functionality including check location coverage, list all units, get specific unit.

Example prompt: Call GET `/api/v1/coverage` to check location coverage

### Automated Coverage Management

Automate coverage operations by combining multiple Showdigs API endpoints. Agents can list all units and then get specific unit in a single workflow.

Example prompt: Call GET `/api/v1/units` to list all units, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Showdigs 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 'check location coverage', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/coverage` | Check location coverage |
| GET | `/api/v1/units` | List all units |
| GET | `/api/v1/units/{uuid}` | Get specific unit |
| POST | `/api/v1/units/{uuid}/listing` | Create listing for unit |
| PUT | `/api/v1/units/{uuid}/listing` | Update listing |
| GET | `/api/v1/listings` | Get all active listings |
| GET | `/api/v1/listings/{uuid}` | Get specific listing |
| DELETE | `/api/v1/listings/{uuid}` | Deactivate listing |

## Key resources

- **Coverage** — Location coverage operations
- **Units** — Unit management operations
- **Listings** — Listing management operations
- **Inquiries** — Inquiry operations
- **Bot** — Bot conversation operations

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/showdigs.com/showdigs/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 Showdigs API by hand means sending your bearer token on every request against api.showdigs.com and parsing its coverage, unit, and listing responses yourself. Through Jentic you install once, import the Showdigs API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Showdigs puts the unit and listing id in the URL path (`/api/v1/units/{uuid}`, `/api/v1/listings/{uuid}`), so a rule can pin your agent to one unit or listing: it can read that unit and manage its listing and nothing else. You choose the operations it may call, so destructive ones like listing deletion are not included unless you add them.
- **Credential handling:** Your Showdigs bearer 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 'check location coverage' or 'create a listing for a unit', and Jentic returns the matching Showdigs 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 Showdigs API use?

The Showdigs 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 check location coverage with the Showdigs API?

Yes. Use the GET `/api/v1/coverage` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Showdigs 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 check location coverage through Jentic?

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

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

The Showdigs API exposes 16 endpoints covering coverage, units, listings operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Showdigs operations and credentials the agent may use. Since Showdigs puts the unit and listing id in the URL path (`/api/v1/units/{uuid}` and `/api/v1/listings/{uuid}`), you can pin the agent to a single unit or listing so it reads that unit and manages its listing and nothing else. You also choose which operations it may call, so destructive ones like DELETE `/api/v1/listings/{uuid}` stay out of reach unless you add them.