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

# ExhibitDay API

ExhibitDay is a trade-show and event-planning platform whose API exposes events, financials, and reference data so agents can sync external systems with the planning workspace. The 24-endpoint surface covers event retrieval and information lookups, event-cost and miscellaneous-expense tracking, and reference data such as cost types, custom fields, and participation types. Agents use it to push event data in, pull event budgets out, and keep custom fields in sync with downstream tools.

## For AI agents

Pull and push trade-show event data, costs, and reference metadata between ExhibitDay and external planning or finance systems.

## Scope

Does not handle event registration, attendee check-in, or venue booking - use for ExhibitDay event, financial, and reference-data sync only.

## Capabilities

- List events and retrieve detailed event information for trade-show planning
- Pull event-cost line items to feed downstream financial reporting
- Pull miscellaneous annual expense costs alongside event-specific spend
- Look up reference data such as event-cost types and participation types
- Retrieve custom field definitions for events to map them in external systems
- Sync event metadata between ExhibitDay and CRMs, finance tools, or data warehouses

## Use cases

### Trade-show budget reporting

A finance agent pulls event costs and miscellaneous expenses from ExhibitDay each month, joins them with the cost-type reference list, and produces a per-event budget vs actual report. Pulling structured data via the API removes the need for finance to export CSVs from the ExhibitDay UI.

Example prompt: Call /v1/financials/event_costs and /v1/financials/misc_annual_expense_costs, join with /v1/references/event_cost_types, and produce a per-event budget vs actual report.

### Event-to-CRM sync

A marketing operations agent syncs ExhibitDay events into Salesforce or HubSpot as campaigns. It calls /v1/events/ for the list, /v1/events/info for details, and pulls custom fields via /v1/references/event_custom_fields so the CRM mirrors the planning fields exactly.

Example prompt: List events via /v1/events/, fetch details via /v1/events/info for each upcoming event, and upsert them as Salesforce campaigns with the matching custom fields.

### Custom field mapping for data warehouse

An analytics agent loads ExhibitDay event records into a data warehouse and needs the schema. It calls /v1/references/event_custom_fields to retrieve every custom field definition, then generates target columns in the warehouse table so downstream BI dashboards stay aligned with the source.

Example prompt: Fetch /v1/references/event_custom_fields and generate a CREATE TABLE statement for an exhibitday_events table that includes every custom field as a typed column.

### AI agent event assistant via Jentic

An AI assistant integrated through Jentic answers questions like 'what does this trade show cost so far?' and 'list events happening next month'. Jentic isolates the API key in your Jentic One instance and resolves natural-language intents into specific ExhibitDay endpoints.

Example prompt: Use Jentic to search for 'list exhibitday events', load the /v1/events/ operation, and return all events scheduled in the next 30 days.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/events/ | List events |
| GET | /v1/events/info | Retrieve detailed event information |
| GET | /v1/financials/event_costs | Retrieve event-cost line items |
| GET | /v1/financials/misc_annual_expense_costs | Retrieve miscellaneous annual expense costs |
| GET | /v1/references/event_cost_types | List event-cost type reference data |
| GET | /v1/references/event_custom_fields | List event custom field definitions |
| GET | /v1/references/event_participation_types | List event participation types |

## Key resources

- **Events** — Trade-show and event records with details and metadata
- **Financials** — Event costs and miscellaneous annual expense data
- **References** — Reference data such as cost types, participation types, and custom field definitions

## Why Jentic

- **Setup:** Wiring the ExhibitDay API by hand means learning its API key auth and tracking the event, financial, and reference-data endpoints under /v1 yourself. Through Jentic you install once, import ExhibitDay from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** ExhibitDay returns event and cost data through read endpoints without resource ids in the path, so scope the agent to the operations it needs, such as listing events or pulling event costs. It reads sync data and can perform no other action within that set.
- **Credential handling:** Your ExhibitDay 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 exhibitday events' or 'pull event costs', and Jentic returns the matching ExhibitDay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cvent** — Enterprise event-management platform with registration, agendas, and venues
- **HubSpot CRM** — CRM that consumes ExhibitDay event records as marketing campaigns
- **Salesforce** — CRM destination for syncing ExhibitDay events as Campaigns
- **Smartsheet** — Work execution platform for tracking trade-show task lists and budgets

## FAQ

### What authentication does the ExhibitDay API use?

ExhibitDay uses API key authentication. Through Jentic, the key is stored encrypted in your Jentic One instance and replaced with a scoped token at call time, so the raw key never enters the agent's context or transcripts.

### Can I pull event-cost data through the ExhibitDay API?

Yes. GET /v1/financials/event_costs returns event-cost line items, and GET /v1/financials/misc_annual_expense_costs returns the matching miscellaneous expense data so an agent can build a complete spend picture per event.

### How do I get the schema for ExhibitDay custom fields?

Call GET /v1/references/event_custom_fields to retrieve every custom field definition. An agent typically pairs that with /v1/events/info so the field values come back alongside the field definitions for downstream mapping.

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

The OpenAPI spec does not publish explicit rate limits. ExhibitDay enforces account-level throttling at the platform layer, so agents should handle 429 responses with exponential backoff and respect Retry-After headers.

### How do I list ExhibitDay events through Jentic?

Run pip install jentic, search for 'list exhibitday events', load the GET /v1/events/ operation, and execute. Jentic returns the parsed event list so the agent can drive downstream sync without reading the spec directly.

### Does ExhibitDay's API support creating new events?

The endpoints exposed in this spec are heavily oriented toward read access - event listings, financials, and reference data. For event creation and write workflows, check the ExhibitDay developer documentation for any partner-only endpoints not present in this OpenAPI surface.

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

Yes. Because you run Jentic One yourself, your own rules decide which ExhibitDay operations and credentials the agent may use, so you can grant only the calls it needs, such as listing events with GET /v1/events/ or pulling spend with GET /v1/financials/event_costs. The ExhibitDay surface exposed here is read-only and its endpoints carry no resource ids in the path, so a scoped agent can read event, financial, and reference data but perform no other action. You can, for example, allow reference lookups like GET /v1/references/event_cost_types while withholding financial endpoints entirely.