Automate Usetix
Usetix has five integration levels. Start with the smallest one that removes real work; you do not need an API project for every repeated task.
Built-in AI assistant
Use the assistant inside the admin for conversational work on the current account: create or update events, manage tickets and guest lists, configure consent-gated marketing identifiers, upload event sponsor artwork from the latest chat message, create expiring analytics links, look up orders and customers, prepare reports, or draft account content. It uses the same account rules as the normal admin and asks before critical actions.
For sponsor artwork, attach the image in the conversation and name the event plus the intended layout: one wide banner or up to six individual logos. The assistant never silently reuses an attachment from an older message. It can also inspect, switch, or remove existing sponsor artwork; removal requires confirmation.
Best when one organizer wants to complete a task without leaving Usetix.
MCP for ChatGPT, Claude, and other AI clients
Connect an MCP client when you want to use Usetix tools from an external AI workspace. Open Settings → AI Connectors, copy the MCP server URL, add it as a custom connector, and approve the account through OAuth.
MCP connections are account-scoped and revocable. They do not require a manually created API token.
CLI for terminal work and scripts
Use the Usetix CLI when a person, shell script, or coding agent should work with an account from the command line. It provides readable commands for events and orders, stable machine output, profiles, and direct access to the complete Admin API.
The CLI uses an account API token and is a good fit for support lookups, repeatable bulk work, scheduled shell jobs, and CI pipelines.
Admin API for your own software
Use the authenticated Admin API when your software needs to read or change Usetix records directly. It uses the same /admin/... URLs as the dashboard with Accept: application/json and an account API token.
Create a read token for reporting and a write token only when the integration must make changes.
Webhooks for real-time reactions
Use webhooks when another system should react to paid, refunded, cancelled, published, or redeemed activity without polling. Verify every signature and make the receiving handler idempotent because deliveries may be retried.
A practical starting point
- One organizer, occasional task: built-in assistant.
- Existing ChatGPT or Claude workflow: MCP.
- Terminal workflow, shell script, or coding agent: CLI.
- Scheduled import, export, or synchronization: Admin API.
- Immediate downstream reaction: webhook, often combined with the API.
Keep humans in control of publishing, refunds, destructive changes, and broad account settings.