Repository navigation
feat: schedule list gives the account's sending schedules with their windows - #30
Merged
Merged
Conversation
…windows One GET /v3/schedules, which Reply answers in full with no paging. Each schedule carries its Windows time zone identifier as Reply holds it, its flags under the CLI's names, its windows by weekday (the weekday in lower case, each time of day as HH:MM) and Reply's own word for how it is used. A schedule without a usable id is reply.unavailable; a refusal is the house refusal, so a plan or role without the scheduler is access.feature_unavailable.
The only thing that refuses the read is Reply's sequences read scope, so the help, the README and the tests now say so and fake the refusal Reply sends: a problem+json insufficient_scope body with no code. The help names the six reply_status words, says is_default is the caller's own default and that main_timings holds one entry for each day Reply holds.
ArtemKosolap
enabled auto-merge
October 25, 2026 01:46
vigubikReply
approved these changes
Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
A new work command,
reply schedule list, lists every sending schedule the account can use:GET /v3/schedules. Reply answers it in full with no paging, so the command makes exactly one call andkeeps Reply's order.
time_zone_idis the Windows time zone identifier Reply holds (Eastern Standard Time), passed through unchanged.main_timings/follow_up_timingshold one entry for each day Reply holds, in Reply's order; an entry that is nota day at all is left out. Each day carries
week_dayin lower case (Reply names days as .NET does,Monday),active, andrangeswith each time of day writtenHH:MMfrom Reply's{hour, minute}. A range may endat
24:00. A time that is not a time of day isnull, never a guess.useProspectTimezonebecomesuse_recipient_time_zone, and so on); aflag Reply does not give as
trueisfalse;is_defaultis the calling user's default. A blank name or timezone is
null.reply_statusis Reply's own word for how the schedule is used, the first that holds of its six:unknown,inCampaignTemplate,inCurrentUserSequence,inTeamMemberSequence,isDefaultForCurrentUser,isDefaultForTeamMember.follow_up_timingsisnullwhen Reply gives no list there.reply.unavailable; a 403, which thisendpoint answers only to a key without Reply's sequences read scope (a problem+json
insufficient_scopebody with nocode), isaccess.feature_unavailable; 401 isaccess.denied; 5xx or an answer that is not a list isreply.unavailable.--helpdocuments the result shape, the time zone, weekday, time and state formats, and the error codes. The README'stable and work-commands section list the command.
Why
An agent that plans or checks when a sequence will send needs the schedules the account has, their time zones and
their windows, in a stable shape. Today that takes
reply api /v3/schedulesand reading Reply's raw model; this gives itthe same first-class, documented
--jsoncontract asaccount list.How it was verified
npm run buildandnpm test: 58 files, 862 passed, 5 skipped (the skips existed before). The change adds 9 tests:schedules.test.ts(7): the full shape and the single request; an empty account; blank or missing names, timezones and state words; flags only
truewhen Reply saystrue; follow-up windows that are not a list; unreadabledays, ranges and times, including
24:00; a schedule without a usable id; and the refusals (Reply'sinsufficient_scope403, 401, 503, an object instead of a list).
commands.test.ts(1): the command takes no flags or arguments and its help states the formats, Reply's six statewords, and the scope refusal.
program.test.ts(1): through the whole program, a flag or an id exits 2 with no request, and Reply'sinsufficient_scope403 exits 1 with{"error":{"code":"access.feature_unavailable","status":403}}on stderr.dist/index.jswas run against a loopback HTTP server answering/v3/scheduleswith a recorded-shapebody. It printed the expected
itemsexactly (exit 0), the 403 envelope (exit 1), and exit 2 for--name xand foran extra argument. Nothing contacted Reply.
commitlintpasses over every commit.