# Find Users and Resources by Name, Email or Role

> Look up a person in your workspace by name, email or role, pick a Task Assignee, check invitations and see which Events they're involved in.

This is the Markdown copy of https://api.exhibitday.com/Help/V1?guide=find-people for AI tools. Code examples are in curl, JavaScript, Python and C#; the help page shows all 8 languages, and https://api.exhibitday.com/llms-full.txt has the complete reference in one file. Index of all pages: https://api.exhibitday.com/llms.txt

Look up a person in your workspace by name, email or role, pick a Task Assignee, check invitations and see which Events they're involved in.

Example use case

Your HR system sends you “Smith, Jane”. You want her ExhibitDay user ID to assign her a Task, to check she hasn't already been invited, and to see which upcoming shows she's working on.

What you'll end up with

The person's `id`, their workspace role, and the Events they're involved in.

Before you start

Have a workspace API key and the person's name or email address.

Good to know

The lists include the active users and Resources from Users & Permissions. A Resource is a non-user, such as a speaker, a contractor or temporary booth staff, added on the website with Add a Resource (non-user). Resources can't sign in.

## At a glance

Time to try

About 10 minutes

Effect on your data

Read-only

Endpoints

4

The requests only read people, open invitations and Event involvements. They change nothing and send no email.

- [`GET /v1/workspace_settings/users`](https://api.exhibitday.com/Help/V1?epf=6&amp;topic=users#get-v1-workspace_settings-users)
- [`GET /v1/references/users_and_resources`](https://api.exhibitday.com/Help/V1?epf=3#get-v1-references-users_and_resources)
- [`GET /v1/workspace_settings/users/invitations`](https://api.exhibitday.com/Help/V1?epf=6&amp;topic=user-invitations#get-v1-workspace_settings-users-invitations)
- [`GET /v1/workspace_settings/users/involvements`](https://api.exhibitday.com/Help/V1?epf=6&amp;topic=users#get-v1-workspace_settings-users-involvements)

## How it works

1. Search Users & Permissions by name, email or role, and keep the person's `id`.
2. Use the users and Resources list to pick someone who can be assigned Tasks.
3. Check open invitations by email, then list the Events the person is involved in.

## How search matching works

- Searches ignore letter case, accents and spaces before or after your text. `Zoe`, `Zoë` and `ZOE` find the same person.
- `%`, `_` and `[` match themselves. Search for them like any other character.
- A blank name or email search is ignored, so it doesn't narrow the list.
- The name search looks for every word you send in the first or last name, in any order. `Jane Smith`, `Smith Jane` and `Smith, Jane` find the same person, whichever name format your workspace uses.
- The name search doesn't look at email addresses. Use the email filter for those.
- The email filter matches the whole address.

## Find a person and their work

## Step 1: Search by name

Find users and Resources whose first or last name contains every word you send. The results are sorted by display name.

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

**Example response (shortened)**

```json
{
  "records_found": 2,
  "total_records": 2,
  "has_more": false,
  "list_data": [
    {
      "id": "11111111-2222-4333-8444-555555555555",
      "is_resource": false,
      "first_name": "Illustrative",
      "last_name": "Member",
      "display_name": "Illustrative Member",
      "workspace_role_id": 1,
      "workspace_role": "Admin"
    },
    {
      "id": "66666666-7777-4888-8999-000000000000",
      "is_resource": true,
      "first_name": "Illustrative Resource",
      "last_name": "",
      "display_name": "Illustrative Resource",
      "workspace_role_id": 4,
      "workspace_role": "Resource"
    }
  ]
}
```

**Check:** `display_name` follows your workspace's User Name Display Format Preference, First Last or Last, First. If more than one person matches, compare their email addresses before you keep the `id`. Treat the `id` as text.

## Step 2: Search by email

Find the person with one whole email address. For a Resource, this is the contact email recorded for them.

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users?filter_by_email=jane.smith%40example.com&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

**Check:** `jane.smith@example` doesn't match `jane.smith@example.com`, so send the whole address. No match returns an empty list.

## Step 3: List everyone with one role

Send `filter_by_workspace_role_id`: `1` Admin, `2` Team Member, `3` Guest or `4` Resource. This lists every Guest, sorted by display name.

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users?filter_by_workspace_role_id=3&%24result_sort=display_name_asc&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

Other filters you can add:

| To find | Send |
| --- | --- |
| Only Resources, or only users who can sign in | `filter_by_is_resource=true`, or `false` |
| People you already have IDs for | `filter_by_user_ids` with one ID or an array of IDs |
| Each user's permissions and content restrictions | `hydrate_permissions=true` |
| A different order | `$result_sort`: `display_name_asc`, `display_name_desc`, `id_asc` (the default) or `id_desc` |

**Check:** Filters work together, so a role and a name word find people who match both. While `has_more` is true, ask for the next page with the same filters and sort, and add 50 to `$offset`.

## Step 4: Pick someone who can be assigned Tasks

Search the users and Resources list by name and keep only people who can be assigned Tasks. This list returns every match at once, without pages.

```bash
curl -X GET "https://api.exhibitday.com/v1/references/users_and_resources?filter_by_name_contains_text=smith&filter_by_can_have_tasks_assigned=true" -H "Authorization: Bearer YOUR_API_KEY"
```

**Check:** Tasks can't be assigned to Resources, so `filter_by_can_have_tasks_assigned=true` leaves them out, along with users who can't be assigned Tasks. Use the `id` as a Task's Assignee, or in the Tasks list's `filter_by_assignee_user_id`.

## Step 5: Check open invitations

Before you invite someone, check whether they already have an open invitation.

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users/invitations?filter_by_email=jane.smith%40example.com&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

**Check:** A `status` of `pending` means the invitation hasn't been accepted yet. `accepted` means the person accepted but hasn't joined the workspace yet. Add `filter_by_status` to see only one of them. Invitations already used to join aren't listed.

## Step 6: See which Events someone is involved in

Use the person's `id` as `user_id`. This lists their upcoming Events, including Events in progress, for any kind of involvement.

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users/involvements?user_id=11111111-2222-4333-8444-555555555555&filter_by_event_date_category=upcoming&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

**Check:** Each Event appears once, with all of the person's `involvements`. To choose one kind, add `filter_by_involvement`: `creator`, `attendee`, `travel_tag`, `playbook_tag`, `misc_expense_tag`, `task_assignee` or `task_contributor`.

## Try it

## Before running the example

| Value | What to put in it |
| --- | --- |
| `YOUR_API_KEY` | Your workspace API key. Keep it out of shared code and logs. |
| `filter_by_name_contains_text` | The name of someone in your workspace. The example uses `Jane Smith`. |
| `$limit` and `$offset` | The example reads up to 50 matches starting at offset 0. |

**Note.** This example only reads data. It searches for people named Jane Smith.

Copy the complete example in your language and run it. To try another search, change the request to match one of the steps above.

## Complete example program

Code Samples

```bash
curl -X GET "https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0" -H "Authorization: Bearer YOUR_API_KEY"
```

```javascript
const response = await fetch("https://api.exhibitday.com/v1/workspace_settings/users?" + new URLSearchParams({ "filter_by_name_contains_text": "Jane Smith", "$result_sort": "display_name_asc", "$limit": "50", "$offset": "0" }), {
  method: "GET",
  headers: { "Authorization": "Bearer YOUR_API_KEY" }
});
const data = await response.json();
console.log(response.status, data);
```

```python
import requests

response = requests.get(
    "https://api.exhibitday.com/v1/workspace_settings/users",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    params={"filter_by_name_contains_text": "Jane Smith", "$result_sort": "display_name_asc", "$limit": "50", "$offset": "0"},
)
print(response.status_code, response.json())
```

```csharp
using System;
using System.Net.Http;
using System.Net.Http.Headers;

using var client = new HttpClient();
client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", "YOUR_API_KEY");
var response = await client.GetAsync("https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0");
Console.WriteLine($"{(int)response.StatusCode} {await response.Content.ReadAsStringAsync()}");
```

```java
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

public class ExhibitDayExample {
    public static void main(String[] args) throws Exception {
        HttpClient client = HttpClient.newHttpClient();
        HttpRequest request = HttpRequest.newBuilder()
            .uri(URI.create("https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0"))
            .header("Authorization", "Bearer YOUR_API_KEY")
            .method("GET", HttpRequest.BodyPublishers.noBody())
            .build();
        HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());
        System.out.println(response.statusCode() + " " + response.body());
    }
}
```

```php
<?php
$curl = curl_init('https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0');
curl_setopt_array($curl, [
    CURLOPT_CUSTOMREQUEST => 'GET',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ['Authorization: Bearer YOUR_API_KEY'],
]);
$response = curl_exec($curl);
if ($response === false) {
    throw new RuntimeException(curl_error($curl));
}
echo curl_getinfo($curl, CURLINFO_HTTP_CODE) . PHP_EOL . $response;
curl_close($curl);
```

```ruby
require 'net/http'
require 'uri'

uri = URI('https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0')
request = Net::HTTP::Get.new(uri)
request['Authorization'] = 'Bearer YOUR_API_KEY'
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: uri.scheme == 'https') do |http|
  http.request(request)
end
puts "#{response.code} #{response.body}"
```

```go
package main

import (
    "fmt"
    "io"
    "log"
    "net/http"
)

func main() {
    request, err := http.NewRequest("GET", "https://api.exhibitday.com/v1/workspace_settings/users?filter_by_name_contains_text=Jane%20Smith&%24result_sort=display_name_asc&%24limit=50&%24offset=0", nil)
    if err != nil { log.Fatal(err) }
    request.Header.Set("Authorization", "Bearer YOUR_API_KEY")
    response, err := (&http.Client{}).Do(request)
    if err != nil { log.Fatal(err) }
    defer response.Body.Close()
    body, err := io.ReadAll(response.Body)
    if err != nil { log.Fatal(err) }
    fmt.Printf("%d %s\n", response.StatusCode, body)
}
```

## Example response

Response 200 — OK 304 — Not Modified 400 — Bad Request 401 — Unauthorized 429 — Too Many Requests 500 — Internal Server Error

Example Successful request

```json
{
  "records_found": 2,
  "total_records": 2,
  "has_more": false,
  "list_type": "workspace_member",
  "list_data": [
    {
      "id": "11111111-2222-4333-8444-555555555555",
      "is_resource": false,
      "first_name": "Illustrative",
      "last_name": "Member",
      "display_name": "Illustrative Member",
      "email": "member@example.invalid",
      "organization": null,
      "title": null,
      "phone_number": null,
      "profile_photo_url": "https://www.exhibitday.com/Images/Generic-User-Icon.png",
      "workspace_role_id": 1,
      "workspace_role": "Admin",
      "workspace_member_joined_timestamp": null,
      "permissions": null
    },
    {
      "id": "66666666-7777-4888-8999-000000000000",
      "is_resource": true,
      "first_name": "Illustrative Resource",
      "last_name": "",
      "display_name": "Illustrative Resource",
      "email": "resource@example.invalid",
      "organization": "Illustrative supplier",
      "title": "Display equipment",
      "phone_number": "+1 202-555-0146",
      "profile_photo_url": "https://www.exhibitday.com/Images/Associate-Profile-5.png",
      "workspace_role_id": 4,
      "workspace_role": "Resource",
      "workspace_member_joined_timestamp": "2026-01-02T13:00:00Z",
      "permissions": null
    }
  ]
}
```

Note: GET /v1/workspace_settings/users - HTTP 200. The users and Resources whose first or last names contain both Jane and Smith, sorted by display name. Keep the returned id to use in later requests.

Note: There is no response body. Keep using your cached response.

```json
{
  "status_code": 400,
  "status": "Bad Request",
  "message": "HTTP method override is not supported.",
  "error_code": "invalid_request",
  "errors": [
    "Send the documented HTTP method directly. X-HTTP-Method-Override cannot change a request's HTTP method."
  ],
  "error_params": [
    "X-HTTP-Method-Override"
  ],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

```json
{
  "status_code": 401,
  "status": "Unauthorized",
  "message": "No API key was provided. Send your key in the Authorization header as 'Bearer YOUR_API_KEY'. Alternatively, you can use the api_key parameter.",
  "error_code": "missing_api_key",
  "errors": [
    "Copy the key from Workspace Settings > API & Integrations > API Access in ExhibitDay."
  ],
  "error_params": [
    "api_key"
  ],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

```json
{
  "status_code": 401,
  "status": "Unauthorized",
  "message": "The API key is not valid. Check that you copied the whole key from Workspace Settings > API & Integrations > API Access, then send it in the Authorization header as 'Bearer YOUR_API_KEY'. Alternatively, you can use the api_key parameter.",
  "error_code": "invalid_api_key",
  "errors": [
    "Check that you sent the whole key. If it was regenerated, use the current key from Workspace Settings > API & Integrations > API Access."
  ],
  "error_params": [
    "api_key"
  ],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

```json
{
  "status_code": 401,
  "status": "Unauthorized",
  "message": "Access to the ExhibitDay API is not enabled for your workspace. Please contact support@exhibitday.com to enable API Access. Once access is enabled, send your key in the Authorization header as 'Bearer YOUR_API_KEY'.",
  "error_code": "api_access_disabled",
  "errors": [
    "Nothing was read or changed."
  ],
  "error_params": [
    "api_key"
  ],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

```json
{
  "status_code": 429,
  "status": "Too Many Requests",
  "message": "Error 429 - Too Many Requests",
  "error_code": "rate_limited",
  "errors": [
    "Error 429 - Too Many Requests"
  ],
  "error_params": [],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

```json
{
  "status_code": 500,
  "status": "Unexpected Internal Error",
  "message": "An unexpected error occurred. Please try again later.",
  "error_code": "internal_error",
  "errors": [
    "An unexpected error occurred. Please try again later."
  ],
  "error_params": [],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

Note: Use the request_id from your own response when contacting support.

```json
{
  "status_code": 500,
  "status": "Unexpected Internal Error",
  "message": "An unexpected error occurred. Please try again later.",
  "error_code": "internal_error",
  "errors": [
    "Check whether your change was saved before trying again."
  ],
  "error_params": [],
  "request_id": "0123456789abcdef0123456789abcdef"
}
```

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

- Invitations and inactive or deactivated users aren't in the users list. Use the invitations list for people who haven't joined yet.
- A person's name can change and two people can share a name. Save the `id`, not the name.
- `GET /v1/workspace_settings/users/info` returns one person's full details, including Admin Notes.

## Related guides

- [Search Tasks by Name, Details, Assignee and Due Date](https://api.exhibitday.com/Help/V1?guide=search-tasks)
- [Create Tasks from Forms, Tickets or Other Apps](https://api.exhibitday.com/Help/V1?guide=create-tasks)
- [Get a Complete List of Attendees, Travel and More](https://api.exhibitday.com/Help/V1?guide=find-filter-page)
- [Search Workspace Logs to See Who Changed What, and When](https://api.exhibitday.com/Help/V1?guide=workspace-activity)
