​

Mapping

The mapping tools mirror the Mapping page in Fyvel. They read imported bookings, show AI suggestions, and set or remove categories.

​

Available tools

• list_mapping_transactions
• retrain_ai_mapping_suggestions
• accept_ai_mapping_suggestions
• set_booking_categories (assign with categoryUuid, or clear assignments when categoryUuid is null)
• ignore_bookings (only when mappingIgnoreEnabled from list_companies is true)
• unignore_bookings

​

Scope

Mapping is company-specific. You need a companyUuid.

​

What list_mapping_transactions can do

list_mapping_transactions is paginated and supports the main filters from the web app:

• search
• tracked or excluded accounts
• mapped or unmapped bookings (mapped: unmapped, mapped, both — mapped includes ignored bookings)
• filter by categories, optionally including ignored bookings (includeIgnored)
• bookings with AI suggestions
• minimum confidence for suggestions
• sort

By default the tool returns mostly unmapped bookings on tracked accounts. That matches the typical work queue in mapping.

​

Typical use cases

1. list_mapping_transactions
2. choose a matching category — or ignore_bookings, when the booking should deliberately stay without a category and mappingIgnoreEnabled is true for the company
3. set_booking_categories (with categoryUuid; to clear, set categoryUuid to null)
4. optionally retrain AI suggestions or accept them in bulk

Ignored bookings stay assigned to the account in reports (without a category) and do not count as an open mapping. unignore_bookings puts them back in the queue and works regardless of the flag. ignore_bookings fails when ignore is disabled for the company.

​

Notes

• The tools change Fyvel mappings, not the original upload files
• AI suggestions can be accepted explicitly or retrained
• Categories come from list_categories