Release Notes

Community posting via the Social Planner Public API

You can now schedule and publish Community posts through the Social Planner Public API, including choosing which Community member the post is published as. Marketplace apps and custom integrations can bring Community publishing into their own workflows, and Community posting moves closer to API parity with other social channels.

What's new

  • List Community members: retrieve eligible members who can publish posts, search members by name, and paginate through the list. Only active, permitted members are returned, and private Communities return only members of that specific group.

  • Validate member eligibility: before scheduling a post, check whether a selected member is still active and authorized to publish in the Community.

  • Publish as a specific member: when creating a Community post through the API, specify which eligible member the post should be published as.

  • Publish-time verification: Social Planner performs a final eligibility check before publishing. If the selected member has left the Community or lost permission, the post fails with a clear error instead of publishing under the wrong identity.

How it works

  1. Connect a Community group in Marketing → Social Planner → Settings → Social Accounts.

  2. Use Get Accounts to retrieve the Community account ID.

  3. Use Get Community Members to retrieve eligible members.

  4. Select the member you want to publish as.

  5. Create the post using the Community post API, and optionally validate the member before scheduling.

  6. Social Planner verifies the member again before publishing.

Good to know

  • Connecting and managing Community accounts stays available in the app, so no UI changes are needed to use the feature.

  • The Public API supports member listing, member validation, scheduling, and publishing.

  • Draft posts don't require a publish-as member selection.

  • Member eligibility is checked when posts are scheduled and again when they are published, so the selected member must remain active and permitted in the Community at publish time.

  • API access requires the appropriate Social Planner scopes.