Fair app, partner website, info screen: they can all read your exhibitor data directly from your website. In the Settings → API tab you switch the interface on, choose what it passes on and issue keys. Only administrators see the tab.
Nobody can change data through the API. Your own exhibitor list and the hall plan always work independently of it – even when the API is off.
Setting up
- 1Switch on
Tick “Enable public API” and save. It is off by default – then its addresses don’t exist at all.
- 2Copy the base address
…/wp-json/event-exhibitor-manager/public/v1/– this is what you give your partners. - 3Choose access
“API key required” (default, recommended) or “Public”: anyone may fetch without a key.
- 4Define the data scope
See the table below.
- 5Create a key
Under “API keys” enter a name, e.g. “Fair app”. Copy the key (starts with
eempk_) from the yellow box immediately – it is shown only this once. - 6Test
Under “Endpoints & test”, send a test request with the “Send as an external application” checkbox. That way you see exactly what your partner receives.
Basic settings
| Setting | Default | Meaning |
|---|---|---|
| Rate limit | 120 requests per minute | Per key, or per IP address without a key. 0 = unlimited; individual keys can have their own limit. |
| Cache duration | 300 seconds | Finished responses are kept this long. Changes to exhibitors still arrive at once – the cache is discarded automatically. |
| Allowed origins (CORS) | empty = all | Only for websites querying with JavaScript directly in the browser. One address per line. |
Data scope
Always included: name, event, booth, location, type, categories, products, country, logo, short description, sales at booth and link. In addition you choose:
| Area | Default | What is included |
|---|---|---|
| Full description | on | The long text as HTML – in the single view, in lists on request (include=description). |
| Product gallery | on | The gallery images, large and as thumbnails. |
| Links & social media | on | Website, shop, all link platforms and the internal info page. |
| Contact details | off | Contact person, phone and address. |
| Email addresses | off | The email address, unencrypted. Only takes effect together with “Contact details”. |
Only switch on contact details and email if your exhibitors agreed to them being passed on. Never passed on: favorite counters, drafts and hidden location information.
Managing keys
- One key per partner – that way you see who fetches data and can revoke individually.
- Revoke takes effect immediately; all other keys keep working.
- A revoked key stays in the list: Unlock makes it valid again – the same key, the partner changes nothing, the request counts are kept.
- Delete is only available for revoked keys and is final; the application then needs a new key. Each of the three actions asks for confirmation first.
- Keys apply only to this plugin. For the calendar plugin’s interface a partner gets a second one.
- A settings backup contains neither keys nor the on switch – a restore never silently opens an interface.
Addresses, filters, fields and code examples for developers: REST API.