Skip to content

Replace audience members โ€‹

PUT /v1/admin/email/audiences/{id}/members

  • Operation ID: setEmailAudienceMembers
  • Tags: Email audiences
  • Base URL: http://localhost:8787

Replaces the member list with either members (emails and/or user ids) or a pasted csv (first column; optional email header). Duplicates are removed case-insensitively; at most 50,000 members. Invalid CSV rows return 400 validation_failed with invalid_emails and invalid_count in details.

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission email.write.

Authentication โ€‹

  • Auth: staff Bearer JWT (Authorization: Bearer <access_token>) with the permissions below.
  • Required permissions: email.write

Parameters โ€‹

NameInTypeRequiredDescription
idpathstring<uuid>yes-

Request body โ€‹

Required: yes.

Content type: application/json

Schema: object | object

FieldTypeRequiredDescription
(variant 1).members(string<email> | object | object)[]yesMax items: 50000
(variant 1).members[] (variant 2).user_idstring<uuid>yes-
(variant 1).members[] (variant 2).emailstring<email>noMax length: 320
(variant 1).members[] (variant 3).emailstring<email>yesMax length: 320
(variant 2).csvstringyesMax length: 5000000

Responses โ€‹

200 โ€‹

Members stored.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object

FieldTypeRequiredDescription
countintegeryes-

Errors โ€‹

400 โ€‹

Request validation failed. validation_failed: CSV contains invalid email addresses.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ValidationErrorBody) | object (ErrorBody)

FieldTypeRequiredDescription
(variant 1).successbooleanyesOne of: false
(variant 1).errorobjectyes-
(variant 1).error.namestringyesOne of: "ZodError"
(variant 1).error.issuesobject[]yes-
(variant 1).error.issues[].codestringyes-
(variant 1).error.issues[].path(string | number)[]yes-
(variant 1).error.issues[].messagestringyes-
(variant 2).errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
(variant 2).detailsanynoOptional structured context. For 403 it is { perm }.

Request validation

json
{
  "success": false,
  "error": {
    "name": "ZodError",
    "issues": [
      {
        "code": "custom",
        "path": [
          "field"
        ],
        "message": "Invalid value"
      }
    ]
  }
}

Application error

json
{
  "error": "validation_failed"
}

401 โ€‹

Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

FieldTypeRequiredDescription
errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
detailsanynoOptional structured context. For 403 it is { perm }.

Error response

json
{
  "error": "missing_token"
}

403 โ€‹

Authenticated but lacking the required permission. details.perm lists the accepted permission keys.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "forbidden",
  "details": {
    "perm": "email.write"
  }
}

404 โ€‹

audience: no such audience.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "audience"
}

422 โ€‹

too_many_members (details { max }) or invalid_state.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "too_many_members"
}

500 โ€‹

Unexpected server error (internal). No details are returned.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "internal"
}

Examples โ€‹

curl โ€‹

bash
curl -X PUT 'http://localhost:8787/v1/admin/email/audiences/3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90/members' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"members":["player@example.com"]}'

TypeScript โ€‹

ts
const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow

const response = await fetch("http://localhost:8787/v1/admin/email/audiences/3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90/members", {
  method: "PUT",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "members": [
      "player@example.com"
    ]
  }),
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();

Try this endpoint

Requests go directly from your browser to the API. Send request executes this endpoint against the selected server.

PUT/v1/admin/email/audiences/{id}/members

Your token stays in this tab's memory and is sent only when you press Send request.

Parameters
Request body (required)

Built for developers. Ready for agents.