TixFinDocs

Proposals

How your AI client changes things in TixFin, only through a proposal you see and confirm, applied once, and with a fresh second factor for money

7 min read

Your AI client never changes anything in TixFin directly. Every tool that would create, change or delete something answers with a proposal instead: what would change, shown against the current state, and a handle that applies it. Nothing changes until the proposal is applied.

Proposals need Make changes you confirm (tixfin.write) on the consent page, and those that move money or reach buyers need Take actions that move money or reach buyers (tixfin.money) too. See Connect an AI client.

What a proposal shows

A proposal lists its steps in the order they run. For each step it shows:

  • The operation: its name in TixFin and the exact request, for example PUT /projects/…/events/…. If the client added its own description, that is shown separately and in quotes as the AI's description, so you can tell TixFin's words from the client's.
  • The changes in words, against the current state read live at that moment: "name": "Spring gala" → "Spring Gala 2027", "capacity": set to 500, and how many fields keep their current value. A step that creates something has no current state; a delete reads deletes it. A long list shows its count and the first five entries.
  • Personal data stays masked in the preview unless the connection may see it.

If the connection may not read the current state, for example because you did not allow reading, the preview says so and shows only the new values.

Your AI client may word the proposal for you in its own reply. What counts is what TixFin shows: if the client's summary and TixFin's preview differ, trust the preview.

Confirming

How you confirm depends on your client:

  • Clients that can ask you themselves show TixFin's confirmation form with the changes and an apply choice. Only a yes applies the proposal. A no changes nothing, and the proposal stays open until it expires.
  • Every other client shows you the proposal in the conversation and applies it with proposal_apply once you say yes.

TixFin cannot see your conversation. With the second kind of client, your yes is given to the client, not to TixFin, so allow changes only to a client you trust to ask you, and read the result it reports.

Applied once, open for 15 minutes

  • A proposal expires 15 minutes after it was made. An expired one is refused; ask the client for a new one.
  • A proposal applies once. Applying it again is refused; proposal_get shows that it was applied and its changes against the current state.
  • A proposal works only for you, on the connection and client that made it, and in its project. Another member, another client or another sign-in cannot apply it.
  • Each step is checked again when it is applied, against the same permissions, scopes and project as when it was made.
  • One connection applies one proposal at a time.

When something goes wrong

Steps run in order, and the first step that does not succeed stops the run. The client gets a report naming each step as applied, refused, outcome unknown or not sent.

  • TixFin refused the first step (for example a missing permission or an invalid value): nothing changed, and the proposal stays open until it expires.
  • A later step was refused: the steps before it landed and stay. TixFin does not undo them. The proposal is spent.
  • Outcome unknown: TixFin did not answer, or failed while answering, so the step may or may not have landed. The proposal is spent and is never retried, so nothing runs twice. Ask the client to read the current state before you ask for a new proposal of what is still missing.

Planning an event in one go

event_plan makes one proposal for a new event:

  1. the event, always created as a draft, not on sale;
  2. up to 20 ticket types for it;
  3. up to 10 group discounts for it;
  4. a shop page, created hidden.

Each later step is made for the event the first step creates; the preview reads set to step 1's "id", once it has run where it cannot know the value yet. A discount lowers what buyers pay, so a plan with one is a money proposal: it needs Take actions that move money or reach buyers and a fresh second factor, below. The venue and a seat map from a template are separate proposals (venue_upsert, seatmap_apply_template). When you are happy with the draft, event_publish proposes putting the event on sale.

Money and the step-up

Some proposals move money, lower what buyers pay, issue or admit tickets, or reach your buyers: refunds, exchanges, cancelling, postponing or deleting an event, sending a campaign, approving guest-list signups (each guest is mailed), guest-list links, creating or deleting a group discount, packages, changing a product or a seat map's layout, importing external admissions, changing the shop's design settings, writing a draft order for a buyer and retrying a badge print, and, by what they ask, adding a ticket type to an event that exists already or changing an event's refund terms, start, seat map or venue country. The tool reference lists them. A proposal with any such step is a money proposal as a whole.

Applying a money proposal needs a second factor confirmed on this connection in the last ten minutes. Your browser's sign-in does not count, and confirming here does not change your browser session.

The client applies the proposal. If the connection has no fresh second factor, TixFin sends a link to the page Confirm with your second factor. A client that can open links for you opens it; any other client shows you the link in its reply.
Open the link, sign in if asked, and check the client's name, its client ID, when you connected it and what you allowed it.
Enter the code from your authenticator app and click Confirm.
Go back to your client and let it apply the proposal again. Nothing changed before you confirmed.

The confirmation covers the connection for ten minutes, not just one proposal, as a second factor does in your browser. Only an authenticator app code works here, not a passkey or a backup code. Without two-factor authentication the page asks you to set it up first. Each link works for ten minutes and is used up once you confirm with a correct code; a wrong code leaves it open.

TixFin checks the second factor again on every money request itself, not only when the client applies the proposal. If the ten minutes run out before the first step is sent, nothing changes, the proposal stays open and you get a new link. If they run out between steps, the steps before stay applied and the report names the second factor as the reason the run stopped.

Cancelling refunds nothing by itself. Cancelling an event opens its refund job once the cancellation reaches the orders. Starting the refunds is a proposal of its own, which can hold nothing else: its preview shows the job's status, the pending orders, the amount it refunds at most and what gift cards paid. So your yes to a cancellation never starts refunds. The refunds themselves run through the same operation, permissions and checks as in the dashboard.

What is recorded

A change made through an AI client is written to TixFin's audit log as yours, with the client's ID beside it, wherever the same change made in the dashboard is recorded.

On this page