Your account and team

• A team is the workspace that owns your hubs, media, and API keys. Signing up creates one for you, and you can belong to more than one. See Tenancy.
• The team owner is the user who created the team. Only the owner can rename it.
• The active team is the team the admin is working in right now. Every admin page shows the active team’s data.

export MIO_BASE_URL="https://api.member.dev"
export MIO_ACCESS_TOKEN="<platform access token>"

export USER_ID=$(
  curl -s "$MIO_BASE_URL/api/v1/auth/me" \
    -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
    -H "Accept: application/vnd.api+json" | jq -r '.data.id'
)

​

The Account area

​

Team

• Your own row shows your name and email, marked You, with your role (Owner or Member). Select it to open the role and the Joined date.
• Other members are not named yet, because the admin cannot read other people’s profiles. They are counted in one row, for example “2 other members”, with “Names appear once available.”
• You cannot invite people, change roles, or remove members here. See Not yet for adding a member with the API.

​

Profile & security

​

Payment accounts

​

Developer tools

• API keys are the first group. Create key is in the page header. Creating, copying, changing, and revoking keys works as described in Manage API keys in the admin.
• Webhooks lists the team’s endpoints by host, with a Disabled badge where one is off. Add endpoint asks for a name, an endpoint URL, and the hub whose events it receives, then shows the signing secret once. Each row’s menu has Delete. With no hub yet, the group says “Create a hub first, then send its events to another app.”
• Under Advanced:
  • External login (“Sign in with Google, Facebook or a company login.”) lists providers, each with an on/off switch and an Edit or Remove menu, and Add provider. See Configure an external-login provider.
  • Verified domains (“Email domains that use the company login.”) lists domains. For one still waiting on DNS, it shows the TXT record to add, a copy button, and Verify now. Add domain asks for a domain and a hub. See Verified-Domain SSO.
  • OAuth clients (“Let other apps sign people in with Mio.”) lists clients with a copy button for the client ID, a Delete menu, and New client.

​

Billing

​

Edit your profile with the API

curl -s -X PATCH "$MIO_BASE_URL/api/v1/users/$USER_ID" \
  -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
  -H "Content-Type: application/vnd.api+json" \
  -H "Accept: application/vnd.api+json" \
  -d '{
    "first_name": "Sam",
    "last_name": "Rivera"
  }' | jq '.data.attributes | {first_name, last_name, email}'

• You can only update yourself. Any other user id returns 404. There is no PATCH /api/v1/users/me shortcut, so use your id from GET /api/v1/auth/me.
• Send only the fields you want to change. A field you leave out keeps its value. null clears that name, and the response is 200 with the name set to null. An empty string ("") sets the name to an empty string.
• There is no field for your email address, so the API cannot change it either.

​

Rename a team with the API

curl -s "$MIO_BASE_URL/api/v1/teams" \
  -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
  -H "Accept: application/vnd.api+json" \
  | jq -r --arg me "$USER_ID" '.data[] | "\(.id)  \(.attributes.name)  owner: \(.attributes.owner_id == $me)"'

export TEAM_ID="<team id from the list>"

curl -s -X PATCH "$MIO_BASE_URL/api/v1/teams/$TEAM_ID" \
  -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
  -H "Content-Type: application/vnd.api+json" \
  -H "Accept: application/vnd.api+json" \
  -d '{
    "data": {
      "type": "teams",
      "attributes": {
        "name": "Member Academy Team"
      }
    }
  }' | jq '.data | {id, name: .attributes.name, slug: .attributes.slug}'

​

Change your password with the API

CHANGE_RESPONSE=$(
  curl -sS -f -X POST "$MIO_BASE_URL/api/v1/auth/me/password/change" \
    -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
    -H "Content-Type: application/vnd.api+json" \
    -H "Accept: application/vnd.api+json" \
    -d '{"current_password":"example-password","new_password":"a-new-password"}'
)
export MIO_ACCESS_TOKEN="$(printf '%s' "$CHANGE_RESPONSE" | jq -r '.access_token')"
export MIO_REFRESH_TOKEN="$(printf '%s' "$CHANGE_RESPONSE" | jq -r '.refresh_token')"

​

Switch teams

curl -s -X POST "$MIO_BASE_URL/api/v1/teams/$TEAM_ID/switch" \
  -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
  -H "Accept: application/vnd.api+json" \
  | jq '.data | {id, name: .attributes.name}'

​

The active team in API calls

curl -s "$MIO_BASE_URL/api/v1/users" \
  -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
  -H "X-Team-ID: $TEAM_ID" \
  -H "Accept: application/vnd.api+json" \
  | jq -r '.data[] | "\(.attributes.first_name) \(.attributes.last_name)"'

​

Not yet

• Inviting team members by email (MIO-3900). The admin lists the team’s people read only and has no invites. With the API, the team owner can add someone who already has an account, by their user id. They can find their id in data.id of GET /api/v1/auth/me.
  curl -s -X POST "$MIO_BASE_URL/api/v1/teams/$TEAM_ID/members" \
    -H "Authorization: Bearer $MIO_ACCESS_TOKEN" \
    -H "Content-Type: application/vnd.api+json" \
    -H "Accept: application/vnd.api+json" \
    -d '{
      "data": {
        "type": "team_members",
        "attributes": {
          "user_id": "<their user id>"
        }
      }
    }'
  
  Success is 201. Someone who is already a member returns 409, and anyone but the owner gets 403. A team API key can add a member too, but not give them a role: a key request that sets role_id returns 403, so assigning a role needs the owner’s signed-in session. The new member can switch to the team, but only the owner can rename it or manage its API keys. See Add Member. Letting a member read the contact directory. The owner can give a member a reduced, read-only view of the team’s contacts with the contacts.read team permission. With the owner’s signed-in session (team API keys get 403 on these routes):
  1. Create a role for the team: POST /api/v1/roles with team_id set to your team.
  2. Attach the permission: POST /api/v1/roles/{role_id}/permissions with {"slug": "contacts.read"}. A team role accepts only team-scoped permissions; anything else, such as users.read, returns 422 with code permission_not_team_scoped.
  3. Give the member the role: PATCH /api/v1/teams/{team_id}/members/{user_id} with {"data": {"type": "team_members", "attributes": {"role_id": "<role id>"}}}. Send "role_id": null to take it away.
  The member can then call GET /api/v1/teams/{team_id}/contact-directory, which lists the team’s live contacts with six fields only: contact_id, first_name, last_name, email, source and created_at. It never includes deleted contacts, and it supports filter[email], filter[source], sort and cursor pagination. Access is checked against the member’s current role on every request, so removing the permission, the role or the membership takes effect straight away. The owner can call it too; the full contact routes stay owner-only. Who can change the team’s media. Media follows the same team roles. Any team member can read the media library. Editing needs the team owner, or a member whose team role holds the media.edit permission, which you attach exactly like contacts.read above. Editing covers uploading, renaming and updating files, folders and playlists, attaching and detaching, transcripts, transcoding, and publishing to or unpublishing from hubs. Deleting files, folders and playlists, and replacing a file’s media, stay with the team owner. A member without media.edit gets 403 on an edit, and a member with it gets 403 on a delete. A full-scope team API key keeps full media access, deletes included, so the mio CLI’s media commands keep working. Hub owners and admins signed in to a hub keep their current editor access, and the MCP media tools stay owner-only. When this shipped, every existing member without a role was given a team role named “Media editor” that holds media.edit, so nobody lost editing. A member whose role is a platform system role keeps that role and can read the team’s media but not change it. A member holds one role, so giving them a team role replaces their platform role.
• Profile pictures. You cannot upload an avatar, in the admin or with the API. The admin shows your initials.
• Deleting a team. The admin has no button for it. The API has DELETE /api/v1/teams/{team_id}, for the owner with a signed-in session only (team API keys get 403). It refuses with 409 while the team still has hubs, contacts, or API keys, and the error’s meta counts them. See Delete Team.

​

Next steps

• Tenancy: how teams and hubs scope your data.
• Authentication: when to use a platform JWT, a contact JWT, or a team API key.
• API keys: create a team API key for your integration or the CLI.
• Sign in as a creator: the platform sign-in flow for your own tools.