Skip to main content
PATCH
/
api
/
v1
/
teams
/
members
/
cap
Set a team member's spending cap
curl --request PATCH \
  --url https://neo.api.projectdiscovery.io/api/v1/teams/members/cap \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "jsmith@example.com",
  "spending_cap_usd": 1
}
'
{
  "member": {
    "email": "jsmith@example.com",
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "invited_at": "2023-11-07T05:31:56Z",
    "accepted_at": "2023-11-07T05:31:56Z",
    "billable": true,
    "cap": {
      "limit": 123,
      "remaining": 123,
      "used": 123
    },
    "created_at": "2023-11-07T05:31:56Z",
    "invited_by": "jsmith@example.com",
    "updated_at": "2023-11-07T05:31:56Z"
  }
}

Authorizations

Authorization
string
header
required

JWT authentication token

Body

application/json
email
string<email>
required
spending_cap_usd
number<float> | null
required

Absolute USD cap (>= 0); 0 blocks the user. Required — a null or omitted value is rejected (400). To clear a cap, use DELETE.

Required range: x >= 0

Response

Spending cap updated

member
object
required