ExhibitDay API

Name: ExhibitDay API
Brand: ExhibitDay API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey29 EndpointsREST

For Agents

Manage trade show events, tasks, comments, expenses, and financial rollups in ExhibitDay through 29 endpoints covering full event project CRUD plus reference lookups.

Install Jentic One Beta

Connect the ExhibitDay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ExhibitDay API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.exhibitday.com%2Fexhibitday" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.exhibitday.com%2Fexhibitday" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ExhibitDay API.

Create, update, and archive trade show events with their dates and locations

Add or close tasks attached to a specific event with assignees and due dates

Post comments on tasks to track project status updates

GET STARTED

Start building with ExhibitDay API

Explore with Jentic One

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for ExhibitDay API, keeping it validated and agent-ready. ExhibitDay is a trade show planning and event project management platform used by exhibit teams to coordinate booths, staff travel, expenses, and tasks across multiple events. The 29-endpoint API covers full CRUD on events, tasks, task comments, miscellaneous expenses and credits, and read access to financial rollups and reference data (cost centers, custom fields, participation types, tags). Built for syncing event project data into BI tools, internal dashboards, and finance systems.

Use Cases

Patterns agents use ExhibitDay API for, with concrete tasks.

★ Trade Show Project Sync to BI

Sync ExhibitDay event, task, and expense data into a business intelligence warehouse so leadership can see exhibit program ROI in the same dashboard as marketing-attribution and pipeline data. The 29 endpoints cover full event CRUD plus financial aggregates needed for cost-per-show and cost-per-lead analysis.

GET /v1/events/ to enumerate active events, then GET /v1/financials/event_costs to pull rollups and write both to the warehouse

Cross-Show Task Tracking

Run an ops dashboard that lists all open tasks across every trade show in a given quarter, with comments showing the latest status. Pull tasks by event, fetch their comments, and surface anything overdue. Replaces email and spreadsheet chasing with a single canonical view.

GET /v1/tasks/ filtered to status=open and due in the next 14 days, then GET /v1/tasks/comments for the most recent comment on each

Event Budget Reconciliation

Reconcile post-show budgets by recording every miscellaneous expense and credit (booth cleaning, last-minute shipping, hotel adjustments) against the event, then pulling the financial rollup against the original budget line. Closes the gap between project management and finance for exhibit programs.

POST /v1/events/miscexpensecredit with amount and cost type for the event, then GET /v1/financials/event_costs to confirm the rollup updated

AI Agent Event Updates via Jentic

An AI ops agent monitoring upcoming shows can call ExhibitDay through Jentic to add tasks ("book travel for booth lead"), post comments after team check-ins, and flag overdue items. Jentic isolates the api_key header and exposes the 29 operations with schemas, so the agent only needs the event ID and a clear intent.

Search Jentic for 'add a task to a trade show event', load the POST /v1/tasks/ schema, and execute with the eventId, task title, and due date

Key Endpoints

29 endpoints — jentic publishes the only available openapi specification for exhibitday api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/events/

List events with filters

POST

/v1/events/

Create a new event

GET

/v1/tasks/

List tasks for an event

POST

/v1/tasks/

Create a task on an event

POST

/v1/tasks/comment

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring ExhibitDay by hand means setting up its API key auth and coding your own calls to the events, tasks, and financials endpoints. Through Jentic you install once, import the ExhibitDay API from the API Directory, store the key once, and your agent calls it.

Permission scoping

ExhibitDay event and task targets travel in the request body rather than as ids in the URL path, so limit the agent to the operations it needs, such as reading events and tasks, and leave creation of events or expense credits out of the allowed set. Every operation you grant is your explicit choice.

Credential isolation

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.

Intent-based discovery

Agents search Jentic by intent such as 'list upcoming trade show events' or 'add a task to an event', and Jentic returns the matching ExhibitDay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ExhibitDay API through Jentic.

Why is there no official OpenAPI spec for ExhibitDay API?

ExhibitDay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ExhibitDay API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the ExhibitDay API use?

ExhibitDay uses an API key passed in the api_key request header. Through Jentic, the key is stored encrypted in the vault and injected at call time so it never enters agent context.

Can I create and update tasks on an event via the API?

Yes. POST /v1/tasks/ creates a task tied to an event, PATCH /v1/tasks/ updates fields like assignee or due date, and DELETE /v1/tasks/ removes it. Use GET /v1/tasks/info for the schema of available task fields.

How do I pull a financial rollup for a specific show?

Call GET /v1/financials/event_costs with the event ID. It returns the aggregated cost across budget lines and miscellaneous expenses recorded via /v1/events/miscexpensecredit, ready for finance reporting.

How do I add a task to an event through Jentic?

Run pip install jentic, then search 'add a task to a trade show event'. Jentic returns the POST /v1/tasks/ operation with its schema. Execute with the event ID, title, and due date and Jentic handles the api_key header.

Are reference values (cost centers, tags) hard-coded or fetched dynamically?

They are fetched dynamically. Use GET /v1/references/cost_centers, /v1/references/event_tags, /v1/references/event_custom_fields, and the other reference endpoints to enumerate the valid values configured for your account before posting events or tasks.

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

Yes. Jentic One runs self-hosted, so your own rules decide which ExhibitDay operations and credentials the agent may use. You can grant only the read operations it needs, such as GET /v1/events/ and GET /v1/tasks/, while leaving write operations like POST /v1/events/, POST /v1/tasks/, and POST /v1/events/miscexpensecredit out of the allowed set. Because event and task targets travel in the request body rather than the URL path, scoping at the operation level is how you control what the agent can reach, and every operation you grant is your explicit choice.

ExhibitDay API

Connect the ExhibitDay API to your agent

Capabilities

Start building with ExhibitDay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs