Social

Save a Facebook Group as a manual content-calendar destination. Meta no longer permits apps to publish to Groups, so scheduled content is prepared for a person to copy and post.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.add_group \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example",
    "url": "https://example.com"
  }'

Over MCP the same operation is the tool social_add_group at https://app.chirply.io/api/mcp, same bearer token, same input.

Cancel a draft or scheduled social post before any remaining destinations publish. Public Page posts that already succeeded are not deleted.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.cancel \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool social_cancel at https://app.chirply.io/api/mcp, same bearer token, same input.

Use its own OpenRouter account to write a reviewable batch of social posts. This consumes paid AI tokens but does not save or publish anything.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.generate_bulk \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "example"
  }'

Over MCP the same operation is the tool social_generate_bulk at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one content-calendar post and every Page or Group delivery result.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.get_post \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool social_get_post at https://app.chirply.io/api/mcp, same bearer token, same input.

List the account's drafted, scheduled, published, failed, and manual-handoff social posts with the result for every destination.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.list_calendar \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "2026-09-17T15:00:00Z",
    "to": "2026-09-17T15:00:00Z"
  }'

Over MCP the same operation is the tool social_list_calendar at https://app.chirply.io/api/mcp, same bearer token, same input.

List every place this account can put a social post: connected Facebook Pages and Instagram Professional accounts that publish automatically, and saved Facebook Groups that require a manual handoff. Each destination reports its kind (page, instagram, group) and whether it can currently publish.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.list_destinations \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool social_list_destinations at https://app.chirply.io/api/mcp, same bearer token, same input.

Record that a person copied this scheduled content into its Facebook Group. This does not call Facebook or create a post itself.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.mark_group_posted \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "destination_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool social_mark_group_posted at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately creates REAL public posts on every selected Facebook Page and Instagram account. There is no undo on Facebook or Instagram. Group destinations become ready-to-copy manual handoffs and are not posted automatically.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.publish_now \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "",
    "link_url": "https://example.com"
  }'

Over MCP the same operation is the tool social_publish_now at https://app.chirply.io/api/mcp, same bearer token, same input.

Remove a saved Group from future destination pickers. Existing scheduled posts keep their destination snapshot.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.remove_group \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool social_remove_group at https://app.chirply.io/api/mcp, same bearer token, same input.

Retries every failed destination immediately, creating REAL public Facebook or Instagram posts where the retry succeeds. Destinations already published are not duplicated.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.retry \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool social_retry at https://app.chirply.io/api/mcp, same bearer token, same input.

Save 2–12 social posts as drafts, or schedule the series across the selected destinations. Scheduled posts create real public posts at their publishing times. Every post in a series shares one set of destinations and none of them carry an image, so an Instagram destination is rejected outright here — schedule Instagram posts one at a time with social.schedule.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.save_bulk \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      "example",
      "example"
    ]
  }'

Over MCP the same operation is the tool social_save_bulk at https://app.chirply.io/api/mcp, same bearer token, same input.

Save social content and its destinations without publishing or scheduling anything. Content is still validated against every selected network, so an Instagram destination without an image is rejected now rather than at publishing time. Facebook Groups remain manual handoffs.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.save_draft \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "message": ""
  }'

Over MCP the same operation is the tool social_save_draft at https://app.chirply.io/api/mcp, same bearer token, same input.

Schedule this content to publish to every selected Facebook Page and Instagram account at the specified time. Real public posts will be created automatically on the org's own connected Meta assets. Selected Groups become manual handoffs because Meta removed Group publishing from its API.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/social.schedule \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "scheduled_at": "2026-09-17T15:00:00Z"
  }'

Over MCP the same operation is the tool social_schedule at https://app.chirply.io/api/mcp, same bearer token, same input.