Skip to content

Update an audience โ€‹

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

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

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

FieldTypeRequiredDescription
namestringyesMin length: 1. Max length: 200
kindstringyesOne of: "static", "dynamic"
filterobject | nullno-
filter.qstringnoMin length: 1. Max length: 200
filter.statusstringnoOne of: "active", "banned", "deleted"
filter.tierstringnoMin length: 1. Max length: 32
filter.rolestringnoMin length: 1. Max length: 48
filter.providerstringnoMin length: 1. Max length: 32
filter.has_subscriptionbooleanno-
filter.created_fromstring<date-time>no-
filter.created_tostring<date-time>no-
filter.last_seen_fromstring<date-time>no-
filter.last_seen_tostring<date-time>no-

Responses โ€‹

200 โ€‹

Audience updated.

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

Schema: object (EmailAudienceId)

FieldTypeRequiredDescription
idstring<uuid>yes-

Errors โ€‹

400 โ€‹

Request validation failed.

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

Schema: object (ValidationErrorBody)

FieldTypeRequiredDescription
successbooleanyesOne of: false
errorobjectyes-
error.namestringyesOne of: "ZodError"
error.issuesobject[]yes-
error.issues[].codestringyes-
error.issues[].path(string | number)[]yes-
error.issues[].messagestringyes-

Request validation

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

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 โ€‹

invalid_state: rejected by the database function.

  • 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": "invalid_state"
}

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' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"name":"example","kind":"static","filter":{"q":"example","status":"active","tier":"example","role":"example","provider":"example","has_subscription":false,"created_from":"2026-01-15T12:00:00.000Z","created_to":"2026-01-15T12:00:00.000Z","last_seen_from":"2026-01-15T12:00:00.000Z","last_seen_to":"2026-01-15T12:00:00.000Z"}}'

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", {
  method: "PUT",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "name": "example",
    "kind": "static",
    "filter": {
      "q": "example",
      "status": "active",
      "tier": "example",
      "role": "example",
      "provider": "example",
      "has_subscription": false,
      "created_from": "2026-01-15T12:00:00.000Z",
      "created_to": "2026-01-15T12:00:00.000Z",
      "last_seen_from": "2026-01-15T12:00:00.000Z",
      "last_seen_to": "2026-01-15T12:00:00.000Z"
    }
  }),
});
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}

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.