Skip to main content
This page lists every event objectChangeHistory can return, grouped by object. Each row is one event you can get back. For the query itself, actors, and access rules, see Activity history overview. How to read the tables:
  • changeType is the kind of event.
  • field is set on FIELD_CHANGED events and names what changed.
  • old → new are the values in change.old and change.new.
Treat every list here as open. Fluz adds events as it records more actions.

Events on every object

These work the same way on each object that supports them. See Ownership and access and Approvals. Access levels: GUEST 0, VIEWER 1, SPENDER 10, MANAGER 100, ADMIN 1000.

Virtual card events

objectType: VIRTUAL_CARDS. Details: Virtual card activity history.

Creation

Settings

Status

Security

Expense details

Recorded on the card a transaction was made with. Each event also carries transaction_log_id and transaction_record_id.

Sharing

Plus the ownership, access, invite, and approval events in Events on every object.

Gift card events

objectType: GIFT_CARDS. Details: Gift card activity history. Plus the ownership, access, invite, and approval events in Events on every object.

Spend account events

objectType: SPEND_ACCOUNTS. Details: Spend account activity history. Plus the ownership, access, invite, and approval events in Events on every object.

Funding source events

objectType: FUNDING_SOURCES. Details: Funding source activity history.

Bank cards

Bank accounts

PayPal


Approval codes


Reason and source values


Systems you can see


What isn’t recorded

  • Reads. Revealing card details or a gift card code, viewing balances, and listing objects.
  • Money movement. Transactions, authorizations, refunds, deposits, withdrawals, and transfers. Use Transaction activity.
  • Other things on the account. Authorized users, roles, approvals that don’t touch one of the four objects, share links, and developer applications.
  • Group access. Access a user has through a group.
  • A few specific actions. A card closed only at the issuer, failed bank card verifications, the last step of a bulk card removal, a primary funding source set automatically after linking, and gift card status changes made in Fluz Enterprise.

Next steps

Activity history overview

The query, response fields, actors, approvals, and access levels.

Approvals & requests

The requests that create approval events in activity history.