Try now

EU Data Act Online Registry

Service
Provider: MICE Operations
Registry Version: 1.0
Date: October 1, 2026

This registry is subject to periodic technical and legal validation.

1. Categories of data and digital assets that may be transferred

The transfer can take place via two existing channels: the public MICE Operations REST API at https://api.miceoperations.com/api/v1/ and the logged-in MICE application for company users. The API uses JSON for requests and responses. Collections are paginated; the documented maximum page size is 100 records. Invoices can also be downloaded individually as PDFs. The logged-in application offers additional exports and downloads in CSV, XLSX, PDF, DOCX, UBL/XML, ZIP, DOC, and iCalendar formats, as detailed in section 1.4.

1.1 Data Entered or Managed by the Customer in MICE

The following data categories are available via the public API, depending on the permissions associated with the company-specific API key used. Some categories can also be exported—or can only be exported—via the logged-in application; these are listed in section 1.4:

  • Company data via /companies/me: company ID and company name.
  • Events via /events and /events/{event_id}: ID, external ID, creation and modification dates, name, type, status, schedule, location, organizer/planner, client, contacts, number of guests, references, comments, additional fields, booking information, prices, VAT totals, and deletion status. A search query can include associated activities, products, packages, location, client, planner, and contacts.
  • Activities within events via /events/{event_id}/activities and /events/{event_id}/activities/{activity_id}: schedule, name, description, location, setup, number of guests, notes, link to the event, and linked products.
  • Clients and suppliers via /clients and /clients/{client_id}: organizational details, type, external identification, contact information, addresses, country, VAT number, Chamber of Commerce number, OIN, and references.
  • Event contacts as part of an event: name, email address, phone number, and role. There is no separate public V1 endpoint for all contacts.
  • Products and product categories via /products and /products/categories: product ID, external identifier, code, category, name, description, content, language, price, price excluding VAT, VAT, VAT rates, and general ledger number.
  • Product lines within events and activities: object type, object ID or code, date, quantities, description, prices, VAT, and link to event, activity, or package.
  • Locations via /locations and /locations/{location_id}: location ID, external identifier, code, general ledger information, category, name, description, content, sort order, price, VAT, and active/blocked status.
  • Invoices via /invoices and /invoices/{invoice_id}: invoice type, status, identifier, number, dates, customer details, event link, payment terms, amounts, VAT, discount, synchronization status, internal note, and invoice lines.
  • Invoice documents via /invoices/{invoice_id}/file.pdf: PDF version of an invoice, separate for each invoice.
  • Messages and notes linked to an event via /events/{event_id}/messages: subject, message content, type, object link, and author details.
  • Availability via /availability: available, unavailable, and blocked time slots, dates, times, locations, minimum and maximum number of guests, and maximum duration.
  • External object links via /external_objects and /external_objects/get: link between a MICE object and an external system based on object type, internal object ID, and external identifier.
  • Webhook subscriptions via /webhooks and /webhooks/{id}: event type, callback URL, and optional secret key. This is configuration for future synchronization and not a historical data export.
  • POS and cash register-related data: POS setup, products, deposit/credit lines, receipt lines, and the integration with invoicing.

1.2 Metadata, Data Structures, and Formats

  • The data structure is described using OpenAPI 3.1.0.
  • The primary data exchange uses JSON (application/json).
  • Date fields use ISO-style date or date-time values as described in the API specification.
  • Invoices can be exported as PDF (application/pdf).
  • Collections use pagination with `page`, `items_per_page`, `total_items`, `total_pages`, and `next_url` where applicable.

1.3 Digital assets that can be transferred via the public API

  • Invoice PDFs.
  • JSON representations of the objects listed above.
  • Text and HTML content provided in object fields, such as descriptions, content fields, and message content.
  • Webhook configuration and external ID links.

The public API does not support general export or download of attachments, images, logos, uploaded files, or files linked to messages, tasks, contacts, or documents. The logged-in MICE application does, however, offer separate export and download functions for some of these categories; these are described in section 1.4.

1.4 Export Functions in the Logged-In Application for Company-User Admins

In addition to the public API, the following export and download functions are available in the logged-in MICE application for users with the “admin” role, sometimes in conjunction with additional roles, feature flags, or other permissions:

Function Path or entry point Page in the application Format Data Terms and Conditions
Export product catalog /company/products/export Company Settings / Products → More → Export XLSX Products and Variants Manager or Admin
Export customers/suppliers /clients/export Clients → Export CSV with semicolon as delimiter Clients, suppliers, and custom attributes admin
Export contacts /contacts/export Contacts → Export CSV with semicolon as delimiter Contacts, linked customers, and custom attributes admin
Planboard locations /reports/planboards/locations/export.pdf or .xlsx Location Planboard → Export → PDF/Excel PDF or XLSX Location and Event Capacity Planning staff, planner, manager, billing, or admin, plus feature planboards
Planboard products /reports/planboards/products/export.pdf or .xlsx Product Planboard → Export → PDF/Excel PDF or XLSX Product and Activity Planning staff, planner, manager, billing, or admin, plus Planboard features
Event Cost Summary /events/{id}/export/cost-summary Event → Reports → Cost Summary → Export DOC download with HTML content Cost summary for an event staff, planner, manager, billing, or admin, plus event visibility
Event schedule /events/{id}/export/schedule Event → Reports → Schedule → Export DOCX Event schedule and activities staff, planner, manager, billing, or admin, plus event visibility
Event margin calculation /events/{id}/export/margin-calculation Event → Reports → Margin Calculation → Export XLSX or DOC download Product costs, revenue, and margin Planner, Manager, or Admin; event visibility; and the “cost_price” feature
Reports /reports, /reports/revenue, /reports/cancellations, /reports/invoices with export=xlsx Reports / Revenue Report → filters → Export XLSX Events, revenue, cancellations, and invoices Reports or Admin, plus feature reports
Detailed Revenue /reports/revenue/detailed/export Reports → Revenue → Detailed → Export XLSX Revenue by event, category, and product Reports or Admin, plus feature reports
Invoice list /invoices/export/download Invoices → Export → filtered export screen → Export CSV Invoices and optional invoice line items billing, admin
Invoices in UBL /invoices/export/download_ubl Invoices → Export → filtered export screen → Export → UBL ZIP file containing UBL/XML files Invoices billing, admin
Individual invoice /invoices/{id}/invoice.pdf or .xml Invoice details → Download → PDF or UBL PDF or UBL XML Single invoice billing, admin
Client and contact attachments /clients/{id}/download/{attachment} and /contacts/{id}/download/{attachment} Client/Contact details → Documents/attachments → select file Original file Attachments for clients and contacts Client: planner, manager, billing, or admin
Media library /admin/media/files/{id}/download Media Library → open file → Download Original media file Company media and uploads planner, manager, or admin
Documents /documents/{id}/download Event → Documents tab → open document → Download PDF Company documents staff, planner, manager, or admin
Quotes /quotations/{id}/download Quotations list → Event → Documents → quotation detail → Print/Download PDF Company quotations planner, manager, or admin
Event attachments /events/{id}/file/{file_id} Event details → Files/attachments → select attachment Original file Event attachments Depending on event visibility and object permissions
Calendar feed /export/ical/{token} or .ics Company → Settings → Integrations → iCal → Copy feed URL iCalendar Events from the past three months Token-based access

These features are user-initiated exports or downloads within the application. Availability may also depend on the activated subscription, features, the visibility of the event in question, billing ownership, and other object permissions.

2. Data and digital assets for which no general company-user export function has been defined

Based on the public API examined and the logged-in application paths, the following categories have not been identified as general export functions for admins. This does not mean that no underlying fields are available: for example, partial data may be part of an event, invoice, document, or report. It means that no complete, standalone export function was found for the categories listed.

  • Tasks and task boards, including internal task relationships, followers, labels, archive status, and task attachments.
  • Complete structured quote and document files, including document blocks, send logs, publication statuses, templates, and archives. PDF downloads of individual quotes and documents are included in section 1.4.
  • Complete user and access management, including company memberships, roles, permissions, invitations, and access settings.
  • Audit logs, notifications, and a complete internal activity history.
  • A complete export of all attachments and media. Individual client/contact attachments and media files can be downloaded using the functions described in section 1.4; however, no general export has been established for message files, task files, document images, or all files combined.
  • Complete company configuration, including workflows, languages, templates, settings, feature configuration, subscriptions, billing settings, and direct debit authorizations.

3. Data and digital assets protected by intellectual property rights or trade secrets and exempt from migration

The following categories are not offered as general transferable customer data via the public API or exports, as they are part of MICE’s internal operations or intellectual property:

  • MICE’s source code, internal software architecture, algorithms, internal data models, and implementation details.
  • Internal configuration of workflows, permission models, feature flags, operational settings, and management processes.
  • Internal templates, document blocks, technical migration tools, analysis models, and reporting infrastructure, to the extent that these are not specifically stored as customer data.
  • Aggregated, anonymized, or pseudonymized data from multiple customers.
  • Data from other customers, suppliers, or third parties that does not belong to the relevant customer environment.
  • Security data, including API keys, passwords, secret webhook keys, signing secrets, encryption keys, and internal infrastructure data.
  • Data provided by customers or third parties that is subject to their own intellectual property rights, to the extent that MICE is not authorized to transfer such data independently.

The classification of individual customer fields, free text, document content, and files may vary on a case-by-case basis depending on contractual agreements, privacy laws, and third-party rights.

4. Information on procedures for migration and porting using migration tools

4.1 API Procedure

  1. The customer requests an API key or uses an existing key with sufficient permissions.
  2. The customer connects exclusively to the HTTPS base URL https://api.miceoperations.com/api/v1/.
  3. Requests are authenticated with the API key via the Authorization header in accordance with HTTP Basic Authentication. An API key can also be provided as a key query parameter; however, the use of a query parameter is not recommended due to logging and visibility risks.
  4. The client first retrieves the available object collections and processes the results according to the pagination (page, items_per_page, total_pages, and next_url).
  5. For complete event data, the available include_* parameters are used where necessary to include activities, products, packages, locations, customers, planners, and contacts.
  6. Invoice PDFs are retrieved separately using the invoice ID.
  7. The customer checks for error responses, HTTP status codes, totals, relationships, and missing records, and securely stores the export in the target system.
  8. Upon completion, the API key can be revoked or replaced.

4.2 Webhooks

Webhooks can be used to notify another system of new or modified events, including `event.created`, `event.updated`, `event.deleted`, status changes, and certain invoice and activity events. Webhooks do not replace an initial historical export; they are intended for synchronization after the initial transfer.

5. Estimated Time Required for Exporting and Transferring Data and Digital Assets

  • Regular API export of JSON data: typically 2 to 5 business days to develop an extractor, including pagination, relationships, logging, validation, and invoice PDFs.
  • Production-ready, repeatable export: typically a few days.
  • Full transfer, including non-public domains, attachments, and documents: approximately 2 to 4 weeks. The actual duration depends on the number of records, file size, quote and document complexity, third-party rights, and the chosen export procedure.

These estimates are indicative and do not constitute contractual service levels. Export time may increase due to API limits, data volume, manual checks, missing relationships, or validation of personal data and intellectual property rights.

6. Known Risks to the Continuity of MICE’s Features or Services

  • A complete transfer requires multiple paginated API calls and separate downloads.
  • During pagination, concurrent changes may result in duplicate or missing records.
  • Deleted data is not demonstrably available in the same way for all domains. For events, the `include_deleted` option is available; for other object types, equivalent coverage is not available.
  • Attachments, images, quote files, and other digital assets may be excluded from a JSON export.
  • Webhooks do not provide a history and therefore cannot replace an initial export.
  • The API specification and implementation may vary. Changes to status codes, parameters, field types, and response formats are documented in the current API documentation.
  • There is no publicly documented contract describing rate limits, retry behavior, export checkpoints, or guaranteed recoverability.
  • Changes to standards, open interoperability specifications, or the API version may require an update to this registry.

7. IT resources guaranteed by MICE for an effective transition

Based on the current documentation, the following resources are available:

  • A publicly accessible HTTPS REST API with the base URL https://api.miceoperations.com/api/v1/.
  • An OpenAPI 3.1.0 specification containing endpoint, parameter, response, and schema information.
  • JSON as the standardized data format for the API.
  • Pagination and metadata for collection responses.
  • Company-specific API authentication with a revocable API key.
  • Endpoint support for events, activities, customers, suppliers, products, product categories, locations, invoices, invoice PDFs, messages, availability, external object links, and webhooks.
  • HTTP status codes and error structures for success, unauthorized, not found, and validation errors.
  • Webhooks for certain future changes following an initial migration.

The following are
not guaranteed: a full database export, a historical snapshot, a complete export of all attachments and files in a single transfer, export of all internal domains, a fixed export SLA, a guaranteed rate limit, an automatic retry or resume function, and a general combined CSV/XML/ZIP export.

Maintenance of this registry

MICE updates this registry when new API endpoints, data formats, relevant standards, or open interoperability specifications become available, or when existing export capabilities are modified or discontinued. At a minimum, with every material API version change, a review is conducted to determine which data is transferable and which restrictions apply.

This registry is a technical description of the current transfer options. The final legal classification of data as exportable, excluded, a trade secret, or protected by intellectual property rights requires a separate assessment by MICE.