Sign in
Ad Accounts

Schedule a budget increase

Pre-schedule a temporary budget increase (Black Friday, a launch, a sale) instead of editing the budget by hand on the day. Same target rule as the GET: exactly one of campaignId / adSetId.

Two Meta constraints worth knowing before you call it. timeStart / timeEnd must fall on a 15-minute boundary, and a campaign cannot mix ABSOLUTE and MULTIPLIER across its schedules; the second type is rejected with "Can't mix your budget scaling selection". Window rules (must sit inside the campaign's run dates, minimum lead time, no overlap) are Meta's and its message is forwarded verbatim.

post/v1/ads/high-demand-periods

Request body

accountIdstring required

Zernio SocialAccount id used to resolve the Meta token.

campaignIdstring

Platform campaign id. Exactly one of campaignId / adSetId.

adSetIdstring

Platform ad set id. Exactly one of campaignId / adSetId.

budgetValuenumber required

With ABSOLUTE, a budget in the ad account's currency in WHOLE units (50 = $50.00). With MULTIPLIER, a factor of the existing budget (2 = double it) and NOT a currency amount.

budgetValueType'ABSOLUTE' | 'MULTIPLIER' required
timeStartinteger required

Unix seconds, on a 15-minute boundary (:00, :15, :30, :45).

timeEndinteger required

Unix seconds, on a 15-minute boundary and after timeStart.

recurrenceType'ONE_TIME' | 'WEEKLY' | 'MONTHLY'
currencystring

Ad account currency, for the ABSOLUTE minor-unit conversion. Ignored for MULTIPLIER.

Response

Budget schedule created

objectIdstring

The campaign / ad set the schedule was attached to.

idstring

Meta budget schedule id.

Changes

Changed in 5 of the 56 revisions of this API.17

  • 2c04683ce6948See the full diff
    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 3e6ddf2a99ea2See the full diff
    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

  • 0dba7d004d754See the full diff
    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

  • e70ed06e71502See the full diff
    • ○

      added the non-success response with the status

      response-non-success-status-added

    • ○

      added the non-success response with the status

      response-non-success-status-added

  • 1e9a379eafca1See the full diff
    • ○

      endpoint added

      endpoint-added