Event Miscellaneous Expenses & Credits

Retrieve a Single Event Miscellaneous Expense/Credit by Id #

Method
GET
Endpoint
Sample Object
Retrieves information about a specific event miscellaneous expense/credit (using the "id" parameter).
Parameters
Name Type Required? Details Description
api_key String Yes
id Number Yes
Id of the specific event miscellaneous expense/credit that you would like to retrieve.
$result_format String No
Pass in "array" to get the miscellaneous expense/credit inside a JSON array (a list with one item).
$on_error_return_empty_result Boolean No
default: false
For a missing or invalid expense/credit id, or a record not found, return HTTP 200 with null (or [null] when $result_format=array). Authentication, rate-limit and unexpected server errors keep their normal HTTP status.
$include_record_revision Boolean No
default: false
Pass in true to add record_revision to the response: an opaque value that describes the current values of the fields this record's update can change (the help page lists what each revision covers). Send it back as expected_revision when you update this record, and the update is refused with HTTP 409 (error_code record_changed) if any of those fields changed in the meantime. In the rare case that the record keeps changing while it is being read, no record_revision can be given and the response is HTTP 409 (error_code record_changed); read it again. If you leave it out, the response has no record_revision.
Code Samples
curl -X GET "https://api.exhibitday.com/v1/events/miscexpensecredit?id=12345" -H "api_key: YOUR_API_KEY"

Example HTTP response body (JSON)

GET /v1/events/miscexpensecredit - HTTP 200
{
  "id": 12345,
  "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345&OtherExpensesTab=1",
  "description": "Sample description",
  "is_credit": false,
  "amount": 0.00,
  "amount_cost_center_breakdown": [],
  "notes": "",
  "payment_due_date": null,
  "payment_status": {
    "id": 0,
    "name": "Not Specified"
  },
  "next_partial_payment_due_date": null,
  "payment_notes": null,
  "event": {
    "id": 12345,
    "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345",
    "name": "Sample Event",
    "start_date": "2026-12-12",
    "end_date": "2026-12-14",
    "participation_type_id": 1,
    "participation_type": "Committed",
    "format_id": 1,
    "format": "In-Person",
    "event_created_timestamp": "2026-11-12T17:00:00Z",
    "event_last_update_timestamp": "2026-11-12T17:00:00Z"
  },
  "event_misc_expense_credit_created_timestamp": "2026-11-12T17:00:00Z",
  "event_misc_expense_credit_last_update_timestamp": "2026-11-12T17:00:00Z",
  "integration_metadata_field_1": "",
  "integration_metadata_field_2": "",
  "integration_metadata_field_3": "",
  "integration_metadata_field_4": "",
  "integration_metadata_field_5": ""
}
Note: Illustrative response. Assume the identified records exist in an illustrative workspace and the request succeeds. Generated IDs, related records and timestamps are illustrative. Item links use illustrative workspace 98765 and the DTO's configured application host (an illustrative production-host fallback is used only if absent). Timestamps are illustrative values formatted by the current API serializer; they do not establish the timezone semantics of stored timestamps. The default response representation is shown; documented options can select another shape. Reference labels are illustrative; assume the workspace uses the standard participation types with no custom choices. Request inputs: {"id":12345}.

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

Method
GET
Endpoint
Retrieves Event Miscellaneous Expenses/Credits using search filters. At least one filter must be passed in: filter_by_event_id, one of the filter_by_integration_metadata_field filters, or filter_by_last_update_timestamp_greater_than_or_equal_to.
Parameters
Name Type Required? Details Description
api_key String Yes
filter_by_event_id Number No
Only include miscellaneous expenses/credits for a given event.
filter_by_integration_metadata_field_1 String No
max length: 3000
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).
filter_by_integration_metadata_field_2 String No
max length: 3000
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).
filter_by_integration_metadata_field_3 String No
max length: 3000
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).
filter_by_integration_metadata_field_4 String No
max length: 3000
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).
filter_by_integration_metadata_field_5 String No
max length: 3000
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).
filter_by_last_update_timestamp_greater_than_or_equal_to String No
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, process and save every page before advancing the cursor. 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, upsert every returned record by id, including boundary records). Deleted miscellaneous expenses/credits are not returned. Any other value is rejected with an error.
$limit Number No
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.
$offset Number No
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.
$result_format String No
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.
$on_error_return_empty_result Boolean No
default: false
For a missing required filter or an invalid ID, filter or paging value, return HTTP 200 with no matching records in the selected result format. Authentication, rate-limit and unexpected server errors keep their normal HTTP status.
Code Samples
curl -X GET "https://api.exhibitday.com/v1/events/miscexpensecredits?filter_by_event_id=12345" -H "api_key: YOUR_API_KEY"

Example HTTP response body (JSON)

GET /v1/events/miscexpensecredits - HTTP 200
{
  "records_found": 1,
  "total_records": 1,
  "has_more": false,
  "list_type": "event_misc_expense_credit",
  "list_data": [
    {
      "id": 12345,
      "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345&OtherExpensesTab=1",
      "description": "Sample description",
      "is_credit": false,
      "amount": 0.00,
      "amount_cost_center_breakdown": [],
      "notes": "",
      "payment_due_date": null,
      "payment_status": {
        "id": 0,
        "name": "Not Specified"
      },
      "next_partial_payment_due_date": null,
      "payment_notes": null,
      "event": {
        "id": 12345,
        "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345",
        "name": "Sample Event",
        "start_date": "2026-12-12",
        "end_date": "2026-12-14",
        "participation_type_id": 1,
        "participation_type": "Committed",
        "format_id": 1,
        "format": "In-Person",
        "event_created_timestamp": "2026-11-12T17:00:00Z",
        "event_last_update_timestamp": "2026-11-12T17:00:00Z"
      },
      "event_misc_expense_credit_created_timestamp": "2026-11-12T17:00:00Z",
      "event_misc_expense_credit_last_update_timestamp": "2026-11-12T17:00:00Z",
      "integration_metadata_field_1": "",
      "integration_metadata_field_2": "",
      "integration_metadata_field_3": "",
      "integration_metadata_field_4": "",
      "integration_metadata_field_5": ""
    }
  ]
}
Note: Illustrative response. Assume the identified records exist in an illustrative workspace and the request succeeds. Generated IDs, related records and timestamps are illustrative. Item links use illustrative workspace 98765 and the DTO's configured application host (an illustrative production-host fallback is used only if absent). Timestamps are illustrative values formatted by the current API serializer; they do not establish the timezone semantics of stored timestamps. The default response representation is shown; documented options can select another shape. Reference labels are illustrative; assume the workspace uses the standard participation types with no custom choices. Request inputs: {"filter_by_event_id":12345}.

Add a New Event Miscellaneous Expense/Credit #

Method
POST
Endpoint
Parameters
Name Type Required? Details Description
api_key String Yes
event_id Number Yes
The id of the event you would like to add the miscellaneous expense/credit to.
description String Yes
max length: 400
A short description of the miscellaneous expense/credit. Accepts up to 400 characters, the same limit as in ExhibitDay (any html tags are stripped and not counted). Longer descriptions are rejected with an error, and the miscellaneous expense/credit is not added.
is_credit Boolean No
default: false
The is_credit flag indicates whether or not the miscellaneous expense/credit you’re adding is a credit. For example, if you’re adding a partial credit the event organizer issued for a booth service, set the is_credit flag to true. Accepted values: true or false (also yes/no, 1/0); any other value is rejected with an error.
amount Number No
The nonnegative amount of the expense/credit, without currency symbols or commas (e.g., 11250.75). Negative amounts are rejected; use is_credit=true for a credit. If omitted, the total is the sum of amount_cost_center_breakdown charges, or 0.00 if there are none. Amounts and allocation charges may contain extra decimals on input; each entered amount and allocation is rounded to two decimal places first, with midpoint values rounded away from zero. Repeated cost-center IDs are then combined, and any remaining amount goes to Unassigned. Stored and returned amounts use cents, including historical values read at greater precision; totals sum the individually rounded lines. Credit sign is applied afterward. Rounded totals of 1,000,000,000,000,000 or more are rejected before changes are saved.
amount_cost_center_breakdown String No
Cost-center allocations as a JSON array of cost_center_id and charge values. Use IDs from /v1/references/cost_centers, or null for Unassigned (shown as Not Specified in responses). Charges must be nonnegative and must not exceed the total; the remainder goes to Unassigned. When amount is omitted, supplied charges determine the total. Invalid JSON, unknown centers, negative charges or allocations exceeding the total return HTTP400 without saving changes. Amounts and allocation charges may contain extra decimals on input; each entered amount and allocation is rounded to two decimal places first, with midpoint values rounded away from zero. Repeated cost-center IDs are then combined, and any remaining amount goes to Unassigned. Stored and returned amounts use cents, including historical values read at greater precision; totals sum the individually rounded lines. Credit sign is applied afterward. Rounded totals of 1,000,000,000,000,000 or more are rejected before changes are saved. Example: [{"cost_center_id":123456,"charge":60.00},{"cost_center_id":null,"charge":40.00}].
payment_status_id Number No
default: 0
The Payment Status Id for the miscellaneous expense/credit. Note: Payment status only applies to miscellaneous expenses. If you pass in a payment_status_id for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. You can use the following endpoint to retrieve a list of available payment_status_id's: /v1/references/payment_statuses. Any other value is rejected with an error.
payment_due_date Date No
Payment due date in YYYY-MM-DD format. Note: Payment Due Date only applies to miscellaneous expenses. If you pass in a payment_due_date for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. A value that is not a valid date is rejected with an error.
next_payment_due_date Date No
The next payment due date in YYYY-MM-DD format. This field only applies to expenses with payment_status_id 2 (Partially Paid). It is ignored for credits and other payment statuses. Responses use next_partial_payment_due_date; either name is accepted as input. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.
next_partial_payment_due_date Date No
An input alias for next_payment_due_date. The same payment-status rules apply. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.
payment_notes String No
max length: 200
Notes about the payment for the expense. Note: Payment notes only apply to miscellaneous expenses. If you pass in a payment_notes for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored.
notes String No
max length: 30000
Notes about the miscellaneous expense/credit. Only accepts plain text. Any html tags in the value you pass in will be stripped. New line characters will get replaced with a <br/> tag, and the text is stored HTML-encoded, so it is returned as HTML (a < b comes back as a &lt; b). Accepts up to 30,000 characters as stored, including formatting. Some characters take more space when stored: each line break counts as the 5 characters of <br/>, the characters & < > " ' count as their HTML codes (for example, & is stored as &amp;), and accented letters, symbols and non-breaking spaces such as é, ü, © and ° count as 6 characters each (é is stored as &#233;). The notes must also fit the notes editor in ExhibitDay, which counts up to 30,000 characters of its own HTML: it adds 7 characters of formatting and counts letters and symbols such as é ’ “ — € as their HTML codes (for example, ’ counts as the 7 characters of &rsquo;). Longer notes are rejected with an error, and the miscellaneous expense/credit is not added.
integration_metadata_field_1 String No
max length: 3000
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).
integration_metadata_field_2 String No
max length: 3000
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).
integration_metadata_field_3 String No
max length: 3000
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).
integration_metadata_field_4 String No
max length: 3000
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).
integration_metadata_field_5 String No
max length: 3000
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).
Code Samples
curl -X POST https://api.exhibitday.com/v1/events/miscexpensecredit -H "api_key: YOUR_API_KEY" -H "Content-Type: application/json" -d "{\"event_id\":12345,\"description\":\"Sample description\"}"

Example HTTP response body (JSON)

POST /v1/events/miscexpensecredit - HTTP 200
{
  "id": 23456,
  "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345&OtherExpensesTab=1",
  "description": "Sample description",
  "is_credit": false,
  "amount": 0.00,
  "amount_cost_center_breakdown": [],
  "notes": "",
  "payment_due_date": null,
  "payment_status": {
    "id": 0,
    "name": "Not Specified"
  },
  "next_partial_payment_due_date": null,
  "payment_notes": null,
  "event": {
    "id": 12345,
    "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=12345",
    "name": "Sample Event",
    "start_date": "2026-12-12",
    "end_date": "2026-12-14",
    "participation_type_id": 1,
    "participation_type": "Committed",
    "format_id": 1,
    "format": "In-Person",
    "event_created_timestamp": "2026-11-12T17:00:00Z",
    "event_last_update_timestamp": "2026-11-12T17:00:00Z"
  },
  "event_misc_expense_credit_created_timestamp": "2026-11-12T17:00:00Z",
  "event_misc_expense_credit_last_update_timestamp": "2026-11-12T17:00:00Z",
  "integration_metadata_field_1": "",
  "integration_metadata_field_2": "",
  "integration_metadata_field_3": "",
  "integration_metadata_field_4": "",
  "integration_metadata_field_5": ""
}
Note: Illustrative response. Assume the identified records exist in an illustrative workspace and the request succeeds. Generated IDs, related records and timestamps are illustrative. Item links use illustrative workspace 98765 and the DTO's configured application host (an illustrative production-host fallback is used only if absent). Timestamps are illustrative values formatted by the current API serializer; they do not establish the timezone semantics of stored timestamps. The default response representation is shown; documented options can select another shape. Reference labels are illustrative; assume the workspace uses the standard participation types with no custom choices. Request inputs: {"event_id":12345,"description":"Sample description"}.

Update an Event Miscellaneous Expense/Credit #

Method
PATCH
Endpoint
To update an event miscellaneous expense/credit, only pass in the properties that you want to update. A miscellaneous expense/credit cannot be moved to another event. To clear a property that supports clearing, pass in null; an empty value leaves the property unchanged (the warnings property in the response names any such parameters). If the update is successful, the message property in the response will contain a list of event miscellaneous expense/credit properties that were actually changed.
Parameters
Name Type Required? Details Description
api_key String Yes
id Number Yes
The id of the event miscellaneous expense/credit you would like to update.
description String No
max length: 400
A short description of the miscellaneous expense/credit. Accepts up to 400 characters, the same limit as in ExhibitDay (any html tags are stripped and not counted). Longer descriptions are rejected with an error, and nothing is changed. A description that is already stored longer than this can be kept as it is or shortened, but not made longer.
is_credit Boolean No
Whether this record is a credit: true/false, yes/no or 1/0. Blank leaves the current type unchanged. An actual expense/credit conversion clears financial details belonging to the previous type while preserving amount, allocations, description and other applicable fields. Valid expense payment fields supplied when converting to an expense apply afterward. Omitted payment fields remain unchanged when type is unchanged, subject to normal next-payment-date normalization. This API exposes expense payment fields, not credit-status/date/note fields. Existing records are not changed until a conversion request; no additional confirmation step is required.
amount Number No
The nonnegative amount of the expense/credit, without currency symbols or commas. Negative amounts are rejected; use is_credit=true for a credit. Null clears the costs to 0.00. An unchanged rounded amount with omitted or blank allocation breakdown preserves the current split; a changed amount with omitted breakdown replaces the split with Unassigned. Amounts and allocation charges may contain extra decimals on input; each entered amount and allocation is rounded to two decimal places first, with midpoint values rounded away from zero. Repeated cost-center IDs are then combined, and any remaining amount goes to Unassigned. Stored and returned amounts use cents, including historical values read at greater precision; totals sum the individually rounded lines. Credit sign is applied afterward. Rounded totals of 1,000,000,000,000,000 or more are rejected before changes are saved.
amount_cost_center_breakdown String No
Cost-center allocations as a JSON array of cost_center_id and charge values. Use IDs from /v1/references/cost_centers, or null for Unassigned (shown as Not Specified in responses). Charges must be nonnegative and must not exceed the total; the remainder goes to Unassigned. When amount is omitted, supplied charges determine the total. Invalid JSON, unknown centers, negative charges or allocations exceeding the total return HTTP400 without saving changes. Amounts and allocation charges may contain extra decimals on input; each entered amount and allocation is rounded to two decimal places first, with midpoint values rounded away from zero. Repeated cost-center IDs are then combined, and any remaining amount goes to Unassigned. Stored and returned amounts use cents, including historical values read at greater precision; totals sum the individually rounded lines. Credit sign is applied afterward. Rounded totals of 1,000,000,000,000,000 or more are rejected before changes are saved. Example: [{"cost_center_id":123456,"charge":60.00},{"cost_center_id":null,"charge":40.00}]. On PATCH, null clears the allocations to Unassigned while preserving the current total unless amount is also supplied. Omitted or blank breakdown alone preserves existing allocations.
payment_status_id Number No
The Payment Status Id for the miscellaneous expense/credit. Note: Payment status only applies to miscellaneous expenses. If you pass in a payment_status_id for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. You can use the following endpoint to retrieve a list of available payment_status_id's: /v1/references/payment_statuses. Any other value is rejected with an error. To reset the payment status to 0 (Not Specified), pass in null.
payment_due_date Date No
Payment due date in YYYY-MM-DD format. Note: Payment Due Date only applies to miscellaneous expenses. If you pass in a payment_due_date for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. A value that is not a valid date is rejected with an error.
next_payment_due_date Date No
The next payment due date in YYYY-MM-DD format. This field only applies to expenses with payment_status_id 2 (Partially Paid). It is ignored for credits and other payment statuses. Responses use next_partial_payment_due_date; either name is accepted as input. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.
next_partial_payment_due_date Date No
An input alias for next_payment_due_date. The same payment-status rules apply. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.
payment_notes String No
max length: 200
Notes about the payment for the expense. Note: Payment notes only apply to miscellaneous expenses. If you pass in a payment_notes for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored.
notes String No
max length: 30000
Notes about the miscellaneous expense/credit. Only accepts plain text. Any html tags in the value you pass in will be stripped. New line characters will get replaced with a <br/> tag, and the text is stored HTML-encoded, so it is returned as HTML (a < b comes back as a &lt; b). Accepts up to 30,000 characters as stored, including formatting. Some characters take more space when stored: each line break counts as the 5 characters of <br/>, the characters & < > " ' count as their HTML codes (for example, & is stored as &amp;), and accented letters, symbols and non-breaking spaces such as é, ü, © and ° count as 6 characters each (é is stored as &#233;). The notes must also fit the notes editor in ExhibitDay, which counts up to 30,000 characters of its own HTML: it adds 7 characters of formatting and counts letters and symbols such as é ’ “ — € as their HTML codes (for example, ’ counts as the 7 characters of &rsquo;). Longer notes are rejected with an error, and nothing is changed. Notes that are already stored longer than this can be kept as they are or shortened, but not made longer.
integration_metadata_field_1 String No
max length: 3000
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).
integration_metadata_field_2 String No
max length: 3000
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).
integration_metadata_field_3 String No
max length: 3000
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).
integration_metadata_field_4 String No
max length: 3000
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).
integration_metadata_field_5 String No
max length: 3000
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).
expected_revision String No
The record_revision value from a GET of this record with $include_record_revision=true. When you send it, the update is saved only if none of the fields the revision covers has changed since that read (every field this update can change; the help page lists what each revision covers). A change that was undone in the meantime does not count. Otherwise nothing is changed and the response is HTTP 409 with error_code record_changed. Then read the record again, review its current values and decide whether to send your change again (the API never retries it for you). Treat the value as opaque: do not build or parse it. If you leave it out, the update is saved without this check. A blank, null or malformed value is refused with HTTP 400 (error_code invalid_request), and so are different values sent for it more than once. A successful update returns the record's new record_revision. It grants no permission (every request is still checked as usual) and is separate from Idempotency-Key and ETag/If-None-Match.
Code Samples
curl -X PATCH https://api.exhibitday.com/v1/events/miscexpensecredit -H "api_key: YOUR_API_KEY" -H "Content-Type: application/json" -d "{\"id\":12345,\"description\":\"Updated description\"}"

Example HTTP response body (JSON)

PATCH /v1/events/miscexpensecredit - HTTP 200
{
  "status_code": 200,
  "status": "OK",
  "message": "Event Miscellaneous Expense/Credit Update Successful. Event Miscellaneous Expense/Credit properties that were changed: description",
  "errors": []
}
Note: Illustrative response. Assume the identified records exist in an illustrative workspace and the request succeeds. Generated IDs, related records and timestamps are illustrative. Item links use illustrative workspace 98765 and the DTO's configured application host (an illustrative production-host fallback is used only if absent). Timestamps are illustrative values formatted by the current API serializer; they do not establish the timezone semantics of stored timestamps. The default response representation is shown; documented options can select another shape. Reference labels are illustrative; assume the workspace uses the standard participation types with no custom choices. Request inputs: {"id":12345,"description":"Updated description"}.

Delete an Event Miscellaneous Expense/Credit #

Method
DELETE
Endpoint
Permanently deletes an event's miscellaneous expense/credit. It cannot be undone.
Parameters
Name Type Required? Details Description
api_key String Yes
id Number Yes
The id of the event miscellaneous expense/credit you would like to delete.
Code Samples
curl -X DELETE "https://api.exhibitday.com/v1/events/miscexpensecredit?id=12345" -H "api_key: YOUR_API_KEY"

Example HTTP response body (JSON)

DELETE /v1/events/miscexpensecredit - HTTP 200
{
  "status_code": 200,
  "status": "OK",
  "message": "Event Miscellaneous Expense/Credit Deleted",
  "errors": []
}
Note: Illustrative response. Assume the identified records exist in an illustrative workspace and the request succeeds. Generated IDs, related records and timestamps are illustrative. Item links use illustrative workspace 98765 and the DTO's configured application host (an illustrative production-host fallback is used only if absent). Timestamps are illustrative values formatted by the current API serializer; they do not establish the timezone semantics of stored timestamps. The default response representation is shown; documented options can select another shape. Reference labels are illustrative; assume the workspace uses the standard participation types with no custom choices. Request inputs: {"id":12345}.