Skip to content
Open Markdown

Schedule a campaign ​

POST /v1/admin/email/campaigns/{id}/schedule

  • Operation ID: scheduleEmailCampaign
  • Tags: Email campaigns
  • Base URL: http://localhost:8787

Schedules sending at a future time. Publishes a dashboard progress event.

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission email.send.

Authentication ​

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

Parameters ​

NameInTypeRequiredDescription
idpathstring<uuid>yes-

Request body ​

Required: yes.

Content type: application/json

Schema: object

FieldTypeRequiredDescription
scheduled_atstring<date-time>yes-

Responses ​

204 ​

Campaign scheduled.

  • Header x-request-id: Request identifier; quote it when reporting an error. No response body.

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.send"
  }
}

404 ​

campaign: no such campaign.

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

422 ​

scheduled_at_in_past 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": "scheduled_at_in_past"
}

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 POST 'http://localhost:8787/v1/admin/email/campaigns/3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90/schedule' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"scheduled_at":"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/campaigns/3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90/schedule", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "scheduled_at": "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.

POST/v1/admin/email/campaigns/{id}/schedule

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.