Practical guidance for content that moves through bundle.social: media requirements, account permissions, platform rules, bulk workflows, Google Business Profile fields, and failure handling.
Last updated: May 2026
Company page
Clear product context for builders
A successful API request does not guarantee every platform will accept the final post.
Your product should show users platform-specific media, caption, permission, and eligibility constraints before they publish.
bundle.social surfaces practical errors so customers know whether to fix content, permissions, media, account state, or timing.
11
Sections
6
Checks
4
FAQs
Publishing reality
These guidelines are for composers, bulk imports, media workflows, and support flows where platform-specific rules need to be visible before customers press publish.
bundle.social can help you send content to social platforms, but every platform still controls what it accepts. A request can be valid for bundle.social and still fail later because the destination account, media file, content field, profile state, or platform rule does not allow that exact post.
If your UI lets users select TikTok, Instagram, LinkedIn, YouTube, Facebook, X, Pinterest, Reddit, Google Business Profile, and other destinations in one composer, the UI still needs to explain that each destination has different media, caption, account, privacy, eligibility, and publishing rules.
Prepare media before sending it into a publishing workflow. Platforms can reject files because of codec, container, image format, dimensions, aspect ratio, file size, duration, bitrate, audio track, animated content, fetchability, or temporary processing issues. When possible, keep video exports boring and reliable: MP4, H.264, standard audio, sensible dimensions, and publicly reachable media URLs when using URL-based upload workflows.
A media URL that works in your browser is not always usable by a platform crawler or by bundle.social. Avoid URLs that expire quickly, require authentication, block crawlers, redirect through unusual chains, depend on cookies, or return HTML instead of the actual file. If the media is important, upload it through bundle.social first instead of hoping every platform can fetch it from a random storage URL.
Do not assume every platform accepts the same text. Length limits, URL handling, hashtags, mentions, titles, descriptions, privacy fields, branded content fields, and audience settings vary by destination. Your product should keep platform-specific fields visible instead of flattening everything into one caption box and acting surprised when a provider rejects the result.
Connected accounts still need the right permissions, account type, role, profile state, and platform approval for the requested action. A user may be able to connect an account but still be unable to publish a specific content type, access a specific metric, edit a specific Google Business Profile field, or use a feature that requires business verification or platform review.
Bulk workflows are powerful, but they should not become invisible automation. Before submitting large CSV imports or campaign batches, show users which rows target which teams, which platforms are selected, what media will be used, and which rows already look invalid. One bad row should be fixable without turning the entire campaign into a mystery failure.
Google Business Profile workflows can include posts, reviews, hours, menus, services, attributes, media, and location fields. Many of those fields are location-specific, category-dependent, country-dependent, or controlled by verification state. Your UI should check eligibility before showing editable fields and explain why a field may be unavailable for one location but valid for another.
Customers are responsible for the content they send through the API. That includes rights to images, videos, music, logos, user-generated content, personal data, claims, offers, promotions, and regulated content. bundle.social moves content through platform APIs; it does not grant rights to use assets or override the rules of the destination platforms.
Do not show users a dead-end message like 'post failed' when the platform response tells them what to fix. Good error handling should explain whether the issue is media format, media fetchability, account permissions, unsupported destination fields, platform processing, rate limits, provider downtime, or content policy. The more specific the error, the fewer support tickets you will create for yourself.
bundle.social can validate request shape, required fields, account mapping, upload references, scheduling data, and known platform constraints. The destination platform still decides final acceptance, processing, publication, visibility, analytics availability, and enforcement. Build your product as if the platform can say no, because sometimes it will.
Before shipping
Use these guidelines as product requirements for your composer, validation, media handling, bulk import review, and error messages. The cleaner those constraints are before publish, the fewer failed posts your users need to debug later.
Platform APIs change. Use these links to confirm current error behavior and field support.
Not always. Some platforms process media asynchronously or can reject content after the initial request. Your app should use status, errors, and follow-up data instead of assuming every accepted request is immediately published everywhere.
No. bundle.social can help move files through the workflow and expose useful errors, but platforms still enforce their own media formats, dimensions, duration limits, processing rules, and content policies.
The customer or end user sending the content is responsible for making sure they have the rights, permissions, licenses, and approvals needed to publish that content on the selected platforms.
Usually no. A clean composer is good, but hiding important platform differences creates worse failures later. Keep the shared workflow simple while still exposing destination-specific fields when they matter.
Build with less platform drag