canonical: https://jentic.com/apis/suitebox.suitebox.co.nz/suitebox-suitebox-co-nz

# Suitebox Suitebox SuiteBox Meeting Requests

This is a dummy web site to show the set up of swagger to manager API's for SuiteBox. The API exposes 3 endpoints.

## For AI agents

Programmatically sbxmeetingrequest, sbxcancelmeeting. Covers 3 operations.

## Scope

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

## Capabilities

- SbxMeetingRequest
- SbxCancelMeeting
- SbxAuthenticateUser
- Query and filter SuiteBox Meeting Requests records by parameters
- Monitor SuiteBox Meeting Requests operational status and events

## Use cases

### Productivity Operations

Use the SuiteBox Meeting Requests to perform productivity operations programmatically. The API provides 3 endpoints covering core functionality including sbxmeetingrequest, sbxcancelmeeting, sbxauthenticateuser.

Example prompt: Call GET `/Meetings/SbxMeetingRequest` to sbxmeetingrequest

### Automated Authenticate Management

Automate authenticate operations by combining multiple SuiteBox Meeting Requests endpoints. Agents can sbxcancelmeeting and then sbxauthenticateuser in a single workflow.

Example prompt: Call GET `/Meetings/SbxCancelMeeting` to sbxcancelmeeting, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SuiteBox Meeting Requests 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 none tokens manually.

Example prompt: Search Jentic for 'sbxmeetingrequest', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/Meetings/SbxMeetingRequest` | SbxMeetingRequest |
| GET | `/Meetings/SbxCancelMeeting` | SbxCancelMeeting |
| POST | `/Authentication/SbxAuthenticateUser` | SbxAuthenticateUser |

## Key resources

- **Authenticate** — Operations related to Authenticate
- **Meeting** — Operations related to Meeting

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 55 / 100
  - AI-Readiness & Agent Experience: 35 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/suitebox.suitebox.co.nz/suitebox-suitebox-co-nz/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:** The SuiteBox Meeting Requests API exposes meeting request, cancellation, and user authentication calls that you would otherwise wire against its SBX host yourself. Through Jentic you install once, import SuiteBox Meeting Requests from the API Directory, and your agent calls them without you hand-building the request plumbing.
- **Permission scoping:** SuiteBox carries its meeting and user targets in the request parameters rather than a resource path, so you limit the agent to the operations it needs, such as requesting a meeting. Because you choose the operations, cancelling a meeting is not available unless you include it in the allowed set.
- **Credential handling:** Any credential you configure for SuiteBox 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 'request a meeting' or 'cancel a meeting', and Jentic returns the matching SuiteBox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the SuiteBox Meeting Requests use?

The SuiteBox Meeting Requests uses no authentication. 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 sbxmeetingrequest with the SuiteBox Meeting Requests?

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

### What are the rate limits for the SuiteBox Meeting Requests?

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 sbxmeetingrequest through Jentic?

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

### How many endpoints does the SuiteBox Meeting Requests have?

The SuiteBox Meeting Requests exposes 3 endpoints covering authenticate, meeting operations.

### Can I limit what my agent is allowed to do with the SuiteBox Meeting Requests API?

Yes. Because Jentic One is self-hosted, you decide which SuiteBox operations your agent may call, so you can allow SbxMeetingRequest for booking a meeting while withholding SbxCancelMeeting and SbxAuthenticateUser. SuiteBox carries its meeting and user targets in the request parameters rather than a resource path, so scoping is done by choosing the operations themselves; cancelling a meeting stays unavailable unless you add it to the allowed set. Any credentials the API needs are held by your own Jentic One instance and injected at execution time, so the agent only ever exercises the calls you permit.