Your cart is empty
Build on Eventure
Connect any AI assistant over MCP, or drive the platform directly with the REST API. Manage events, content, offers, orders and more in the organizations you administer.
How access works
- You act as your own Eventure account. Reads are limited to the organizations you belong to.
- Writes (create/update/delete) require you to be an owner or admin of the target organization.
- Creating a brand-new organization is reserved for platform operators.
Connect an AI assistant (MCP)
This is a standard remote MCP server - no API key needed. Add it as a custom connector / remote MCP server in Claude, ChatGPT, or any MCP-compatible client, then sign in with your Eventure account.
- In your assistant, add a custom connector / remote MCP server and paste the URL above.
- When prompted, sign in with your Eventure account.
- Approve the requested permissions. The assistant can then manage content in the organizations you administer.
Prefer the terminal? Add the same endpoint to Claude Code:
REST API
Prefer raw HTTP, or building an integration (n8n, Make, your own script)? The REST API uses an API key. Organization admins can create a key from the Connections page after signing in.
http://racunalnisko-drustvo.si/api/v1Authorization: Bearer whk_... or X-API-Key: whk_....filter[field]=value- filter by an allowed fieldsort=-field- sort ascending, or prefix - for descendingpage=N & per_page=N- paginationfields=a,b,c- return only these fieldsexpand=rel1,rel2- include related data (where supported)
Endpoints
Paths are relative to the base URL. The scope column is the permission your key must hold.
Events
| GET | /api/v1/events | read:events |
| GET | /api/v1/events/{id} | read:events |
Content
| GET | /api/v1/content | read:content |
| GET | /api/v1/content/{id} | read:content |
| POST | /api/v1/content | write:content |
| PUT | /api/v1/content/{id} | write:content |
| DELETE | /api/v1/content/{id} | delete:content |
Offers
| GET | /api/v1/products | read:products |
| GET | /api/v1/products/{id} | read:products |
| POST | /api/v1/products | write:products |
| PUT | /api/v1/products/{id} | write:products |
| DELETE | /api/v1/products/{id} | delete:products |
Organizations
| GET | /api/v1/organizations | read:organizations |
| GET | /api/v1/organizations/{id} | read:organizations |
| POST | /api/v1/organizations | write:organizations |
| PUT | /api/v1/organizations/{id} | write:organizations |
| DELETE | /api/v1/organizations/{id} | delete:organizations |
Files
| GET | /api/v1/files/{id} | read:files |
| POST | /api/v1/files | write:files |
| DELETE | /api/v1/files/{id} | write:files |
Users
| GET | /api/v1/users | read:users |
| GET | /api/v1/users/{id} | read:users |
| PUT | /api/v1/users/{id} | write:users |
Read-only resources
| GET | /api/v1/contacts | read:contacts |
| GET | /api/v1/deals | read:deals |
| GET | /api/v1/bookings | read:bookings |
| GET | /api/v1/orders | read:orders |
| GET | /api/v1/subscribers | read:subscribers |
| GET | /api/v1/invoices | read:invoices |
| GET | /api/v1/surveys | read:surveys |
| GET | /api/v1/galleries | read:galleries |
Incoming webhooks (POST)
| POST | /api/v1/incoming/create-contact | write:contacts |
| POST | /api/v1/incoming/update-contact | write:contacts |
| POST | /api/v1/incoming/create-subscriber | write:subscribers |
| POST | /api/v1/incoming/send-notification | write:notifications |
| POST | /api/v1/incoming/update-order-status | write:orders |
| POST | /api/v1/incoming/create-todo | write:todos |
| POST | /api/v1/incoming/create-content | write:content |
| POST | /api/v1/incoming/trigger-event | write:webhooks |
Examples
Uploads return a file id - pass it to create/update calls as featured_image_file_id so image bytes never travel through the assistant.
Ready to connect?
Sign in, then open Connections to connect an assistant or create an API key for the organizations you administer.
Go to Connections