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

# edoobox API

edoobox is a Swiss-built course-and-event booking platform used by schools, training providers, and seminar organisers. The v2 API exposes a focused integration surface: authenticate to obtain a bearer token, then list the offers (courses, events, and bookable services) available in your edoobox account. It is designed for partners and integrators who need to surface bookable offers in their own websites, agent assistants, or marketing automation without manually copying course catalogues.

## For AI agents

Authenticate against an edoobox tenant and list its bookable course and event offers. Useful for agents that surface or shop for training courses.

## Scope

Does not handle booking creation, payment processing, attendee management, or course content delivery - use for authenticating to edoobox and listing bookable offers only.

## Capabilities

- Authenticate to an edoobox tenant and receive a bearer access token
- List the catalogue of course and event offers configured in an edoobox account
- Surface bookable training and seminar offers inside an external website or agent
- Pull the latest offer catalogue on a schedule to keep partner sites in sync with edoobox

## Use cases

### Embed edoobox course catalogue on a partner site

A training provider wants its public website to show the live catalogue of courses configured in edoobox so visitors always see current dates and availability. A scheduled job authenticates against the edoobox API, lists offers, and pushes the result into the website's CMS or static site generator. Because the API is just two endpoints, the connector is easy to build and maintain.

Example prompt: POST /auth with the API credentials to get a bearer token, then GET /offer/list with that token and write the response into the website's course catalogue store.

### Course discovery agent for learners

A conversational agent helps prospective learners find suitable courses inside a training provider's edoobox tenant. The agent authenticates once per session, lists offers, and filters them by topic, language, or date based on the user's natural-language request. Even though edoobox itself handles registration in its UI, the API gives the agent the catalogue it needs to recommend the right course.

Example prompt: Authenticate via POST /auth, call GET /offer/list, and return the three closest matches to the learner's stated topic and preferred date range.

### Marketing automation sync

A marketing team needs the latest list of bookable seminars in their email and ad campaigns. An automation calls the edoobox API on a daily cadence and refreshes the list of offers in the marketing platform's product catalogue, so audience segments and dynamic content stay accurate. Agents using Jentic can run the same flow end-to-end without writing a custom client.

Example prompt: Search Jentic for 'list edoobox offers', load the schema, execute the call, and push the resulting offer list into the marketing platform's catalogue.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /auth | Authenticate and get an access token |
| GET | /offer/list | List all offers |

## Key resources

- **Authentication** — Exchange API credentials for a bearer access token
- **Offers** — List the course and event offers configured in an edoobox tenant

## Why Jentic

- **Setup:** Wiring edoobox by hand means handling its bearer auth, running the POST /auth token exchange yourself, and choosing between the app2 and app1 hosts. Through Jentic you install once, import the edoobox API from the API Directory, store the bearer credential once, and your agent calls it.
- **Permission scoping:** The edoobox operations here carry no resource id in the URL path, so scope the agent by operation: limit it to the calls it needs, such as authenticating and listing offers with GET /offer/list. You choose the operations it may call, so anything outside that set is not included unless you add it.
- **Credential handling:** Your edoobox bearer credential 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 bookable course offers in edoobox', and Jentic returns the matching GET /offer/list operation with its input schema so the agent calls the right endpoint without handling the token exchange or browsing the reference docs.

## Related APIs

- **Calendly API** — Calendly schedules individual appointments rather than managing course-and-seminar catalogues, but is a common alternative for simple booking flows.
- **Teachable API** — Teachable hosts on-demand courses; choose it when the offering is digital course content rather than instructor-led sessions.
- **Brevo API** — Brevo (formerly Sendinblue) sends booking confirmations and reminders alongside an edoobox catalogue feed.

## FAQ

### What authentication does the edoobox API use?

edoobox uses HTTP bearer authentication. You first POST API credentials to /auth to receive an access token, then send that token in the Authorization: Bearer header on calls to /offer/list. Jentic stores the credentials encrypted and injects the bearer token at execution time.

### Can I list bookable courses with the edoobox API?

Yes. GET /offer/list returns the catalogue of offers - courses, events, and bookable services - configured in the authenticated edoobox tenant.

### Does the edoobox API support creating bookings or registrations?

No. The published v2 spec only exposes /auth and /offer/list. Booking creation continues to happen through the edoobox web UI or other vendor-specific endpoints not covered by this spec.

### What are the rate limits for the edoobox API?

Rate limits are not declared in the spec. Because the offer list is a relatively static resource per tenant, cache the response between syncs and avoid polling more frequently than once an hour.

### How do I retrieve edoobox offers through Jentic?

Run pip install jentic, search Jentic for 'list edoobox offers', load the operation schema, and execute the call. Jentic handles the /auth exchange and forwards the resulting bearer token to /offer/list, returning the offer list to the agent.

### Which edoobox server should I use, app1 or app2?

The spec lists app2.edoobox.com as the primary v2 server with app1.edoobox.com as a secondary. Use the host that edoobox assigned to your tenant when your account was provisioned.

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

Yes. Because your Jentic One instance is self-hosted, you decide which edoobox operations your agent may call and which credentials it may use. The edoobox operations carry no resource id in the URL path, so you scope the agent by operation: allow only the calls it needs, such as authenticating with POST /auth and listing offers with GET /offer/list. Anything outside that set stays unavailable unless you add it yourself.