> ## Documentation Index
> Fetch the complete documentation index at: https://direct-api.reap.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Team members

> Team members are the people on your Business Account. The API reads them so you can choose who holds a card.

Team members are the people on your Business Account team. The API reads
them; it can't invite or edit them, that's dashboard only. To give someone a
card, invite them in the dashboard first (see [Managing Your Team](https://support.reap.global/hc/en-us/articles/16170798649743-Managing-Your-Team) in the Help Center), then use their `userId` as
`cardholderId` on [Create card](/api-reference/cards/create-card.md).

> [!NOTE]
>
> Team members must be employees or contractors of your company. The Business
> Account is a corporate account, so cards can only be issued to people who
> work for the business.

## Key fields

| Key | Type | Notes |
| - | - | - |
| `userId` | string | The member's ID. Pass it as `cardholderId` when creating a card. |
| `name` | string | The member's full name. |
| `email` | string | The member's email. Match on it to link members to your own records. |
| `teamGroupName` | string | The member's group in the dashboard (read-only). |
| `inviteStatus` | string | Where the member is in the invite lifecycle (below). |

## `inviteStatus`

| Value | Meaning |
| - | - |
| `approved` | The member accepted their invite and is active. **Only `approved` members can hold cards.** |
| `invited` | Invited but hasn't accepted yet. |
| `unresolved` | The invite needs attention before the member is active. |
| `declined` | The member declined the invite. |

Anyone whose status isn't `approved` fails card creation with
`422 CARDHOLDER_NOT_FOUND`.

## Related endpoints

* [List team members](/api-reference/team-members/list-team-members.md)
* [Create card](/api-reference/cards/create-card.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.