Set the ad schedule
Human-friendly schedule input: HH:MM windows, day shorthands (MON, WEEKDAYS, WEEKEND) and presets. The server expands them, splits windows that cross midnight, resolves the time zone and stores the result as adScheduleStructured.
Time zones: "local" means the searcher's own time zone on platforms that support it, and the account time zone elsewhere. An explicit IANA zone (Europe/Berlin) is converted into account-time hours before storing. Introspect the current token shows the account time zone per platform under scheduling.timezones.
Pass dry_run: true to get the expanded schedule and any warnings without changing the campaign. Changes reach the ad platforms on the next sync.
Errors
- 404 NOT_FOUND: no campaign with this id in the active Space.
- 400 INVALID_REQUEST: the body is not valid JSON.
- 400 with a schedule-specific error.code (for example AD_SCHEDULE_TOO_MANY_WINDOWS), or VALIDATION_ERROR with details.issues[].
Request
- Base URL: https://api.growomat.com
- URL: https://api.growomat.com/api/v1/campaigns/{id}/ad-schedule
- Auth: HTTP bearer
Path parameters
The campaign id.
Headers
The Space to work in, for example spc_8f3aK2. Omit it to use your personal Space. List your Spaces returns the ids. A Space that does not exist returns 404 SPACE_NOT_FOUND; one you are not a member of returns 403 NOT_A_MEMBER.
Request body
Response
OK. The result is in data. List responses also carry meta with nextCursor and total.
Changes
No recorded changes to this operation across all 2 revisions of this API.