GET /api/v1/series/{seriesId}
Reads one series. Answers 400 when the id belongs to an enrollment sequence rather than a
series — a null start date and an empty audience would have looked like a badly configured series
instead of the wrong kind of object.
Authorization
| Role | Access |
|---|---|
OWNER | Allowed |
ADMIN | Allowed |
MEMBER | Allowed |
Path parameters
| Parameter | Type | Description |
|---|---|---|
seriesId | string (uuid) | The series id — also its sequence id |
Example
bash
curl -s 'https://www.agentsmail.io/api/v1/series/7d7d7d7d-8888-4ccc-9ddd-eeee00001111' \
-H "x-api-key: $AGENTMAIL_API_KEY"Response
| Code | When |
|---|---|
200 | The series |
400 | This id is a sequence, not a series |
401 | Missing or invalid key |
404 | No series with this id in your organization |
Response fields
Same shape as list series, for the single object indata.
Example response
json
{
"success": true,
"data": {
"id": "7d7d7d7d-8888-4ccc-9ddd-eeee00001111",
"name": "March launch",
"status": "active",
"startsAt": "2026-03-15T08:00:00.000Z",
"listId": "9f8e7d6c-1111-4bbb-8ccc-ddddeeeeffff",
"audienceSegmentId": null,
"audienceTagId": null,
"topicId": null,
"createdAt": "2026-03-01T10:00:00.000Z",
"updatedAt": "2026-03-02T10:00:00.000Z"
}
}Notes
The steps are not in this response. Read them withGET /api/v1/sequences/{seriesId}/versions/{versionId}/nodes — each sending step carries its
sendTimeMinutes, and each wait its waitHours.