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

# Weezevent API

Weezevent event management API for managing participants, checkpoints, partners, forms, widgets, promocodes, and webhooks. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get access token, list event participants. Covers 18 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get access token
- List event participants
- Create/update participants
- Partial update participants
- Delete participants

## Use cases

### Developer Tools Operations

Use the Weezevent API to perform developer tools operations programmatically. The API provides 18 endpoints covering core functionality including get access token, list event participants, get participant.

Example prompt: Call POST `/auth/access_token` to get access token

### Automated Authentication Management

Automate authentication operations by combining multiple Weezevent API endpoints. Agents can list event participants and then get participant in a single workflow.

Example prompt: Call GET `/evenement/{id_event}/participants` to list event participants, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Weezevent 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 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/access_token` | Get access token |
| GET | `/evenement/{id_event}/participants` | List event participants |
| GET | `/evenement/{id_event}/participants/{id_participant}` | Get participant |
| POST | `/participants` | Create/update participants |
| PATCH | `/participants` | Partial update participants |
| DELETE | `/participants` | Delete participants |
| POST | `/checkpoints` | Create/update checkpoints |
| GET | `/checkpoints` | List checkpoints |

## Key resources

- **Authentication** — Operations related to Authentication
- **Checkpoints** — Operations related to Checkpoints
- **Participants** — Operations related to Participants
- **Partners** — Operations related to Partners
- **Webhooks** — Operations related to Webhooks

## 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:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 79 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/weezevent.com/weezevent/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 Weezevent API by hand means calling its `/auth/access_token` endpoint, then passing the api_key query parameter across the participant and checkpoint calls, and handling retries yourself. Through Jentic you install once, import Weezevent from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Weezevent puts the event id in the URL path (`/evenement/{id_event}/participants`), so a rule can pin your agent to one event: it can read participants for that event and nothing else. You choose the operations it may call, so participant deletion or update is not included unless you add them.
- **Credential handling:** Your Weezevent 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 'list participants for an event' or 'check in a participant', and Jentic returns the matching Weezevent 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 Weezevent API use?

The Weezevent API uses an API key passed in the `api_key` query. 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 get access token with the Weezevent API?

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

### What are the rate limits for the Weezevent 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 get access token through Jentic?

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

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

The Weezevent API exposes 18 endpoints covering authentication, checkpoints, participants operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Weezevent operations and credentials the agent may use. Since the event id sits in the URL path (`/evenement/{id_event}/participants`), you can pin the agent to a single event so it reads that event's participants and nothing else. You choose the operations it may call, so participant deletion or update via /participants stays off limits unless you explicitly add it.