Create a bulk post

Creates a single post campaign and fans it out to every location in locationIds, publishing to the selected postSites. Unlike the per-location create, one call targets your whole fleet, which is the efficient way to run a company-wide announcement, offer, or event.

Request shape. The entire body must be wrapped in an input object, every field (postName, locationIds, postType, …) is a property of input. A flat, unwrapped body is rejected with an HTTP 400 (Variable "$input" of required type ... was not provided). This is the same contract as POST /posts; the two endpoints share the underlying mutation, which is why a successful response is keyed under createSocialPost rather than a bulk-specific key.

Use case: company-wide announcement (shown above). Set postType: "ANNOUNCEMENT", list the location IDs, and provide one postMessage per site. Add postScheduledDates to run the post over a fixed window (the post is then created with status SCHEDULED); omit it to publish immediately.

Use case: a limited-time offer across all stores. Switch postType to OFFER and supply the coupon in postContextInfo (still wrapped in input):

{  "input": {    "postName": "Summer 20% Off",    "locationIds": ["TG9jYXRpb246MTgwMDI4OQ=="],    "postType": "OFFER",    "postSites": ["GOOGLE"],    "postMessage": [{ "site": "GOOGLE", "message": "20% off through July!" }],    "postContextInfo": {      "title": "Summer Sale",      "couponCode": "SUMMER20",      "redeemUrl": "https://example.com/offer",      "termsConditions": "Valid through July 31",      "startDay": "2026-07-10",      "startTime": "09:00",      "endDay": "2026-07-31",      "endTime": "23:59"    }  }}

Gotchas.

• The body must be wrapped in input; sending the fields at the top level returns an HTTP 400.
• postType, postSites, postName, and locationIds are required; EVENT, OFFER, and PRODUCT types additionally require the matching postContextInfo (or products) fields.
• postSites accepts only GOOGLE and FACEBOOK; the target locations must have the corresponding channel connected or that site is skipped.
• The response returns HTTP 200 with success: false and a populated errors array on partial or full validation failure, check success, then track live delivery per location with the fetch bulk post endpoint.