Create Multi-Image Posts via API

Integrators can now publish posts containing multiple images in a single API call to the Create Content endpoint (POST /content). Previously, the public API only supported single-image posts, requiring workarounds for multi-image content. This update enables richer, more visually engaging posts, particularly for programs that automate content distribution via the Hearsay API.

Key behavior:

• Supports up to 10 image URLs per post.
• Value must be an array of strings containing valid image URLs.
• Duplicate URLs are automatically deduplicated before the content is created; the first occurrence is preserved.
• Instagram content requires at least one image in picture_urls.
• If more than 10 unique image URLs are provided, the API returns a 400 error with error_code: "too_many_photos".

To publish multi-image posts, do the following:

1. Review the updated API documentation: docs.hearsaysocial.com/reference/create-content
2. Update your API request payload to include picture_urls as an array of up to 10 valid image URLs.
3. Ensure your error handling accounts for the "too_many_photos" error code (HTTP 400) if the image count could exceed 10.

Example request body:

{
  "author_id": 24542,
  "messages": ["Text post with multiple images"],
  "social_networks": ["facebook", "linkedin"],
  "modification_rule": "optional",
  "picture_urls": [
    "https://example.com/images/product-1.png",
    "https://example.com/images/product-2.png",
    "https://example.com/images/product-3.png"
  ]
}

The same constraints (supported file formats, max file size, resolution limits) apply to images uploaded via the API as to those uploaded in-app.

No configuration changes are required. Integrators already using the Create Content endpoint can immediately begin passing picture_urls with multiple URLs.

More Granular Control Over Respond Tab Capabilities 

Organizations can now allow users to delete their own published posts on the Respond tab without allowing them to engage via likes or comments. This provides more precise control over what actions users can take on the Respond tab, enabling organizations to match the product experience to their compliance and governance policies.

This feature is configurable via an admin setting. To configure it in the Administration view:

1. In the sidebar, click Settings. 
2. On the Organizational Settings page, click the Content & Email tab. 

3. Configure the Allow users to like and comment on published posts setting. 

   1. Enabled (default): Users can like, comment, and delete posts on the Respond page. 
   2. Disabled: Users can only delete posts on the Respond page. 

Respond tab with setting Enabled (Like and Comment visible)

Respond tab — Published Posts view with setting Disabled (Like and Comment hidden, Delete still available)