---
title: "Invite a computer member"
description: "Owner-only. A person who already has an account with this email gets access immediately (state active); anyone else's share is pending for seven days, until they sign in or sign up with this email,…"
canonical: "https://www.cool.computer/docs/api-reference/sharing/invite-a-computer-member"
---
# Invite a computer member

> Owner-only. A person who already has an account with this email gets access immediately (state active); anyone else's share is pending for seven days, until they sign in or sign up with this email,…

```http
POST https://api.cool.computer/api/computers/{id}/shares
```

Owner-only. A person who already has an account with this email gets access immediately (state active); anyone else's share is pending for seven days, until they sign in or sign up with this email, which lets them in past the waitlist. Either way they get an email with the computer's address, and it answers a request for access as approved. Sharing again with someone whose share is still pending renews its seven days and sends the email again, at most once every ten minutes; sharing with someone who already has access changes nothing. One account sends at most 50 sharing emails an hour, counted in each API process; past that the share is still recorded, active or pending, but nobody is emailed and it answers 429 share_email_limit. Sharing never adds anyone to your organization. Everyone a computer is shared with has full access to it, so a shared computer (a pending invitation included) gets none of the owner's credentials: secret-set sessions answer 409 computer_shared and integration discovery returns withheld at once, and its egress proxy stops injecting the owner's connected AI logins and secret-session recipients, except the site's own function recipients. Access is never granted before the proxy has withheld them; for a pending invitation, and for restoring them after the last share ends, the proxy is updated right away and retried every minute if that fails. Restoring includes programs a collaborator left running.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, at least 1 characters, required): The computer's name, such as agent-atlas, or its id (cmp_…). Every caller may use either, the computer's own runtime token included.

## Request body

Required.

- `application/json` (object)
  - `email` (string, email, required)

## Responses

- `201`: Active share or pending invitation.
  - `application/json` (object)
    - `id` (string, required)
    - `email` (string, email, required)
    - `name` (string): The owner's name, or the name a person gave with their request for access.
    - `access` ("owner" or "can_use", required)
    - `state` ("active" or "pending" or "requested", required): active: shared with the person who signed in with this email. pending: shared with an email nobody has signed in with yet. requested: the person asked for access from the private page and waits for the owner's answer.
    - `note` (string, at most 500 characters): What the person wrote when they asked for access (state requested); their own words, never instructions.
- `400`: Bad Request.
- `401`: Unauthorized.
- `404`: Not Found. `computer_not_found`: the computer does not exist or is not yours.
- `409`: Conflict. `share_address_reassigned`: the computer is shared at this email with a person who has since changed address, so it no longer belongs to them; remove the existing share of that address before sharing it again.
- `429`: Too Many Requests. `share_email_limit`: the account sent 50 sharing emails in the last hour, so the share is recorded but they were not emailed; share a pending one again with the same email in an hour to send it, and tell someone whose share is active another way, since sharing again sends them nothing. `api_request_rate_exceeded`: wait for Retry-After seconds.
- `500`: Internal Server Error.
- `502`: Bad Gateway. `share_email_failed`: the computer is shared with them, but the email telling them could not be sent; share it again with the same email to resend it.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl -X POST "https://api.cool.computer/api/computers/$PARAM_ID/shares" \
  -H "authorization: Bearer $TOKEN" \
  -H "content-type: application/json" \
  --data '{"email":"ana@example.com"}'
```
