Search API documentation

Type to search the API docs.

Send a Weekly Progress Report for Events and Tasks

List your upcoming shows, count last month's Events and Completed Tasks, and give each Assignee a list of the Tasks due next week.

Example use case

Every Monday your events manager wants one page: the shows coming up, how last month went, and what each person has due in the week ahead.

What you'll end up with

The lists for your report: upcoming Events, last month's Events and Completed Tasks, and each Assignee's Tasks due next week, with their email address.

Before you start

Have a workspace API key. Decide how far ahead “upcoming” should look. The example uses 90 days.

Good to know

The requests only read. Build the report from the results and send it with your own email tool or chat app.

At a glance

Time to try

About 10 minutes

Effect on your data

Read-only

Endpoints

3

The requests only read Events, Tasks and people. They change nothing and send no email.

How it works

  1. List the Events that start in the next 90 days.
  2. List the Events that took place last month and count the Tasks Completed last month.
  3. List each Assignee's Incomplete Tasks due next week, with their email address.

Build the report

The examples assume you build the report on Sunday, November 22, 2026. Next week is November 23 to 29, and last month is October 2026. Work out last month and next week in your workspace's time zone.

Step 1: List upcoming shows

Find the Events that start between tomorrow and 90 days from now, earliest first.

curl -X GET "https://api.exhibitday.com/v1/events?filter_by_start_date_greater_than_or_equal_to=2026-11-23&filter_by_start_date_smaller_than_or_equal_to=2027-02-20&%24return_event_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 Event",
      "start_date": "2026-12-22",
      "end_date": "2026-12-24",
      "participation_type": "Committed",
      "format": "In-Person"
    }
  ]
}

Check: Print each Event's name, dates, Participation Status (participation_type) and format (In-Person, Virtual or Hybrid). Add filter_by_event_participation_type_id=1 to list only Committed Events. For every upcoming Event, including Events in progress, send filter_by_event_start_date_category=upcoming instead of the two date filters.

Step 2: List the Events that took place last month

Find every Event that overlaps last month: it started on or before the last day of the month and ended on or after its first day.

curl -X GET "https://api.exhibitday.com/v1/events?filter_by_start_date_smaller_than_or_equal_to=2026-10-31&filter_by_end_date_greater_than_or_equal_to=2026-10-01&%24return_event_lites=true&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"

Check: total_records is the number of Events. List each one with its Participation Status (participation_type) so the report shows which shows you attended. An Event that ran from September 30 to October 2 counts, because part of it was in October. Don't send filter_by_event_start_date_category here. It overrides the date filters.

Step 3: Count the Tasks Completed last month

There's no completion-date filter, so ask for Completed Tasks changed since the first day of last month, then count the ones Completed in that month.

curl -X GET "https://api.exhibitday.com/v1/tasks?filter_by_completed_only=true&filter_by_last_update_timestamp_greater_than_or_equal_to=2026-10-01T00%3A00%3A00Z&%24return_task_lites=true&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"

Check: Count only Tasks whose task_completed_timestamp_est falls in last month. Despite its name, this Task Lite field holds the UTC time, the same value as task_completed_timestamp in a full Task. A Task Completed last month was last changed then or later, so this filter never leaves it out.

Step 4: List each Assignee's Tasks due next week

Find Incomplete Tasks with an Assignee and a Due Date next week, then group them by person.

curl -X GET "https://api.exhibitday.com/v1/tasks?filter_by_incomplete_only=true&filter_by_has_assignee=true&filter_by_due_date_greater_than_or_equal_to=2026-11-23&filter_by_due_date_smaller_than_or_equal_to=2026-11-29&%24return_task_lites=true&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"

Check: In Task Lite results, group rows by assignee_user_id and print assignee_display_name, the Due Date, the Task name and event.name. A General Task has no Event. For one person only, send filter_by_assignee_user_id instead of filter_by_has_assignee.

Step 5: Look up each Assignee's email address

List the people who can be assigned Tasks. This list comes back in one response, without pages.

curl -X GET "https://api.exhibitday.com/v1/references/users_and_resources?filter_by_can_have_tasks_assigned=true" -H "Authorization: Bearer YOUR_API_KEY"

Example response (shortened)

{
  "list_data": [
    {
      "id": "11111111-2222-4333-8444-555555555555",
      "display_name": "Jane Smith",
      "email": "jane@example.invalid",
      "can_have_tasks_assigned": true
    }
  ]
}

Check: Match id to assignee_user_id from Step 4. Treat user IDs as text.

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.
filter_by_due_date_greater_than_or_equal_to and filter_by_due_date_smaller_than_or_equal_toThe first and last day of next week as YYYY-MM-DD. The example uses November 23 to 29, 2026.
$limit and $offsetThe example reads up to 50 matches starting at offset 0.

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 GET "https://api.exhibitday.com/v1/tasks?filter_by_incomplete_only=true&filter_by_has_assignee=true&filter_by_due_date_greater_than_or_equal_to=2026-11-23&filter_by_due_date_smaller_than_or_equal_to=2026-11-29&%24return_task_lites=true&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"

Example response

{
  "records_found": 1,
  "total_records": 1,
  "has_more": false,
  "list_type": "task",
  "list_data": [
    {
      "id": 12345,
      "exhibitday_url": "https://www.exhibitday.com/Workspace/TaskView/98765?tid=12345",
      "event_task_section_id": null,
      "event_task_section": null,
      "display_rank": 0,
      "name": "Sample task",
      "due_date": null,
      "assignee": null,
      "assigned_by": null,
      "contributors": [
        {
          "id": "11111111-2222-4333-8444-555555555555",
          "first_name": "Jane",
          "last_name": "Smith",
          "display_name": "Jane Smith",
          "email": "jane@example.invalid",
          "type": "user",
          "workspace_role": "team_member",
          "is_active": true
        },
        {
          "id": "66666666-7777-4888-8999-aaaaaaaaaaaa",
          "first_name": "Alex",
          "last_name": "Morgan",
          "display_name": "Alex Morgan",
          "email": "alex@example.invalid",
          "type": "user",
          "workspace_role": "team_member",
          "is_active": true
        }
      ],
      "is_completed": false,
      "task_completed_timestamp": null,
      "task_completed_by": null,
      "details": "",
      "comments": null,
      "event": null,
      "task_created_by": {
        "id": "11111111-2222-4333-8444-555555555555",
        "first_name": "Jane",
        "last_name": "Smith",
        "display_name": "Jane Smith",
        "email": "jane@example.invalid",
        "type": "user",
        "workspace_role": "team_member",
        "is_active": true
      },
      "task_created_timestamp": "2026-11-22T17:00:00Z",
      "task_last_update_timestamp": "2026-11-22T17:00:00Z",
      "integration_metadata_field_1": "",
      "integration_metadata_field_2": "",
      "integration_metadata_field_3": "",
      "integration_metadata_field_4": "",
      "integration_metadata_field_5": ""
    }
  ]
}
Note: GET /v1/tasks - HTTP 200. One page of Incomplete Tasks due next week, each with its Assignee. Group them by Assignee to build each person's list.

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

  • Read every page. While has_more is true, ask for the next page with the same filters and add 50 to $offset.
  • Due Date filters and the Events date filters take calendar dates. today, yesterday and tomorrow work in the Due Date filters and use your workspace's time zone.
  • Completion times are in UTC. A Task Completed late on the last evening of the month in your time zone may count in the next month.
  • Tasks with no Due Date and unassigned Tasks aren't in Step 4. Add filter_by_no_due_date=true or filter_by_assignee_user_id=null in a separate request to report them.
  • Tasks can't be assigned to Resources, so every Assignee in Step 4 is a user. Someone who has since left your workspace may still be the Assignee but isn't in Step 5's list, so check those Tasks yourself.