🚨Error Reference
Match an exact error to its failing stage, preserve request evidence, and choose a correction without blind retries.
Find the returned error below. For API or MCP requests, start with Errors and retries. Use Accounts and identifiers for account or page ID errors.
Search this page with Ctrl+F or Cmd+F. Preserve the error text, request ID, and submission ID when asking support.
For a missing, delayed, or duplicate post without a known cause, start with Find a post's outcome before retrying. A symptom, status code, or historical incident does not establish the present cause.
API Errors
Authorization failed - please check your credentials
Double check your Blotato API key. Use the n8n/Make official Blotato nodes for easier setup. You don't have to worry about copy/pasting IDs or raw JSON code. See tutorial: Help guide
Wrong Blotato API Key
Check you've copied the API key correctly without whitespaces. Use the official Blotato n8n/Make nodes for easier setup - you won't need to hardcode API keys manually. See tutorial: Help guide
URL is empty
The submitted URL is empty. Inspect the preceding operation and the field mapped into this request. For a visual, verify completion and use its returned mediaUrl or imageUrls. Do not substitute a longer fixed wait for checking status and errors. See visual workflow.
Wrong Account ID
Use the official Blotato n8n/Make nodes - you can select accounts from a dropdown instead of copying IDs manually. See tutorial: Help guide. If not using official nodes: Check you've copied the social account ID correctly from Accounts.
Account [ID] not found
The submitted account ID does not match the authenticated Blotato user and requested platform. Retrieve accounts through the same credential or MCP connection, then check the platform, current ID, and separate Page ID. Saved dropdowns and earlier AI lookups are not proof the ID is current. See Account not found.
Wrong Page ID
Facebook requires both Account ID and Page ID. Check you've copied Page ID correctly using the "Copy Page ID" button.
The setting for future activity history off Meta technologies is not in Account Center anymore
Meta's privacy labels differ by account version. Follow the current authorization screen's Accounts Center link if a change is required. Do not reset settings or remove a working connection to find an old label. See Meta privacy-setting diagnosis.
Invalid File Format
Check your file format is valid per social platform requirements.
Invalid Video Dimensions
Video dimensions are not supported by the target platform. For a portrait Instagram Reel, 1080 x 1920 or 720 x 1280 is a compatible export preset. The converter downscales Instagram video above 2,073,600 pixels, but does not force a 9:16 crop. Videos longer than 120 seconds need any required resizing before upload. Follow the Instagram Reel troubleshooting checklist.
reached_active_user_cap
TikTok reported its daily active-user quota. This error does not establish an account warm-up or content-quality problem. Preserve the error and request ID, then contact support or follow confirmed retry guidance. Do not repeatedly reconnect the account.
You Ran Out Of AI Credits
Go to Settings > Billing to check and add credits. Via API or MCP, check your balance with GET /v2/credits and buy more with POST /v2/credits (blotato_buy_credits) -- see Credits API.
Image or video stuck on "generating" indefinitely
A persistent loading state does not identify the cause or prove a failed job. Retrieve the existing visual's status and error before starting another generation. For website work, retain the visual link and report the displayed state and elapsed time. Do not assume a credit problem or a silent failure. See visual completion and recovery.
500 Internal Server Error on visual creation
The request failed at a server boundary, but the status alone does not identify the cause or prove no job was created. Preserve the response and request ID. Check for an existing visual before repeating generation, then inspect the selected template's inputs and any returned error. See Errors and retries.
Media conversion failed
Conversion did not finish. This message alone does not identify the cause. Blotato also returns it when the source download fails or returns an empty response. Inspect the source URL and exact processing error, then check the file's metadata against the destination's requirements. Follow media diagnosis. Check the original submission's status before retrying.
ClientError: Command failed: ffprobe ... Invalid data found when processing input
The metadata probe could not read its input as valid media. Check the fetched response and inspect the source file. An error page, incomplete transfer, or invalid media are possibilities, not a confirmed diagnosis from this text alone. Replace or re-encode the file only after identifying the problem. See media diagnosis.
Could not publish on Instagram: An unexpected error has occurred
This error comes from Instagram/Meta, not Blotato. Troubleshooting steps: 1) Check the Logs for the full error. 2) Reconnect your Instagram account in Accounts. 3) Verify the media URL is publicly accessible (open in incognito). 4) Reduce hashtags and caption length. 5) Increase time between posts. If the error persists after reconnecting, submit a support ticket with the reqId from the error message.
Unsupported media format (.mov)
Blotato recognizes MOV files, but handling differs by platform. LinkedIn converts non-MP4 videos to MP4. Facebook accepts MP4 and MOV. Other publishers may receive the MOV file unchanged. For the widest compatibility, encode the video as H.264 with AAC audio in an MP4 container. If the video is longer than 120 seconds, prepare it to match the target platform before uploading because automatic conversion will not run. See Media Requirements.
Account [ID] not found (LinkedIn)
For LinkedIn company pages, you need both an accountId and a pageId. A common mistake is passing the pageId where accountId is expected. Use GET /v2/users/me/accounts to get the accountId, then GET /v2/users/me/accounts/{accountId}/subaccounts to get the pageId. Pass accountId in post.accountId and pageId in post.target.pageId. See: Accounts API
503 Service Unavailable
Identify which service returned the response and preserve its body and request ID. For a read, use a delayed, bounded retry. After a write, check for existing work first. A 503 alone does not establish a social-platform outage or exclude a Blotato issue. See Errors and retries.
504 Gateway Timeout
The request timed out at a gateway. The downstream operation's outcome is not established by this response. Check the original submission or creation before retrying a write. Reconnect only if a separate authentication or permission error requires it. See publishing-status diagnosis.
Wrong Template Parameters
Each video template has different parameters. Check API docs for correct template parameters.
Missing AI Voice
POV template doesn't include AI voice. Use empty template ID for AI voiceover.
Missing Music
Add autoAddMusic: true parameter in PUBLISH TO TIKTOK step for music.
Wrong Heygen API Key and IDs
Check you've copied HEYGEN AVATAR ID correctly, not the Avatar GROUP ID.
You're On Heygen Free Plan
HeyGen API requires $99/mo API plan. Free API plan won't work.
Your Avatar Has a Background
Set matting to false and remove background section for default avatar background.
Invalid JSON Error
Validate JSON at jsonlint.com and compare with Blotato API docs.
The service is receiving too many requests from you
Rate limit exceeded. Upload Media: 30 requests/minute. Publish Post: 30 requests/minute.
Exceeded rate limits (repeated YouTube or LinkedIn publish failures)
The platform is rate-limiting publishing for your connected account. Wait an hour and retry from Posts > Failed. If posts keep failing with this error after waiting, reconnect the social account in Accounts, then retry the post -- a stale connection token keeps triggering the platform's rate limiter.
Unsupported media format: mov,mp4,m4a,3gp,3g2,mj2
Blotato did not recognize the file's container brand. A filename ending in .mp4 does not establish the format. Inspect the metadata and export an MP4 file, then check the destination's requirements. This is separate from the 120-second conversion limit. Follow container identification.
The aspect ratio is not supported
Video aspect ratio not supported by platform. Check platform requirements.
body/template/id must be equal to constant
Check the request URL and body together. Legacy /v2/videos/creations uses a different schema. Current /v2/videos/from-templates uses templateId and inputs. Retrieve the template specification without running a blank generation job. See Create Visual migration.
scenes.0: missing object
Incorrect JSON format for scenes array in CREATE VISUAL node. Each template has a specific scenes format -- find your template's exact format with examples at Visual Templates. To debug: (1) Select template in n8n/Make, (2) Remove ALL parameters including Prompt, (3) Run the step, (4) Check Logs to see the exact JSON structure your template expects.
slides.image: must be at most 400 characters
The image field expects a short public URL (e.g. https://your-site.com/image.jpg), not a base64 string or data blob. Keep image URLs under 400 characters.
mediaURL is null or empty
Video not done. Increase wait time or check if you have AI credits (GET /v2/credits).
Cannot read properties of undefined (reading 'mediaUrl')
The publishing queue did not receive 1 usable media-processing result for every media URL. First confirm the Create Visual job reached done and every mediaUrls value is a public file URL. Retry the post once. If the same error returns, contact support with the request ID so the team can inspect the queue results. Reconnect a social account only when the Logs shows a separate authentication error.
Cannot read properties of undefined (reading 'status')
The social platform (Instagram, TikTok, etc.) did not return a response. This is usually a temporary issue. Wait a few minutes and retry. If the error persists, check that your media file is in a supported format: Social Platform Requirements. In the web app, retry from the Posts > Failed screen.
Failed to upload stream to Supabase
The media file could not be saved to storage. Common causes: the source URL is not publicly accessible, the URL points to a preview page instead of the direct file, the file is too large, or the media file is corrupted. Open the media URL in an incognito browser window to verify it downloads directly. If using Google Drive, use a direct download link, not a /view link.
Could not upload media to storage
Same underlying cause as "Failed to upload stream to Supabase" above. Blotato fetched the URL in your mediaUrls but could not read it as a media file, almost always because the file is not reachable rather than broken. Check: 1) The URL is publicly accessible -- open it in an incognito window and confirm it downloads the raw file instead of a login or preview page. 2) It is not a Google Drive or Dropbox share link -- those open a preview page, so use a direct download link (https://drive.usercontent.google.com/download?id=FILE_ID&export=download&confirm=t). 3) The file is within your plan's upload size cap (Plan Limits). For local files, use the Presigned Upload flow and publish with the returned publicUrl.
Failed to fetch media URL: char '...' is not expected.:1:1 (often shown in n8n alongside "Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.")
Inspect the available response status and body without exposing secrets. An unexpected character in a deserialization error does not establish the complete response body or cause. Check URL accessibility, expiry, actual media content, and upload completion. A Blotato hostname or a later successful retry does not prove a timeout. Follow media-fetch diagnosis and publishing-status checks before another submission.
Please review our URL ownership verification rules
TikTok rejects certain URLs. Try using a different hosting service for your media, or use the optional Blotato Upload endpoint first: Help guide
TikTok's servers may be experiencing issues. This is a retryable error
TikTok server issue or posting too frequently. Wait and retry.
Could not refresh TikTok access_token: Service Unavailable
TikTok's servers temporarily rejected the token refresh. Wait 15-30 minutes and retry. If the error persists, reconnect your TikTok account in Accounts.
JSON value expected but got '<' at position 0 (TikTok)
TikTok's API returned an HTML error page instead of a JSON response. This is a temporary TikTok server issue (outage, rate limiting, or maintenance). Your post payload is valid. Retry after a few minutes. If it keeps failing, reconnect your TikTok account in Accounts.
Threads API Feature Not Available: This user does not have access to this Threads API feature
Link Instagram account to Threads. Warm up Threads account for a few days with posts before connecting to Blotato.
Failed to read media metadata. Is the file accessible and a valid media file?
Blotato could not obtain usable metadata. Check the exact error, server-to-server accessibility, response content, file container/codecs, and completed upload bytes. Browser success alone does not prove server access. Do not infer a host problem or metadata-reader defect from an intermittent result. Presigned upload transfers local bytes directly to storage, but publishing still needs accessible media. See media upload and conversion.
Google Drive virus scan warning popup blocking media access
Google Drive sometimes returns a warning page instead of the file for large videos. Blotato does not impose a 100 MB Google Drive cutoff. First, share the file as "Anyone with the link" and use https://drive.usercontent.google.com/download?id=FILE_ID&export=download&confirm=t. If Google Drive still returns the warning page, use the Presigned Upload flow, frame.io, AWS S3, or Google Cloud Storage. Check your Blotato plan limit and the destination platform's media limit separately.
Base64 data is too large, maximum size is 20MB
This error happens when uploading media larger than 15MB via the n8n Upload "Binary Data" option. Switch to URL-based upload: use the Presigned Upload endpoint to upload directly to Blotato, or host on AWS S3/GCP and pass the URL. See: Plan Limits for more details on max upload sizes.
Visual creation fails or images are blank when using self-hosted image URLs
Inspect the visual's current status and error, then verify its input URLs. Blotato's server fetching an asset is a different request from an assistant uploading a file. A blank preview alone does not prove firewall or CDN blocking. If host logs show a blocked fetch, provide the evidence to the hosting administrator and support before changing access rules. Do not invent Blotato IP ranges or apply client egress advice. See support media diagnosis.
Error posting to Instagram: No error
I've noticed a recent glitch with Instagram API that sometimes returns "No Error" and video rejected, but this looks like an issue on IG side, as I haven't changed anything on the Blotato side. I'll keep monitoring it, but I generally recommend the following:
reduce the number of hashtags
reducing the length of caption
increasing time between posts
Error posting to Instagram: An internal server error occurred
A brief temporary outage of Instagram's API, not a Blotato issue. Blotato auto-retries the post 2 times. If it still failed, the outage lasted longer than a few minutes -- wait a few hours and retry from Posts > Failed. See Instagram FAQs.
Instagram rejected your post
The account is hitting Instagram's spam and bot-risk checks. Log into the Instagram account daily for the next week and scroll the feed for about 10 minutes like a normal user, and space out posts instead of retrying in a rapid loop. See Instagram FAQs.
The user has not authorized application (Instagram/Facebook)
The Meta access token for the account is no longer valid -- tokens go stale when they expire, get revoked (password change or security refresh), or the Blotato app was removed from Business Integrations. Newly released features like comments and messaging also require updated permissions. Fix: go to Accounts, click Reconnect on the account, and approve the Meta popup with the Instagram account and its linked Facebook Page both checked.
Could not publish on Instagram: Error validating access token: Sessions for the user are not allowed because the user is not a confirmed user
This error comes from Instagram/Meta. The Instagram account session is not confirmed. To fix: 1) Log into the Instagram account in a browser and complete any pending prompts (email/phone confirmation, security checkpoints, updated terms). 2) Reconnect the account in Blotato: go to Accounts, disconnect and reconnect using an incognito browser logged into only that Instagram account. 3) Verify the account is a Professional or Business account (personal accounts have issues with third-party publishing). See: Help guide
Instagram allows a maximum of 5 hashtags per post
This is a Blotato guardrail, not an Instagram rule. Instagram itself allows more hashtags, but Blotato caps posts at 5 on purpose because more than 5 hashtags reduces your reach on Instagram, TikTok, and Facebook. Fix: trim your caption to 5 hashtags or fewer and republish. See hashtag rules by platform and how many hashtags to use.
Source / Ingestion Errors
TikTok video has no captions / transcript extraction failed
Blotato extracts the transcript from TikTok videos to use as a source. If the TikTok video has no captions (subtitles), Blotato cannot pull the transcript. Try a different TikTok video that has captions, or copy-paste the video's content as a Text source instead.
Connection Errors
400 Session Error Connecting Instagram Account
Sometimes connection succeeds despite error. Test with a post first. If not, use incognito browser, log out of other accounts, log into only the target account, then reconnect.
"No LinkedIn pages found for this account"
Not an error. This message appears in the Select LinkedIn pages window after your LinkedIn sign-in succeeds. It means the signed-in profile has no company Pages where it holds the Super Admin or Content Admin role. Analyst, Curator, Paid Media Admin, Recruiting Poster, and collaborator roles do not expose Pages to Blotato. Your personal LinkedIn profile remains connected. See: LinkedIn FAQs
Unable to connect LinkedIn company page (a Page you administer is missing from the list)
Open the Page on LinkedIn and go to Admin tools > Manage admins. Confirm your profile has the Super Admin or Content Admin role. Ask a Super Admin to update your role if needed. After the role changes, use an incognito browser, log into LinkedIn, then Blotato, and connect the Page. If your role stays unchanged, ask a Super Admin or Content Admin to connect the Page to Blotato.
YouTube Unauthorized error
Use incognito browser. Log into YouTube, then Blotato. Reconnect account. Update YouTube account ID in automation workflows.
Unable to connect social account (general)
Use incognito Chrome browser. Log into social account first, then Blotato. Connect account.
invalid_grant (Instagram/Meta)
The Instagram/Meta authorization token expired. Go to Accounts, find the Instagram account, and click Reconnect. This error often causes follow-on "mediaUrl" TypeErrors -- fix the token first.
Account requires reconnect
The account's authorization token expired, or the account requires some other manual reconnect/confirmation. Go to Accounts, click Reconnect on the Instagram account, then retry your request.
invalid_grant (Claude Cowork / MCP)
Your Blotato MCP OAuth connection expired. In Claude, open Customize > Connectors, remove and re-add the Blotato custom connector, and re-approve access via OAuth. This is separate from reconnecting a social account. See: MCP Setup
Blotato shows "Connected" in Claude Settings, but Claude.ai returns an OAuth error when asked to list accounts
Blotato API and MCP require a paid subscription. Go to Settings > API and click "Generate API Key" to activate your paid subscription.
Comments Errors
Comments not available for this post's platform (error code 20200)
The post you tried to comment on is on a platform Blotato does not support comments for. Comments work on Instagram and Facebook Page posts only. Twitter/X, TikTok, LinkedIn, Pinterest, Threads, Bluesky, and YouTube are not supported. See Comments API.
Comment failed to post (error code 20201)
The social platform rejected the comment. Check the comment's errorMessage for the reason. Common causes: the parent post was removed, the comment triggered the platform's spam rules, or the account lost comment permissions. Reduce how often you comment and retry. See Comments API.
Blotato does not have permission to post comments on this Instagram account (error code 20203)
The connected Instagram account is missing the permission Blotato needs to post comments. Disconnect the account, connect it again with Login with Instagram, and accept every permission on the consent screen. See Connect Instagram.
Active contacts limit reached (error code 20101)
You reached your monthly active-contacts limit by replying to audience comments. Your count resets at the start of next month. Upgrade your plan or check your current account limit. See Comments API.
Messaging Errors
Active contacts limit reached (error code 20101)
You reached your monthly active-contacts limit by messaging new people. Your count resets at the start of next month. Upgrade your plan or check your current account limit. See Active Contacts.
Message failed to send (error code 20102)
The social platform rejected the message. Check the message's errorMessage for the reason. Common causes: the 24-hour messaging window closed, the comment you replied to is invalid or already received a private reply, or the account lost messaging permissions. See Messages API.
Your Instagram account has expired / Your Facebook account has expired (error code 5002)
The connected account's authorization expired, so the message never reached the platform. Reconnect the account. See Connection Errors.
DM Automation Errors
No connected Instagram account / No connected Facebook account (error code 5000)
The account the automation runs on is disconnected or expired. Reconnect it in Accounts, then publish the automation again.
Automation is invalid (error code 20303)
The automation is missing something it needs to go live: at least one trigger that is turned on, message text of 1 to 640 characters, a valid http(s) URL on every button, a message on every gate you turned on, or a valid http(s) URL on the webhook. Fix the flagged field and publish again. See DM Automations API.
Flow must have at least one active trigger (error code 20303)
You turned off the only active trigger on a live automation, or tried to publish with every trigger off. Turn another trigger on first, or move the automation to draft. See Update DM Automation Trigger.
Flow may have at most one trigger per trigger type (error code 20303)
An automation holds one comment trigger and one message trigger at most. Remove the duplicate trigger and publish again. See Trigger Object.
Follow gate requires an Instagram automation (error code 20303)
A follow gate runs on Instagram only. Remove it from the Facebook automation, or rebuild the automation on an Instagram account. See Follow Gate Object.
Request URL must be http(s) / Request URL resolves to a private address / Could not resolve request URL (error code 20304)
The automation webhook failed. Blotato calls public http(s) endpoints only and rejects private, loopback, link-local, and cloud metadata addresses. Point the webhook at a public URL and confirm the domain resolves. Blotato does not follow redirects, so use the final URL. See Webhook Object.
Request timed out after 15s (error code 20305)
The automation webhook did not answer within 15 seconds. Blotato logs the timeout and the automation run still completes. Make your endpoint answer faster if you need the response in later automation steps. See Webhook Object.
Your subscription is not active. DM automations are paused until you reactivate. (error code 20300)
The run stopped because your Blotato subscription is not active. Reactivate your plan in Settings > Billing.
You have reached the maximum active contacts for your plan this month (error code 20101)
The DM the automation tried to send hit your monthly active-contacts limit, so the run failed. Wait for the monthly reset, upgrade your plan, or check your current account limit. See Active Contacts.
A DM automation that fails after the message is queued reports the platform error on the run, not on the request. Open the automation in Automations, or call List Runs, and read the run's error. The object includes code, message, and, when available, action and details with account, permission, platform, and retry context. The codes match the messaging errors above.
A run stuck on a follow gate until it expires has 2 common causes. An account connected before DM automations and follow gating landed might lack the button-tap subscription, so reconnect the account in Accounts. If the first message arrives but the next message does not send after the person taps I'm following, another app might control the conversation in Meta. Remove the default routing app or select Blotato, then turn off Take control of conversations for every other app. Follow the conversation routing checklist.
Instagram also renders the confirm button in the mobile app only, so ask for a typed reply in the gate message for desktop readers. Blotato runs the follower check on any reply.
A run showing expired is not an error. It means the person never answered a follow gate inside 30 days or an email gate inside 72 hours, so nothing further sent. A run showing superseded means a newer run started waiting on the same person.
A webhook endpoint answering with a non-2xx status does not fail the run. Blotato records the status in the run logs and the run still completes.
Platform-Specific Errors
Post failed to publish. Could not upload video
Each platform has different requirements for video uploads. Check that your video follows the requirements here: Help guide
Could not upload media to [platform] (e.g. "Could not upload media to Twitter"), same message on every platform
The platform rejected the media Blotato tried to upload. This is not a rate-limit or credits problem, and retrying the same media without changes will not help. Open the specific failed post in Posts > Failed (web app) or the Logs (API) to read the exact per-post error, then follow the matching steps in this reference. Common causes: the media does not meet the platform's format or size specs (Social Platform Requirements), or a stale connection -- reconnect the account in Accounts and retry. When the same message appears on every platform at once, check each post's error separately, because the cause can differ per platform.
This video is N seconds long, but we can only automatically fix videos up to 120 seconds
Your video needs cropping, resizing, downscaling, re-encoding, or bitrate adjustment, but its duration exceeds Blotato's 120-second conversion limit. The error lists the exact target-platform requirement that Blotato cannot fix automatically, such as MP4 format, smaller dimensions, a crop size, or lower bitrate. Either shorten the video to 120 seconds or less, or export the source to match every target-platform requirement before publishing. For Instagram Reels, follow the Instagram Reel troubleshooting checklist. Check Social Platform Requirements for other platforms.
The user has exceeded the number of videos they may upload (YouTube)
YouTube upload limit reached. Wait 24 hours. Check API quota in Google Cloud Console. Verify account.
You have reached the maximum number of 10 posts for the last 24 hours for this account (YouTube)
Blotato enforces 10 posts per channel per rolling 24 hours on Starter, or 25 on Creator and Agency. Wait for prior successful posts to leave the window. YouTube's own restrictions are separate. Check the original outcome before retrying or uploading manually. See YouTube limit diagnosis.
You have reached the maximum number of 25 posts for the last 24 hours for this account (Facebook)
Facebook publishing is limited to 25 posts per 24 hours per Page. Each Page has its own independent limit. Wait 24 hours and try again, or publish to a different Page.
You have reached the maximum number of 50 posts for the last 24 hours for this account (LinkedIn)
LinkedIn publishing is limited to 50 posts per 24 hours per profile and per company Page. Each profile and company Page has its own independent limit. Wait 24 hours and try again, or publish to a different profile or company Page.
Unsupported picture size (TikTok)
Inspect the image's format, dimensions, and file size. Use a JPEG export, such as 1080 × 1920 for portrait images, at no more than 20 MB. Blotato attempts image normalization before publishing, but a successful upload does not prove TikTok accepted the image. Follow TikTok image requirements.
TikTok views consistently < 50
Account likely shadowbanned. Start fresh with new account.
TikTok views consistently ~200
TikTok doesn't know your video topic. Use niche keywords in title, description, and audio.
Single TikTok video stuck at low views
Change video privacy to PRIVATE, close app, reopen, switch back to EVERYONE.
TikTok account banned
Account not warmed up properly. Follow warm-up guide. Don't post more than 3x/day via API. Stay active on account.
body.post.target must have required property 'isYourBrand' or 'isBrandedContent'
Both fields are required on every TikTok post sent through the REST API, including the n8n and Make.com nodes. Put them inside the target object, not content. There is no default -- send both explicitly, even when both are false. Set isYourBrand: true when the post promotes your own brand, and isBrandedContent: true for a paid partnership. See Publish Post.
Escape Multi-Line Paragraphs error
Long text with linebreaks needs escaping. In n8n use toJsonString() function.
Brand New Account error
Account not warmed up. Don't connect 3rd party apps until account is established with manual posts.
Sorry! This site doesn't allow you to save Pins.
This error is from Pinterest. Two common causes: 1) The website indicated they do not want to be pinned. 2) Pinterest's blocklist flagged your URL (often a false positive). Workaround: append parameters to your link (e.g., ?ref=pin&v=111) so Pinterest sees it as a new URL that bypasses the filter.
Pinterest API access is temporarily restricted to verified accounts only
Your Pinterest still looks pretty new. You MUST warm it up for 2 weeks before connecting to 3rd party posting tools like Blotato. Failing to do this often results in being shadowbanned or flagged by Pinterest. Start posting 1 pin per day manually, then gradually ramp up to 2, then 3, etc. pins per day. Once you get 100+ views per month, reconnect your Pinterest account with Blotato and it will be automatically verified. If your Pinterest account already has 100+ monthly views, do not keep warming it up. Go to Accounts, click Reconnect on the Pinterest account, then retry the publish.
Could not create Pinterest pin (no specific reason shown)
This is the generic wrapper Blotato shows when Pinterest rejects the pin without a readable reason. Open your Logs and click the failed request to read the exact Pinterest error response for that pin, then match it to the specific Pinterest rows above (permission, blocked URL, or verification). If the failure starts across all your Pinterest accounts at once while manual pinning still works in the Pinterest app, it points to a temporary Pinterest API issue on Pinterest's side rather than your account or link -- check the Logs for the exact response and retry later.
Error posting to Facebook: (#200) requires pages_read_engagement and pages_manage_posts permission (the full message may also mention "If posting to a group..." and "requires both pages_read_engagement and pages_manage_posts as an admin with sufficient administrative permission")
Confirm the intended Facebook identity has publishing access to the Page. Reconnect that identity and select the required Page and permissions. Blotato publishes to Pages, not Groups or personal profiles. Do not remove the integration as a routine next step. See Facebook connection diagnosis.
Please reduce the amount of data you're asking for, then retry your request (may also appear as "Could not upload video to Facebook: ...")
The message does not establish an outage, memory exhaustion, or a follower-count threshold. Check the Page and original submission before retrying, since an error does not prove no publication occurred. Retain the exact response and request ID. See Facebook Errors and publication outcome diagnosis.
Error posting to Instagram: We restrict certain activity to protect our community.
Instagram made a final decision based on risk/spam scores. To fix: 1) Reduce the number of hashtags. 2) Reduce your caption length. 3) Increase time between posts. 4) If none of the above works, try posting manually to warm up your account and prove to Instagram you're not a bot.
Instagram encountered a temporary error while publishing your post. Please try again in a few minutes. (error code 20003)
Instagram returned a temporary error while Blotato published the post. Blotato retries on its own before reporting this. Wait a few minutes and retry from Posts > Failed. The message ends with a reference ID. Include it when you contact support if the post keeps failing.
Instagram server media processing timed out. Please try submitting the post again in a few minutes. (error code 20003)
Blotato exhausted its publishing wait/retry path while Instagram still reported media not ready. Preserve the reference ID. Check the destination and original post status before a delayed retry. Do not treat a timeout alone as proof of no platform-side result. See publishing-status diagnosis.
Could not publish on Instagram: Unsupported post type. The post has too little or too many attachments to qualify as a carousel
Via API, Instagram supports a maximum of 10 images or videos per carousel. See Instagram Media Requirements.
This user is not allowed to post a video longer than 2 minutes (X/Twitter 403 Forbidden)
X rejected the video's duration for the connected account. Blotato passes Twitter videos through without automatic conversion, so its 120-second conversion gate is not the cause on this path. Check the account's API publishing restrictions and file requirements. An X Premium subscription does not guarantee acceptance. Follow X video troubleshooting.
You are not permitted to perform this action (X/Twitter 403 Forbidden)
Twitter/X authorization expired or permissions changed. Go to Accounts, find your Twitter account, and click Reconnect. Re-authorize the app when prompted. Retry your post after reconnecting.
You are not allowed to create a Tweet with duplicate content (X/Twitter 403 Forbidden)
X/Twitter rejects posts with identical text to a previous tweet on your account. Change the caption text (even slightly) before reposting. If you scheduled the same post twice by accident, delete the duplicate from Posts > Scheduled.
Post published twice / duplicate post
Record both platform URLs, destinations, submission IDs when available, and timestamps. Duplicate content does not by itself prove a timeout or identify which client sent the requests. Ask which copy to keep before removal through the social platform. Send support the evidence. See publishing-status diagnosis.
Bluesky media attachment rejected
Attach up to 4 images or 1 video per Bluesky post. Confirm every media URL is public and uses a supported format. See Bluesky Media Requirements.
Failed to publish TikTok post after 3 retries (Unknown error reason)
Blotato exhausted its retry loop. Unknown error reason is a fallback for an unmapped failure reason, not proof of an outage or credit problem. Check the destination before another submission, then send support the full error and reference IDs. See TikTok failure diagnosis.
TikTok post disappears and never appears (stuck "buffering," not in Failed Posts)
The publishing outcome is unresolved. Check the original submission, destination, and existing post records. Do not repost because the schedule disappeared or blame a service without evidence. See TikTok missing-post diagnosis.
Error uploading images to TikTok: Please notice the user to update their TikTok to the latest version to enable this functionality
This error comes from TikTok on image and carousel (photo) posts, and it appears even when the TikTok app is already up to date. On the phone connected to that TikTok account: update the TikTok app, open it once and log in, force close, reopen, then go to Profile > Settings and privacy > Free up space and clear the cache. Retry from Posts > Failed. If it persists, select Reconnect from the TikTok account actions menu in Accounts. If it still keeps returning, ask in the in-app chat for the team to remove the TikTok account from the database, then connect it fresh with Connect account > TikTok. If one TikTok account works while another keeps failing, the block sits on that specific TikTok account. See: TikTok FAQs.
Scheduled posts disappear at publish time (no error, not in Failed Posts) -- YouTube, Facebook, Instagram
A schedule leaving Upcoming Posts does not establish publication or failure. Check Published Posts, Failed Posts, the intended platform account, and the original submission ID when available. Do not infer a corrupt stored file or re-upload without evidence. Follow Find a post's outcome before retrying.
Post shows "published" but does not appear on the platform
Blotato recorded publication. Check the intended destination and returned platform URL. An inaccessible URL alone does not prove deletion, spam filtering, or account suppression. Preserve the evidence and avoid a replacement submission until the result is understood. See publishing-status diagnosis.
Could not schedule post: No available slot time found in the next 9 months (also shown as "in the next year")
No available matching time was found in the search window. Check whether slots exist, match the requested platform/account/Page, and have available times. This applies to Next free slot time in the website and useNextFreeSlot: true in API requests. Open Weekly schedule to inspect eligibility. If a slot is needed, choose Add Slot, select Time, Days, and Accounts, then Create. Exact-time scheduling does not require slots. Do not remove scheduling fields as a workaround because an unscheduled request publishes immediately. See slot setup and Schedule Slots API.
Post shows CANCELED
CANCELED is a post status, not a publishing error. A post is marked canceled when its schedule was removed before it published: the scheduled post was deleted, moved back to drafts in the calendar, or removed via DELETE /v2/schedules/:id through the API. Nothing failed on the social platform, and it is different from FAILED (a permanent publishing error). If you meant the post to go out, open it and schedule it again.
Plan Limit Errors
These errors are returned when you exceed one of your Blotato plan limits. For the full table of limits per plan, see Plan Limits.
Account N not found (error code 5000)
The accountId does not belong to the API key you used, the account was disconnected, or you used an ID from another platform. Call List Accounts or blotato_list_accounts, then retry with one of the returned IDs.
Text length exceeds the character limit of N characters for platform X (error code 20005)
The post text is too long for the target platform. Shorten the text and any additionalPosts listed in the error details, then retry. Emoji and full-width characters count as 2.
Tweet is longer than N characters (error code 20005)
The tweet text is too long for the connected X account's limit. Shorten the text and any additionalPosts listed in the error details, then retry. Emoji and full-width characters count as 2.
You have reached the maximum number of connected accounts (N) for your plan. Please disconnect some accounts or upgrade your plan.
You hit the connected-accounts cap for your plan. Disconnect an account in Accounts or upgrade. Each connected Facebook Page counts toward the limit (the Facebook login does not), and for LinkedIn your profile plus each connected company Page count. See: Plan Limits
You have reached the maximum number of 3 unique accounts for the last 24 hours. Please upgrade your plan to add more.
This is a TikTok posting-destination limit on the Starter plan, not an account-connection limit. Blotato counts the distinct TikTok account IDs with successful posts during the rolling previous 24 hours. Posting again to one of those accounts does not use another destination slot. A post to a 4th account fails until one of the prior 3 leaves the window. The connection date does not affect this count. See: TikTok FAQs
You have reached the maximum number of scheduled posts (N) for your plan. Please remove some scheduled posts or upgrade your plan.
You hit the queued-scheduled-posts cap. Delete upcoming posts from Posts > Scheduled or upgrade your plan. See: Plan Limits
Scheduled time is too far in the future.
Your scheduled time is more than 9 months in the future. Pick a time within the 9-month window. See: Plan Limits
File exceeds the maximum upload size (N MB) for your plan. Upload a smaller file, or upgrade your plan to increase your max upload size.
Your media file is larger than your plan's upload cap. Compress or trim the file, or upgrade. See: Plan Limits
Platform Posting Limits
TikTok
25 posts per account per rolling 24h in the current validator; Starter also has a 3-destination cap
Counts successful Blotato posts. Creator and Agency remove the 3-destination cap, not the per-account cap. The Starter error still mentions 10 posts per account. See the documented mismatch.
50 posts per day per account
Hard limit per 24-hour window.
50 posts per 24h per profile and per Page
Your profile and each connected company Page each have their own independent 50-post limit.
Stored account cap, normally 10, 20, or 50 posts per rolling 24h
Set at connection from Pinterest-reported monthly views. Account-specific or legacy fallback values apply. Separate from the 100-view API-access check. See Platform Posting Limits.
25 posts per 24h per Page; 5 per day per Page recommended
Each Page has its own independent 25-post limit, so posts to one Page do not count against another. Posting above 5 per day per Page also negatively impacts post reach.
YouTube
10 posts per channel per rolling 24h on Starter; 25 on Creator and Agency
Enforced by Blotato. YouTube's own quotas and account restrictions still apply.
For full details on platform posting limits, see: Help guide
App Errors
Application error: a client-side exception has occurred while loading my.blotato.com
This is almost always a browser issue, not your account. Start with a hard refresh. If it persists, follow the full checklist in App Won't Load (client-side exception) below.
Troubleshooting Steps
App Won't Load (client-side exception)
If you see "Application error: a client-side exception has occurred while loading my.blotato.com" (often after a few loading screens, and you cannot log in), it comes from your browser, not your Blotato account. Work through these steps in order:
Refresh the page first. This clears it more often than you would expect.
Open my.blotato.com/login in an incognito window, logged out of other accounts.
Still stuck? Try a different browser or your phone to see if the issue is only on one device.
Turn off ad blockers and privacy extensions (uBlock, Ghostery, and similar), then reload.
Clear site data for blotato.com only: click the padlock by the URL, open Site settings, click Clear data, then log in fresh.
If none of that helps, open the browser console when the error shows (right-click the page, Inspect, Console tab), screenshot it, and send it to support through the in-app messenger.
General Connection Issues
Open incognito Chrome browser
Log out of all other accounts
Log into target social account only
Log into Blotato
Connect account
API Issues
Check your Logs - click on any request to see the full payload, error response, and which account it was sent to
Verify API keys copied correctly without spaces
Check you have sufficient AI credits (
GET /v2/credits)Validate JSON at jsonlint.com
Compare your request with API documentation
Account Health Issues
Warm up new accounts manually for several days
Post organically before connecting to Blotato
Stay active on account (reply to comments, engage)
Don't exceed platform posting limits
Use platform-appropriate content formats
Last updated