Search API documentation

Type to search the API docs.

Plan Next Year's Show by Copying Last Year's Event

Copy last year's Event into a new Event for next year's show, choose what comes along, then set its Exhibit Hall dates and review the copied Tasks.

Example use case

Sample Expo comes around every March. You want next year's Event with the same Tasks, Task Sections and Event Information, without retyping last year's plan.

What you'll end up with

A new Event for next year, a mapping from each of last year's Tasks to its copy, and the Exhibit Hall dates you set.

Before you start

Have a workspace API key, last year's Event name and next year's show dates. Your workspace plan must include Copy/Duplicate Event.

Good to know

Last year's Event stays as it is. By default the copy brings Event Information and Tasks. You choose anything else.

At a glance

Time to try

About 15 minutes

Effect on your data

Creates records

Endpoints

5

The example creates one Event with copies of last year's Event Information and Tasks. It sends notify=false, so nobody gets an email. Step 3 replaces the new Event's Exhibit Hall dates.

How it works

  1. Find last year's Event by name and year.
  2. Copy it into a new Event with next year's name and dates.
  3. Set the new Event's Exhibit Hall dates, then review the copied Tasks.

Copy the Event or copy Tasks?

This guide: Copy/Duplicate EventCopy Tasks from a Previous Event
RequestPOST /v1/events/copyPOST /v1/tasks/import_from_event
CreatesA new EventNothing new except Tasks, in an Event you already have
CopiesEvent Information and Tasks by default. Booth, Staff, Travel, Shipments, Giveaways, Sponsorships, Playbook, Misc. Expenses & Credits, Budget, Objectives and your Special tab when you ask.Selected Tasks only
Task SectionsCopied with the TasksLeft behind. You choose one target section.

Use Copy Tasks from a Previous Event when next year's Event exists, for example because your CRM created it.

Copy the Event and finish setting it up

Step 1: Find last year's Event

Search by part of the name and the year the show started. This example looks for Sample Expo in 2026.

curl -X GET "https://api.exhibitday.com/v1/events?filter_by_event_name_contains_text=Sample%20Expo&filter_by_event_start_date_category=2026&%24return_event_lites=true" -H "Authorization: Bearer YOUR_API_KEY"

Example response (shortened)

{
  "records_found": 1,
  "total_records": 1,
  "has_more": false,
  "list_data": [
    {
      "id": 12345,
      "name": "Sample Event",
      "start_date": "2026-11-20",
      "end_date": "2026-11-22",
      "participation_type": "Committed"
    }
  ]
}

Check: Keep the id of the one Event you mean. A year in filter_by_event_start_date_category finds Events that start in that year. To search a date range instead, use filter_by_start_date_greater_than_or_equal_to and filter_by_start_date_smaller_than_or_equal_to and leave the category out.

Step 2: Copy the Event

Send last year's Event ID, next year's name and dates, and the parts you want. Add the header Idempotency-Key: YOUR_UNIQUE_KEY so a retry can reuse the original result.

curl -X POST "https://api.exhibitday.com/v1/events/copy" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d "{\"event_id\":12345,\"name\":\"Sample Expo 2027\",\"start_date\":\"2027-03-09\",\"end_date\":\"2027-03-11\",\"copy_tasks\":true,\"task_due_date_mode\":\"same_offset\",\"notify\":false}"

Example response (shortened)

{
  "source_event_id": 12345,
  "id": 23456,
  "name": "Sample Expo 2027",
  "start_date": "2027-03-09",
  "end_date": "2027-03-11",
  "tasks_copied": 1,
  "files_queued": 0,
  "files_skipped": 0,
  "tasks": [
    {
      "source_task_id": 34567,
      "id": 45678,
      "exhibitday_url": "https://www.exhibitday.com/Workspace/TaskView/98765?tid=45678"
    }
  ]
}

Choose what to copy. The labels are the ones in the website's Copy/Duplicate Event dialog.

OptionWebsite labelDefaultWhat it copies
nameEvent NameCopy of and last year's nameThe new Event's name.
start_date, end_dateEvent DatesLast year's datesSend both as YYYY-MM-DD, or neither.
participation_type_idParticipation StatusLast year's statusCommitted, Considering, Not Going or a custom status. If last year's status is no longer available, the copy uses Considering. IDs come from GET /v1/references/event_participation_types.
copy_infoCopy data under the “Event Information” tabtrueInformation fields, their saved documents and custom fields.
copy_info_datesInclude Exhibit Hall dates/times and Booth Setup and Dismantle dates/times (not recommended)falseLast year's Exhibit Hall, Booth Setup and Booth Dismantle dates, unchanged. Leave it off and set next year's in Step 3.
copy_tasksCopy TaskstrueTasks, their Task Sections and saved attachments. Copies start Incomplete, with no comments.
keep_task_assigneesAssign the new/copied tasks to the same assignees as the current tasksfalseKeeps Assignees and tagged Contributors. The default leaves the copies unassigned.
task_due_date_modeAssign due dates to the new/copied tasksnonenone leaves Due Dates empty. same_offset keeps each Task the same number of days from the Event start date. same_date keeps last year's exact dates.
copy_booth (and copy_booth_costs)Copy data under the event “Booth” tab (Include booth/booth Service costs and invoices)falseBooth details and Booth Services (and their costs, payment details and invoices).
copy_staff (and copy_staff_costs)Copy event Attendees (Include attendee registration costs and invoices)falseAttendee / Registration records (and their costs).
copy_travel (and copy_travel_costs)Copy Travel ReservationsfalseTravel Reservations (and their costs).
copy_shipments (and copy_shipments_costs)Copy ShipmentsfalseShipments and their Shipment Components (and their costs).
copy_giveaways (and copy_giveaways_costs)Copy GiveawaysfalseGiveaways (and their costs).
copy_sponsorships (and copy_sponsorships_costs)Copy SponsorshipsfalseSponsorships (and their costs).
copy_playbook (and copy_playbook_costs)Copy PlaybookfalsePlaybook Activities (and their costs).
copy_misc_expenses_credits (and copy_misc_expenses_credits_costs)Copy Misc. Expenses & CreditsfalseMisc. Expenses & Credits (and their amounts).
copy_budgetCopy BudgetfalseBudget amounts and budget notes.
copy_objectives (and copy_objective_scores)Copy Objectives (Copy the specified achievement ratings for the objectives, and the notes (not recommended))falseObjectives and priorities (and last year's achievement ratings and notes).
copy_special_tabCopy (your Special tab's name)falseYour Special tab's custom fields.
notify(none)truetrue emails the people tagged on the copied records once, according to their email preferences, as the website does after Copy/Duplicate Event. false sends no email.

Each _costs option applies only when its area is copied. The Event's General Attachments and invoice attachments aren't copied.

Check: Save the new Event id and each source_task_id with its new id. Each files entry is queued (the new file's id) or skipped (with a reason).

Step 3: Set next year's Exhibit Hall dates

Read the new Event's Exhibit Hall dates with a revision.

curl -X GET "https://api.exhibitday.com/v1/events/dates?event_id=23456&filter_by_date_type_id=1&%24include_record_revision=true" -H "Authorization: Bearer YOUR_API_KEY"

Then replace the whole list. Send expected_revision set to the record_revision from your read, in place of YOUR_RECORD_REVISION.

curl -X PATCH "https://api.exhibitday.com/v1/events/dates" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d "{\"event_id\":23456,\"date_type_id\":1,\"dates\":[{\"date\":\"2027-03-09\",\"start_time\":\"10:00\",\"end_time\":\"17:00\",\"timezone\":\"EST\",\"description\":\"Exhibit hours\"}],\"expected_revision\":\"YOUR_RECORD_REVISION\"}"

Check: The list is replaced as a whole, so send every Exhibit Hall day. Use date_type_id 2 for Booth Setup or 3 for Booth Dismantle. If you get record_changed (HTTP 409), read the dates again before sending another update. See Set an Event's Exhibit Hall Dates and Hours for the details.

Step 4: Review the copied Tasks

List the new Event's Tasks and compare them with the mapping from Step 2.

curl -X GET "https://api.exhibitday.com/v1/tasks?filter_by_event_id=23456&%24return_task_lites=true&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"

Example response (shortened)

{
  "records_found": 1,
  "total_records": 1,
  "has_more": false,
  "list_data": [
    {
      "id": 12345,
      "name": "Sample task",
      "due_date": null,
      "is_completed": false
    }
  ]
}

Check: total_records should equal tasks_copied. With same_offset, a Task due 14 days before last year's show is due 14 days before next year's. While has_more is true, ask for the next page with the same filters and add 50 to $offset.

Try it

Before running the example

ValueWhat to put in it
YOUR_API_KEYYour workspace API key. Keep it out of shared code and logs.
event_idLast year's Event ID, from Step 1. The example uses 12345.
nameThe new Event's name. The example uses Sample Expo 2027.
start_date and end_dateNext year's show dates as YYYY-MM-DD. The example uses March 9 to 11, 2027.
copy_tasks and task_due_date_modeThe example copies the Tasks and keeps each Due Date the same number of days from the Event start date.
notifyThe example sends false, so nobody gets an email.

Copy the complete example in your language and run it. To try another step, change the request to match one of the steps above.

Complete example program

Code Samples
curl -X POST "https://api.exhibitday.com/v1/events/copy" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d "{\"event_id\":12345,\"name\":\"Sample Expo 2027\",\"start_date\":\"2027-03-09\",\"end_date\":\"2027-03-11\",\"copy_tasks\":true,\"task_due_date_mode\":\"same_offset\",\"notify\":false}"

Example response

{
  "source_event_id": 12345,
  "id": 23456,
  "exhibitday_url": "https://www.exhibitday.com/Workspace/Event/98765?eid=23456",
  "name": "Sample Expo 2027",
  "start_date": "2027-03-09",
  "end_date": "2027-03-11",
  "tasks_copied": 1,
  "files_queued": 0,
  "files_skipped": 0,
  "tasks": [
    {
      "source_task_id": 34567,
      "id": 45678,
      "exhibitday_url": "https://www.exhibitday.com/Workspace/TaskView/98765?tid=45678"
    }
  ],
  "files": []
}
Note: POST /v1/events/copy - HTTP 200. The new Event and the mapping from each copied Task to its new Task. Keep the new Event's id for the next steps.

The curl example uses Bash. Node.js needs version 18 or later (save as .mjs). Python uses Requests. C# needs a .NET 8 console project (Program.cs). Java needs Java 11 or later (ExhibitDayExample.java). PHP needs PHP with cURL. Ruby and Go use their standard libraries.

Things to keep in mind

  • Copied files are copied in the background. queued doesn't mean the file can be downloaded yet. A download can return file_copy_pending (HTTP 409) until copying finishes.
  • If last year's Event is busy with another save, the copy returns record_changed (HTTP 409) and creates nothing. Try again in a moment with the same key.
  • If you lose the response, retry the exact request with the same key. For 24 hours, a completed copy returns the saved response with Idempotent-Replayed: true. If the API returns idempotency_key_indeterminate, search for the new name (Step 1) before copying again.
  • The website warns when another Event has a similar name on the same dates. Search for next year's name first so you don't create two.
  • Your plan and access to each area still apply. Areas you can't read aren't copied.