Find Event Miscellaneous Expense(s)/Credit(s)

Only include miscellaneous expenses/credits for a given event.

Only include event miscellaneous expenses/credits that have their integration_metadata_field_1 property equal to the value you pass in for this parameter. Note: The integration_metadata_field_1 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

Only include event miscellaneous expenses/credits that have their integration_metadata_field_2 property equal to the value you pass in for this parameter. Note: The integration_metadata_field_2 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

Only include event miscellaneous expenses/credits that have their integration_metadata_field_3 property equal to the value you pass in for this parameter. Note: The integration_metadata_field_3 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

Only include event miscellaneous expenses/credits that have their integration_metadata_field_4 property equal to the value you pass in for this parameter. Note: The integration_metadata_field_4 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

Only include event miscellaneous expenses/credits that have their integration_metadata_field_5 property equal to the value you pass in for this parameter. Note: The integration_metadata_field_5 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

Only include miscellaneous expenses/credits that were added or changed on or after this date and time, for example 2026-10-14T18:30:00 (a date alone, such as 2026-10-14, means midnight). Responses give event_misc_expense_credit_last_update_timestamp in UTC (it ends in Z), and that value can be passed back unchanged; a value without an offset is read as US Eastern time, and any other offset (e.g., 2026-10-14T18:30:00-04:00) is converted. To sync changes, save the latest event_misc_expense_credit_last_update_timestamp you receive and pass it in next time (miscellaneous expenses/credits changed at exactly that time come back again, so skip ids you already have). Deleted miscellaneous expenses/credits are not returned. Any other value is rejected with an error.

The most miscellaneous expenses/credits to return (a whole number of 1 or more). Use it with $offset to read a long list in pages: total_records in the response counts every matching miscellaneous expense/credit and has_more is true while more pages follow (the X-Total-Count header carries the total too). Without $limit, every matching miscellaneous expense/credit is returned.

How many miscellaneous expenses/credits to skip before the first one returned (a whole number; 0 by default). For the next page, add the number of miscellaneous expenses/credits you received to $offset.

Pass in "array" to get the results as a plain JSON array (without records_found, total_records, has_more and list_type; the X-Total-Count header still gives the total), or "wrapped_in_array" to get the usual response inside a JSON array.

If the request has an error (e.g., no filter or an invalid filter value), return an empty list with HTTP status 200 instead of an error response.

The ETag of a response you already have: while the data is unchanged the API answers 304 Not Modified without a body.