REST API

에러

모양은 하나, 코드는 구체적으로, 값은 다룰 수 있게.

모양

실패는 code 와 영어 message 를 가진 error 객체로 옵니다. message 에 끼워 넣은 값은 따로 필드로도 보냅니다. 그 값으로 자기 언어의 문장을 다시 만들 수 있습니다.

Idempotency-Key 헤더를 주면 두 번 올리는 대신 저장해 둔 응답을 그대로 돌려줍니다. 성공한 결과를 24시간 보관하고, 같은 키에 다른 본문이 오면 idempotency_key_reused 로 거절합니다. 층이 둘입니다. 키는 이 요청을 이미 실행했는지를 묻고, 내용 지문은 같은 글과 같은 파일이 같은 계정으로 10분 안에 다시 왔는지를 물어 duplicate_post 로 거절합니다. 계정 하나로 가는 글은 그 채널의 options.<channel>.content 가 있으면 그것을 글로 봅니다. 같은 파일을 다시 올려도 같은 파일로 보고, 그사이 지운 글은 막지 않습니다. 실패한 글을 다시 보낼 때도 같은 지문을 보고, 10분이 지났어도 같은 계정에 같은 글의 다른 글이 있으면 duplicate_post 로 거절합니다. 의도한 재발행이면 force: true 를 주세요.

위반이 여럿이면 한 번에 옵니다

규칙을 둘 이상 어기면 error.errors 에 전부 담기고, 첫 항목은 error 자리에도 그대로 펼쳐집니다. 한 번에 고치면 됩니다. 재시도할 때마다 다음 위반을 하나씩 듣지 않아도 됩니다. 둘만 예외로 혼자 옵니다 — no_accounts 와 empty_content 는 나머지 검사의 전제입니다.

{
  "error": {
    "code": "content_too_long",
    "message": "Threads allows 500 characters. This is 620.",
    "platform": "threads",
    "limit": 500,
    "actual": 620
  }
}

코드

이름타입설명
verification_required401Email verification is not finished.
next_post_taken409Another enabled automation is already waiting for the next post on this account. Only one can; it frees the slot once a post binds to it.
past_comments_not_supported400Sending an automation to past comments works on Instagram and Facebook. This channel's comments cannot be read back for it.
past_comments_no_trigger400The automation has no comment trigger, so there are no comments it would react to.
automation_not_live409The automation is a draft. Enable it first, then send it to past comments.
past_comments_no_post409The automation is waiting for the next post, so there is no post whose comments it could read yet.
past_comments_running409The automation is already sending to past comments. Wait for it to finish, or stop it with DELETE. The running job comes back in pastComments.
scheduled_at_invalid422scheduledAt is not ISO 8601 or has no timezone offset.
scheduled_at_range422scheduledAt is under 10 minutes or over a year from now.
draft_and_schedule422Both draft and scheduledAt were passed. Pick one.
batch_id_invalid422batchId is longer than 40 characters or has characters other than letters, digits, - and _.
naver_source_required409update_post sent a new body for a Naver Blog post whose source lives only in Naver (written in Naver's editor, published from a Naver draft, or published through uplika after its uploaded photo files were cleaned up) without the sourceVersion of its current source, or the post changed on Naver since that source was read. A body made from an old copy would lose its photos, videos, cards, tables, links and formatting. The response carries source (the post's current body with @keep lines), keep (their ids) and sourceVersion. Edit source and send it back with sourceVersion; delete a @keep line only to remove that block. Nothing was changed.
naver_keep_unknown422A @keep(...) id is not a block of the post being rewritten, or @keep was used outside update_post on a post written in Naver's editor. Use the ids from its current source (naver_source_required returns it). Nothing was changed.
post_not_editable409PATCH or /publish on a post that already went out on a channel that cannot rewrite it, or retry on one that has not. The message is the channel's reason from list_platforms (feature update, or update_imported for a post written directly on the channel). A post whose targets all failed did not go out: the message says so and names retry_post. Scheduled and draft posts can always be changed. A Naver Blog post whose edit screen Naver would not open (it went to the blog's home page; older posts written in Naver's previous editor do this every time) answers it too: change that post on Naver Blog directly.
live_post_no_schedule422PATCH with scheduledAt or draft on a post that already reached a channel: its send time is fixed. Pass content, mediaIds or options instead. A Naver Blog post still waiting for the browser extension has not reached Naver, so the same PATCH moves it back to a scheduled post or a draft.
live_post_accounts_fixed422PATCH on a published post with a different accountIds. A published post keeps its channels; pass the same ids or leave them out.
nothing_to_change422PATCH on a published post with none of content, mediaIds or options. There is nothing to rewrite.
target_required422An engagement call (like, reply, follow) without a target. Pass postId, or ownerHandle and externalId; follow takes ownerHandle.
thread_piece409PATCH, /publish or DELETE aimed at a later item of a thread. Sends rootId; use the first item instead.
post_spans_channels409DELETE, or PATCH on a published post, named the post by a link or a channel's own id, and the post is also on other channels. Nothing was called on any channel. Sends postId and channels [{ platform, accountId, handle }]; check with the person, then send the same call with postId to act on every channel.
naver_draft_not_found404publish_naver_draft with a logNo that is not in the blog's draft box. list_naver_drafts shows what is there.
account_required422The workspace has more than one account on that channel. Sends accounts; pass accountId.
invalid_api_key401The bearer token is not a valid key.
forbidden_scope403The key lacks the scope. Sends scope.
no_accounts422accountIds was missing or empty. Sends candidates, and next when nothing is connected. Sends needsReconnect and a reconnect hint when the channels you have are expired rather than missing.
empty_content422Neither text nor media was given, or the Naver draft sent to publish_naver_draft has only a title.
account_not_connected404One of the accountIds is not connected. Sends candidates.
account_expired422The channel ended this sign-in (expired or revoked). Sends platform. POST /v1/accounts/{id}/refresh answers with this code too: refreshing does not renew a sign-in. On Threads, Instagram and Facebook, publishing and the read and write routes (replies, metrics, inbox, deletes) also answer with this code when the channel has ended the sign-in, and that connection is marked expired. Reconnect the account under Connections.
platform_not_available422That channel is not live yet. Sends platform.
content_too_long422Sends platform, limit and actual.
media_required422That channel cannot post text alone. Sends platform.
media_mixed422No longer sent for a publish (2026-09-17). A channel that cannot mix images and video keeps the video and drops the images; the target's warning says what was dropped. TikTok still answers with it if a mixed set reaches the channel some other way.
media_too_many422No longer sent (2026-09-17). Over the channel's image, video or carousel limit, the first items up to the limit go out and the target's warning says so. Read the limits from GET /v1/platforms.
media_too_large422Sends limit, limitMb and actual. Video fetched by media_from_url has its own cap, lower than presign; the response carries limitMb. Larger videos go through media_upload_link or presign.
media_aspect_ratio422Sends limit and actual.
media_dimensions422Video wider than the channel's width limit, or with a shorter side below the channel's minimum (TikTok has one; see the channel's media spec in /v1/platforms). Sends limit and actual: actual above limit means too wide, below means too small. Image width is never a reason.
media_type_not_supported422Sends types.
media_too_long422Video longer than the limit. Sends limit and actual in seconds; actual has one decimal and is rounded up, so it is always above limit.
media_url_invalid422Not an https URL.
media_url_blocked422That address is private, loopback or link-local.
media_url_unreachable422The host did not answer, redirected too many times, or answered with an error. When the host sent a short error sentence, the message carries it (for example Wikimedia's "Use thumbnail sizes listed on https://w.wiki/GHai"). A Wikimedia thumbnail at a width Wikimedia does not serve is fetched once more at the largest standard width below it, and a 429 with a Retry-After of a few seconds is retried once after waiting. When the connection does not open or no response comes back, and the host has more than one address, the fetch is tried once more on the next address.
media_unreachable503The channel could not fetch the attached media from its URL at that moment (Telegram: "Wrong file identifier/HTTP URL specified"; Instagram and Threads: error_subcode 2207052, "Media URI does not meet requirements", or 2207003, the download timed out; Facebook photo posts: code 324 with error_subcode 2069019). The adapter already retried before giving up: Telegram with a cache-busting URL, Instagram, Threads and Facebook once more with a direct storage URL for that one file. TikTok's status check answering FAILED with video_pull_failed or photo_pull_failed ends the same way; TikTok is not called again inside the adapter. Recorded on the target's errorCode, not returned from a request. The file is kept for 7 days, so retry the post; if it keeps failing, upload the file again.
workspace_required400This account has more than one workspace and the request did not say which. Sends workspaces, each with id, name, slug and channels, so you can match what the person said without extra calls. Pass the x-uplika-workspace header, or the workspaceId argument on MCP tools. The same code comes back when the x-uplika-workspace header names a workspace that is not on this account, is outside the API key's scope, or was deleted. The message then says so, and workspaces lists the ones this request can use.
workspace_mismatch404The post, channel, or media is in a different workspace on the same account. Sends workspaces. Retry there instead of connecting the account again.
workspace_limit403The plan includes fewer workspaces than this account already has. Sends used and limit. Workspaces are the billing unit, so the fix is a larger plan, not a retry.
platform_already_connected409This workspace already has a channel on that platform, and a workspace holds one per platform. Sends platform, existingHandle, incomingHandle and existingExpired. When existingExpired is true, a reconnect came back signed in as a different account: have the person log in to the channel as the original account and reconnect, which deletes nothing. Otherwise connect the other account in another workspace. Disconnecting the existing one deletes its automations, conversations and scheduled posts. Reconnecting the same account is not affected.
quota_exceeded402The free plan allows a fixed number of posts a month and this workspace used them all. Publishing is blocked until the next period starts, which is a month from the signup date, not the first of the calendar month. Upgrade to remove the limit. A thread counts as one post, not one per item.
workspaces_invalid422The checkout asked for fewer workspaces than a paid plan includes, or for something that is not a whole number. Send the total number of workspaces you want, not the number of extra ones.
billing_not_configured503Billing is not switched on for this deployment. Nothing to buy yet.
full_access_open409Every feature is currently open to all users, so there is nothing to buy. Try again once plans are switched on.
checkout_failed503The payment provider did not return a checkout. Nothing was charged. Try again.
no_subscription422There is no paid subscription on this account, so there is no billing portal to open.
portal_failed503The payment provider did not return a billing portal link. Try again.
media_not_uploaded404media_complete (POST /v1/media/{id}/complete) was never called. media_complete also answers 422 with this code when the object is missing or empty (0 bytes); the row stays. error.reason says which: not_arrived (no bytes yet, PUT the file and complete the same id), upload_url_expired (the signed address ran out, error.nextStep is media_presign) or empty. While the address still works, error.uploadUrlExpiresAt says until when.
media_expired404The upload was reclaimed. Upload the file again. Also set as a post target's errorCode when the attached files were already gone at the moment it went out; that target cannot be retried.
image_unreadable422media_complete found the image incomplete or damaged (the upload was cut off) and discarded it; upload the file again. Also set as a post target's errorCode when the attached image could not be decoded at the moment it went out; that target cannot be retried, upload the file again and create a new post.
media_not_publishable422mediaIds names a document (PDF, HWP or HWPX). Documents are taken for DM automations only (deliver.mediaId); a post carries photos and videos. Sends mediaIds. Remove them and send again.
media_in_use409DELETE on a media item a post still uses, or on an original that a copy in another workspace still shares. Sends postId or cloneId. Delete that first.
media_delete_failed503Storage did not delete the file. The row is kept so you can retry; nothing else changed.
media_store_failed503media_from_url fetched the file but storage refused it, or fit_ad_images made the copies but could not store them. Nothing was saved. Try again.
media_read_failed503fit_ad_images (POST /v1/ads/images/fit) could not read an original image from storage. Nothing was made. Try again.
upload_bytes_missing409presign is refused because earlier presigned uploads never received their bytes. Sends stale, staleAfterMinutes and nextStep (media_upload_link). presign only works if you can PUT the file yourself; use media_upload_link (POST /v1/media/upload-sessions) for a file on someone's device, or media_from_url (POST /v1/media/from-url) for a public https address. Over MCP the tool result also carries a ready upload link (uploadLink) to give to the person, and the same link comes back while it lives.
api_unreachable503An MCP tool called our REST API and got no JSON back, such as a gateway page or a dropped connection. For a read, nothing was changed; try again. If a write (publish, edit, delete) ran out of time, it may still be running: the message says what to check (get_post, list_posts or list_naver_drafts) before sending it again.
server_restarting503Uplika is restarting for an update. A publish (POST /v1/posts with no schedule, a PATCH that sends a post now, or publish_naver_draft), publish_now (POST /v1/posts/{id}/publish), retry_post (POST /v1/posts/{id}/retry) or reply (POST /v1/posts/{id}/replies) is refused before anything is created or sent. Sends retryAfterSeconds and a Retry-After header (about 20 seconds). Send the same request again after that; an Idempotency-Key is safe to reuse because only 2xx answers are stored. Scheduled posts, drafts, edits of a post that is already live, deletes and reads are not refused.
naver_media_kind_mismatch422The Naver Blog body refers to media with the wrong syntax: a video written as a photo (![](media:ID)), a photo written as @video(media:ID), or a video inside @group(). Checked on content, each threadItems entry and options.naver_blog.content, on create and on edit. The response lists each mismatch with body, line, mediaId, kind and the line to write instead. Photos use ![description](media:ID); videos use @video(media:ID) on their own line.
naver_media_over_limit422The Naver Blog body places more photos or videos than Naver takes per post, on its own or together with the attached media that come before it, so some references would not go out. Checked on create and on edit, before anything is saved. Sends referenced (images, videos), limits (images, videos), droppedIds, the references that would not go out, total (images, videos), what would go to Naver before fitting, and unplaced (images, videos), attached media the body does not place, which go at the end. Nothing was changed. Take out the attached media the body does not place, place fewer media in the body, or pass mediaIds with only the media the body places.
naver_media_ref_unattached422The Naver Blog body places media that is not attached to the post, so the extension would stop at that line with media not in payload. It happens when a photo line is written in a shape the server does not read as a reference but the extension does, such as ![alt](media:ID)<br>. Checked on create and on edit, before anything is saved. Sends mediaIds, the ids the body places but the post does not carry. Nothing was changed. Pass those ids in mediaIds, or write each photo on its own line as ![alt](media:ID) {.attrs} with one pair of braces and nothing after it.
media_ref_unknown400The Naver Blog body points at media:<id> we cannot find. The response names the ids. Check them against what media_presign (POST /v1/media/presign) or media_from_url (POST /v1/media/from-url) returned. Uploaded files are cleaned up about a day after the post goes out: on a Naver post that is already live, its photos are the @keep lines of the current source (this response carries source and sourceVersion when the edit took that path), so keep those lines and use media: only for photos you upload now. On a post saved only as a Naver draft (draft:), the response carries draftLogNo: to keep its photos, publish the draft first and then edit it. Retrying the same payload will not help.
media_ref_not_supported422The body places media with media: references, which only Naver Blog, Ghost and WordPress understand, but a target on another channel would publish that markup as literal text. Publish to the channels that read them in their own post, or drop the references and pass mediaIds.
media_ref_mixed_channels422The body places media with media: references and the post mixes channels that read them by different rules: Naver Blog; Ghost and WordPress. Channels in the same group share one body; publish to each group in its own post.
ghost_title_required422Ghost needs options.ghost.title.
ghost_title_too_long422The Ghost title is over 255 characters, counted in code points. Sends limit and actual.
ghost_tag_invalid422A Ghost tag is empty, longer than 191 characters, contains a comma, or starts with # (Ghost would make it a hidden internal tag). Sends limit.
ghost_directive_not_supported422A Ghost body line uses Naver Blog syntax (@group, @video, @card, or {…} after a photo), which Ghost would print as plain text. Sends line.
wordpress_title_required422WordPress needs options.wordpress.title.
wordpress_title_too_long422The WordPress title is over 255 characters, counted in code points. Sends limit and actual.
wordpress_tag_invalid422A WordPress tag is empty, too long or contains a comma (WordPress splits tags on commas), or there are too many tags. Sends limit and max.
wordpress_directive_not_supported422A WordPress body line uses Naver Blog syntax (@group, @video, @card, or {…} after a photo), which WordPress would print as plain text. Sends line.
wordpress_html_not_supported422The WordPress body has raw HTML, a block or an inline tag outside code. uplika sends HTML it renders from Markdown and refuses markup it did not write, so a script in someone else's text never reaches the site. Write that part in Markdown. Sends line.
media_not_configured503Media storage is not set up.
post_not_found404No such publish in this workspace. DELETE also answers this for a post whose publish record was removed when its account was disconnected before 7 October 2026; then the message says the post is still on the channel and to call delete_post with the channel link.
media_not_found404No such media in this workspace.
key_not_found404No such API key.
grant_not_found404No such authorization.
nothing_to_retry422Every target already succeeded, or the post has no targets left because its account was disconnected before 7 October 2026 and its publish record was removed (the message says so and points to the channel link).
not_published422The post has not gone out yet.
delete_window_expired422Telegram only lets a bot delete messages for 48 hours after posting. Retrying will not help; the message has to be removed by hand in the app.
facebook_delete_unsupported422Facebook refused to delete this post with error 200, "New Pages Experience Is Not Supported: This endpoint is not supported in the new Pages experience." Nothing was deleted on Facebook and the Facebook target stays published. It is not a sign-in problem: reconnecting the account or sending the same request again gets the same answer. Delete the post on Facebook itself. If the same request already deleted the post on another channel, the message starts with "Deleted on <channel>."
platform_error503The channel refused or did not answer, or dropped an upload session before it finished.
duplicate_post409The same content with the same files went to this account within 10 minutes. For a post to one account, the content is that channel's options.<channel>.content when it has one. A file uploaded again counts as the same file, and a post deleted since does not block. Sends postId. Pass force: true to publish anyway. A retry answers it too, however long ago the post failed: when a different post with the same content and the same files is queued, going out, published or scheduled on the same account, and was not created more than 10 minutes before the one you retry. Then postId is that post and targets are the failed targets of this post that were held back. Nothing is retried; pass force: true to send it anyway.
unauthenticated401No session and no valid key.
platform_rejected_content400 · 404 · 409 · 422 · 503The channel refused the content itself. Retrying will not help. Read and delete paths pass the upstream status through; the publish path reports it as 503. A 409 means nothing was changed and the reason is in message, for example a Naver Clip clip that is not among the profile's most recent clips.
platform_auth_error503The channel refused our access to that account. Reconnect it. Kept at 503 so it is never confused with a problem with your uplika key.
topic_tag_invalid422The topic tag has a period or an ampersand in it, or is longer than 50 bytes in UTF-8 (about 16 Korean characters; limit and actual say the numbers). Threads does not allow those.
youtube_video_not_replaceabletargetAn update to a published YouTube video came with a new video file. YouTube does not swap the file of a video that is already up; edit the title, description, tags or privacy instead, or publish a new video.
topic_tag_not_supported422You sent the top-level topicTag and some of the channels you picked do not take a topic tag. Sends platforms (every such channel) and platform (the first one). Drop the tag, or move it to options.threads.topicTag, which only Threads reads and which never gets this error.
api_key_revoked401That key was revoked. Create a new one. Kept separate from invalid_api_key so you do not go looking for a typo.
api_key_expired401That key passed its expiry. Create a new one.
idempotency_key_reused422That Idempotency-Key was already used with a different body. Use a new key for a new request.
publish_in_flight409That post is still going out. Deleting mid-flight would let it publish after you deleted it. Wait a few seconds and try again.
delete_in_flight409A delete for that post is already running in the browser extension. Nothing new was sent. Read the post with get_post: when its Naver target is cancelled, the delete went through. For a Naver draft, check list_naver_drafts instead: when no draft with the post's title is there any more, the draft was removed. retryAfterSeconds is 60 while that draft delete still waits its turn and 15 once the extension has picked it up.
edit_in_flight409Another update of the same post (update_post or publish_naver_draft) is still in progress, so this request saved and sent nothing. Wait for the other call to return, read the post with get_post, and send your change again only if it is not there. A scheduled or draft post first waits a moment for the update ahead of it and gets this answer only when that one does not finish in time.
extension_outdated422The uplika browser extension in the user's Chrome is too old for this action (for example update_post needs 0.4.0 or later, a Naver Blog post whose photos carry the AI usage label needs 0.7.3, and rewriting a Naver post written in Naver's editor needs 0.7.8). Nothing was sent. The response carries extensionVersion and requiredVersion. Uplika asks that Chrome to update the extension at the same moment, and with no Naver job running it switches on its own, so call again in a minute or two; if it is still the old version, ask the user to press Update now on the extension badge at the top of the dashboard. If the required version is not on the Chrome Web Store yet (still in review), the message says so and bridge.awaitingRelease is true: updating finds nothing, Chrome installs it on its own once it is published, and until then the action has to be done by hand in Naver.
thread_and_content422You passed both content and threadItems. Pass one.
thread_empty422threadItems was an empty array.
container_expired503The upload container expired before the post went out. Create the post again.
permission_denied503The channel refused for permission reasons.
invalid_json400The request body could not be read as JSON: broken syntax, a top level that is not an object or array, a charset other than UTF-8, or a Content-Encoding other than none, gzip, deflate or br. The message says which, in brackets. Nothing was run; fix the body and send it again. This call is not in /v1/logs because it stopped before we knew who sent it; quote the x-request-id response header if you contact us.
body_too_large413The request body is larger than this path accepts (100KB for REST and MCP). Sends limit in bytes. Nothing was run; send a smaller body.
internal_error500Our fault. The response carries no detail; the request id is in the logs.
system_error503A target failed on our side, not the channel's — an adapter or the runner threw before the post went out. Recorded on the post's error, not returned from a request. Try again.
rate_limited429Over the per-minute limit. Sends limit and retryAfter, and the response carries Retry-After. As a post target's errorCode, it means the channel refused the post because of its own limit on this account (on YouTube, the channel's daily upload limit, with Google's sentence as the error). The files are kept for 7 days, and calling retry_post later sends the same files again.
account_not_found404No such connected account in this workspace.
account_has_pending_posts409DELETE /v1/accounts/:id found scheduled posts or drafts on that account. Sends pending with scheduledOnly (scheduled posts that go only to this account; disconnecting deletes them), scheduledShared (scheduled posts that also go to other accounts; they lose only this one), drafts (drafts that lose only this account), earliestScheduledAt, liveAutomations (enabled automations on that account) and conversations (inbox conversations on that account). Nothing was changed. Automations and conversations alone never cause this error: disconnecting keeps them, with contacts and messages, for 30 days, and reconnecting the same account to the same workspace within that time brings them back with live automations still on. To reauthorize the same account and keep the scheduled posts, reconnect it instead. Send force: true in the body, or ?force=true, to disconnect anyway.
account_disconnected409The account that published this post was disconnected. Reconnect the same account on Connections and the post id comes back. force does not override it. Edit, delete, retry, replies, hide, like and insights on that post answer this; nothing was changed. The post keeps its status, and its target shows connectionId null with accountHandle set to that account's handle.
post_unavailable404The channel (Threads, Instagram, YouTube or Naver Clip) no longer returns this post to the account that published it, most likely because it was deleted in that app. Replies and metrics cannot be read and retrying will not change it. delete_post clears our record. On an Instagram account connected with Instagram login, delete_post asks Instagram once more and clears our record without calling Instagram when the post is still gone. On YouTube, delete_post records the video as deleted without changing anything on YouTube, and editing an imported video that is gone answers this code with our record unchanged. The thread endpoint still returns the post with this code in repliesError, and insights answers 200 with current null and this sentence in note.
post_deleted409You already deleted this post with delete_post. Its replies and metrics are no longer read and nothing is sent to the channel. The thread endpoint still returns the post with this code in repliesError.
account_busy_publishing409A post is going out through that account right now. Sends retryAfterSeconds. force does not override it; wait for the publish to finish and disconnect again.
empty_reply422The reply had no text.
cannot_hide_own_reply400Threads does not let an account hide its own replies. Hiding works on other people's replies to your posts.
media_fields_required422presign needs fileName, contentType and bytes. When only bytes is missing or 0, reason is bytes_unknown and nextStep is media_upload_link (POST /v1/media/upload-sessions): a client that cannot read the file size cannot PUT it either. Over MCP the tool result then carries an upload link too.
not_our_post422retry_post on a post that was imported from the channel, not published through us: it is already on the channel, so there is nothing to retry. Editing an imported post answers post_not_editable instead when the channel cannot rewrite it.
key_name_required422Give the key a name.
key_scope_required422A key must reach at least one workspace. Pass workspaceIds, or allWorkspaces.
invalid_locale422locale must be en or ko.
url_required422Pass url: a public Naver Blog post link.
reference_invalid400That is not a link to one Naver Blog post. Use a form like https://blog.naver.com/someone/224349824125.
reference_not_naver400Only blog.naver.com links can be read as a reference. We do not fetch arbitrary hosts.
reference_not_public400That post is private or gone. Only public posts can be used as a reference.
reference_not_readable400That page is not a SmartEditor post. Posts from older editors cannot be read.
reference_too_large400That post is too large to read.
reference_timeout503Naver did not answer in time. Try again.
reference_unreachable503Could not reach that post.
reference_not_read422 · 404That reference post has not been read yet. Read it with POST /v1/naver/forms/extract first; the saved form is what generation uses.
bad_post_ref422The post reference was not an id, a media id or a post link.
post_not_owned422That post belongs to an account this workspace has not connected.
post_not_in_recent422That post was not in the recent window we searched. Sends scanned, how many posts were read; the post's own id on the channel finds it instead.
upload_session_not_found404That upload link is gone or expired.
upload_session_full422That upload link reached its file limit, or its limit on upload attempts (retries of files that never finished count as attempts). Ask for a new link.
media_url_invalid422Not an https URL.
media_url_blocked422That address is private, loopback or link-local.
media_url_unreachable422The host did not answer, redirected too many times, or answered with an error. When the host sent a short error sentence, the message carries it (for example Wikimedia's "Use thumbnail sizes listed on https://w.wiki/GHai"). A Wikimedia thumbnail at a width Wikimedia does not serve is fetched once more at the largest standard width below it, and a 429 with a Retry-After of a few seconds is retried once after waiting. When the connection does not open or no response comes back, and the host has more than one address, the fetch is tried once more on the next address.
workspace_required400This account has more than one workspace and the request did not say which. Sends workspaces, each with id, name, slug and channels, so you can match what the person said without extra calls. Pass the x-uplika-workspace header, or the workspaceId argument on MCP tools. The same code comes back when the x-uplika-workspace header names a workspace that is not on this account, is outside the API key's scope, or was deleted. The message then says so, and workspaces lists the ones this request can use.
workspace_mismatch404The post, channel, or media is in a different workspace on the same account. Sends workspaces. Retry there instead of connecting the account again.
workspace_limit403The plan includes fewer workspaces than this account already has. Sends used and limit. Workspaces are the billing unit, so the fix is a larger plan, not a retry.
platform_already_connected409This workspace already has a channel on that platform, and a workspace holds one per platform. Sends platform, existingHandle, incomingHandle and existingExpired. When existingExpired is true, a reconnect came back signed in as a different account: have the person log in to the channel as the original account and reconnect, which deletes nothing. Otherwise connect the other account in another workspace. Disconnecting the existing one deletes its automations, conversations and scheduled posts. Reconnecting the same account is not affected.
quota_exceeded402The free plan allows a fixed number of posts a month and this workspace used them all. Publishing is blocked until the next period starts, which is a month from the signup date, not the first of the calendar month. Upgrade to remove the limit. A thread counts as one post, not one per item.
workspaces_invalid422The checkout asked for fewer workspaces than a paid plan includes, or for something that is not a whole number. Send the total number of workspaces you want, not the number of extra ones.
billing_not_configured503Billing is not switched on for this deployment. Nothing to buy yet.
full_access_open409Every feature is currently open to all users, so there is nothing to buy. Try again once plans are switched on.
checkout_failed503The payment provider did not return a checkout. Nothing was charged. Try again.
no_subscription422There is no paid subscription on this account, so there is no billing portal to open.
portal_failed503The payment provider did not return a billing portal link. Try again.
youtube_title_required422A YouTube target needs options.youtube.title.
youtube_title_too_long422The title is over 100 characters. Sends limit and actual.
youtube_angle_brackets422YouTube refuses < and > in the title and the description.
youtube_video_required422YouTube takes exactly one video. Sends limit and actual.
youtube_tags_too_long422Tags are over 500 characters in total. YouTube counts a comma between tags and two quote marks around any tag that contains a space. Sends limit and actual.
youtube_schedule_needs_private422options.youtube.publishAt only works while privacyStatus is private.
youtube_schedule_invalid422options.youtube.publishAt was not an ISO 8601 timestamp.
youtube_thumbnail_type422A thumbnail must be image/jpeg or image/png.
youtube_thumbnail_too_large422A thumbnail can be up to 2MB. Sends limit and actual.
youtube_short_no_thumbnail422A vertical video of three minutes or less publishes as a Short, and Shorts do not take custom thumbnails. Drop the thumbnail or change the video.
youtube_no_threads422threadItems with a YouTube account would upload one video per item. Publish the video on its own.
instagram_reel_video_required422An Instagram reel needs exactly one video and nothing else. Sends limit and actual.
instagram_reel_duration422The reel is outside 3-900 seconds. Sends limit (the bound it broke) and actual in seconds, to one decimal and rounded away from that bound.
instagram_story_single_media422An Instagram story takes exactly one image or video. Sends limit and actual.
instagram_story_no_extras422Stories do not take a first comment or collaborators.
instagram_story_duration422The story video is outside 3-60 seconds. Sends limit (the bound it broke) and actual in seconds, to one decimal and rounded away from that bound.
instagram_cover_reel_only422options.instagram.coverMediaId only applies to a reel.
instagram_trial_reel_only422options.instagram.trialReel was set on a post that would not go out as a reel (a photo, a carousel, a story, or contentType feed). Trial reels are reels only.
instagram_trial_reel_invalid422options.instagram.trialReel is not "performance" or "manual". Uplika refuses it instead of dropping it, because a dropped value would post a normal reel to every follower.
instagram_cover_type422A reel cover must be JPEG, PNG or WebP; Uplika sends Instagram a JPEG. Sends types.
instagram_cover_too_large422A reel cover can be up to 8MB (the uploaded file). Sends limit, limitMb and actual.
instagram_too_many_collaborators422Instagram takes up to 3 collaborators. Sends limit and actual.
instagram_user_tag_position422A user tag on a photo needs x and y between 0 and 1.
instagram_username_invalid422An entry of options.instagram.collaborators, or a username in options.instagram.userTags, is not shaped like an Instagram username: letters, digits, dots and underscores, 1 to 30 characters, without @. The message names the field (for example options.instagram.collaborators[0]) and its value. Nothing was created. Whether the account exists, is public and is a professional account is checked by Instagram when the post goes out; see instagram_collaborator_unavailable.
instagram_audio_invalid422options.instagram.audio is not the right shape: id must be an audio id from search_instagram_audio (digits only), and volume and videoVolume whole numbers from 0 to 100. Instagram itself does not check the volumes, so we do. The message names the field. Nothing was created.
instagram_audio_reel_only422options.instagram.audio was set on a post that would not go out as a reel (a photo, a carousel, a story, or contentType feed). Instagram takes audio on reels only. Also set as a post target's errorCode if that happens when the post goes out.
instagram_audio_needs_facebook_login422options.instagram.audio was set for an Instagram account connected with Instagram login. Instagram offers audio only to accounts connected via Facebook: choose Reconnect through Facebook in the account's menu on the Connections page (its scheduled posts and automations stay), or publish without audio. The message starts with the reason list_platforms gives for feature audio. Also set as a post target's errorCode if the account was reconnected with Instagram login after the post was scheduled.
instagram_audio_unavailable422Instagram has no audio with that id for this account (checked before the post is created, so nothing was created), or Instagram refused the audio when the reel was created; then it is the target's errorCode and retryable is false. Search again with search_instagram_audio and use an id from the same account's results, then publish again; retry_post would send the same audio and fail the same way.
instagram_feed_video_unsupported422contentType feed with a single video (after fitting). Instagram has no single-video feed post: use reel or story, or attach photos. Also set as a post target's errorCode if a post scheduled before this check goes out.
facebook_link_with_media422A Facebook link post cannot carry media. Drop the link or the files.
facebook_link_invalid422options.facebook.link must be an http(s) URL, and not a Facebook share link (facebook.com/share/…): Facebook does not take those in a link post.
facebook_reel_video_required422A Facebook reel needs exactly one video and nothing else. Sends limit and actual.
facebook_reel_duration422The reel is outside 3-90 seconds. Sends limit (the bound it broke) and actual in seconds, to one decimal and rounded away from that bound.
facebook_story_single_media422A Facebook story takes exactly one image or video. Sends limit and actual.
facebook_story_no_extras422Facebook stories do not take a first comment.
facebook_story_no_caption422Facebook stories do not show a caption. Drop the text, or publish as a feed post.
facebook_story_duration422The story video is outside 3-60 seconds. Sends limit (the bound it broke) and actual in seconds, to one decimal and rounded away from that bound.
facebook_feed_video_unsupported422contentType feed with a video. Uplika does not post videos to the Facebook feed yet: use reel (vertical) or story, or remove the video. Also set as a post target's errorCode if a post scheduled before this check goes out.
facebook_schedule_feed_only422Scheduling works on Facebook feed posts only, not reels or stories.
facebook_schedule_invalid422options.facebook.scheduledPublishTime was not an ISO 8601 timestamp.
facebook_schedule_range422A scheduled Facebook post must be 10 minutes to 28 days from now.
facebook_targeting_text_only422options.facebook.feedTargeting works on Facebook text and link posts only. Facebook takes it on photo posts and reels but does not keep it.
facebook_targeting_not_editable422options.facebook.feedTargeting cannot be changed after the post is published. Leave it out to edit the text, or delete the post and publish it again.
facebook_schedule_no_first_comment422A scheduled Facebook post cannot carry a first comment — the post is not live yet, so the comment has nowhere to attach and we are not called back at publish time. Publish now, or add the comment after it goes live.
threads_not_supported422threadItems aimed at a channel that does not chain: replies there are comments or do not exist. Only Threads, Bluesky and X take a chain. Publish one post, or send threadItems to those separately.
beta_access_required403That channel is in beta and this workspace has not been approved for it yet. Request access from the dashboard. Retrying will not help.
naver_title_required422Naver Blog needs options.naver_blog.title.
naver_title_too_long422Naver Blog title over the limit. Sends limit and actual.
naver_category_required422Naver Blog needs options.naver_blog.categoryId or options.naver_blog.category (the name). list_accounts returns the blog's categories under naverBlog.categories; there is no default. Not required when draftOnly is true.
pinterest_board_required400Pinterest needs a board. options.pinterest.boardId was not given and the connection has no default board. list_accounts returns the boards under pinterest.boards; pass one, or set a default with PUT /v1/accounts/:id/pinterest/default-board. Nothing was created.
pinterest_board_not_found400 | targetThe board is not one this Pinterest connection can pin to. As a 400 from PUT /v1/accounts/:id/pinterest/default-board: the id is not in the stored board list; call POST /v1/accounts/:id/refresh first if the board was made after connecting. On a target's errorCode: Pinterest answered 404 for the board when the Pin was created (deleted or made secret). Pick another board and publish again.
pinterest_link_invalid422options.pinterest.link is not an https:// address. Pinterest opens it when someone taps the Pin. Nothing was created.
pinterest_link_too_long422options.pinterest.link is over 2,048 characters. Sends limit and actual. Nothing was created.
pinterest_title_too_long422options.pinterest.title is over 100 characters. Pinterest counts a title in code points, so an emoji is one. Sends limit and actual. Nothing was created.
pinterest_alt_text_too_long422options.pinterest.altText is over 500 characters, counted in code points. Sends limit and actual. Nothing was created. Alt text saved on the media is cut to 500 instead.
pinterest_video_too_short422Pinterest takes videos of 4 seconds or longer. Sends limit and actual in seconds; actual has one decimal and is rounded down, so it is always below limit. Nothing was created.
pinterest_link_blockedtargetPinterest would not save the Pin because of its link: it blocked the site the link points to. It arrives as HTTP 429 with code 9, but it is not a rate limit. retryable is false: the same Pin gets the same answer, and other Pins linking to the same site usually do too. Change options.pinterest.link to another address or remove it, then publish a new post. A Pin with no link that gets the same answer fails with platform_rejected_content.
x_credits_insufficient402 | targetThe X credit balance cannot cover this call. X posts, deletes and insights are paid from X credits bought in advance, and uplika holds the cost before it calls X, so nothing was sent to X. The 402 body carries topUpUrl: pass it to the person to top up, then send again. Connecting an X account with too little balance comes back as connect_error=x_credits_insufficient, and a scheduled post that runs short fails with this code without a retry. When a later part of a thread runs short, parts already up stay up: top up, then call retry_post, which continues from that part, and do not send the whole chain again.
x_duplicate_across_accounts422Another X account of the same person posted the same text in the last 24 hours. X's rules forbid the same or nearly the same post on several accounts, and a breach blocks uplika's X app for everyone. Change the text for this account. Nothing was sent and nothing was charged.
x_poll_invalid422options.x.poll does not fit X's rules: 2 to 4 choices of up to 25 characters each (counted as the characters you see, so one emoji is one), and durationMinutes a whole number from 5 to 10080. Choices past the fourth are not cut off, blank choices are not dropped, and the minutes are not rounded: the request is refused and nothing was created. durationMinutes may be a number or a string of digits. options.x is checked whenever it is sent, even when no X account is picked, so a draft cannot keep a poll that X would refuse later. Fix the poll and send it again.
x_poll_with_media422options.x.poll came with photos or a video. X does not allow a poll and media on the same post. Nothing was created. Remove the media, or leave out the poll and post it on its own.
platform_unavailabletargetThe channel could not take the post right now, so nothing was published: it answered with a server error or stopped answering while the files were going up, or it returned a server error or stopped answering when uplika renewed the connection's sign-in just before sending, or it is not taking posts from uplika for a while, or TikTok returned a server error or did not answer when uplika checked, just before sending, that the creator can post, or Instagram answered the publish that the media was not ready yet (code 9007, subcode 2207027) and it did not go out within uplika's short wait of up to about 30 seconds, or Instagram did not answer (code 2) while uplika was preparing the post, or did not answer the publish and uplika did not find the post among the account's latest posts. Pinterest also lands here when it answered that the problem was on its side (code 2787), or did not save the Pin this time ("This site doesn't allow you to save Pins"), and uplika did not find the Pin among the board's Pins when it checked afterwards. Recorded on the target's errorCode; retry_post sends the same text and files again.
x_publish_unknowntargetThe post was sent to X and then X stopped answering or answered with a server error, so it is not known whether it went up. The post may already be on X. Recorded on the target's errorCode with retryable false; retry_post answers 409 with this code until the call carries force: true. Check the X account first, and pass force: true only if the post is not there; retrying without checking can post it twice.
tiktok_publish_unknowntargetThe publish request was sent to TikTok and then the connection dropped before TikTok answered, so it is not known whether TikTok took it. The post may already be on TikTok, or in the TikTok inbox for a draft. Recorded on the target's errorCode with retryable false; retry_post answers 409 with this code until the call carries force: true. Check the TikTok profile (or the TikTok app's notifications for a draft) first, and pass force: true only if the post is not there; TikTok has no delete API, so a second copy has to be removed in the app.
x_analytics_not_enabled200 noteCodeget_insights on an X post whose connection has insights switched off. Each X metrics read is paid from X credits, so insights are switched on per X connection by the person on the Connections page. The answer is 200 with noteCode x_analytics_not_enabled and no numbers, and nothing was charged.
linkedin_link_with_media422options.linkedin.link was given together with files. A LinkedIn link card carries no image or video, so send the link or the files, not both. Nothing was created.
linkedin_link_invalid422options.linkedin.link is not a full https:// address. Nothing was created.
linkedin_link_title_required422A link card needs options.linkedin.linkTitle. LinkedIn does not read the page behind the link, so the card shows only the title (and optional linkDescription) you send. Nothing was created.
linkedin_link_field_too_long422options.linkedin.link is over 2,048 characters, linkTitle over 200 or linkDescription over 300, counted in code points. The message names the field. Sends limit and actual. Nothing was created.
linkedin_video_too_short422LinkedIn takes videos of 3 seconds or longer. Sends limit and actual in seconds; actual has one decimal and is rounded down, so it is always below limit. Nothing was created.
discord_username_invalid422options.discord.username contains "discord" or "clyde" (any case). Discord refuses those sender names. Pick another name or leave it out to use the webhook's own name. Nothing was sent.
discord_field_not_editable422PATCH /v1/posts/:id on a posted Discord message tried to change what Discord only takes when a message is sent: mediaIds (attachments), options.discord.username or options.discord.silent. field names which. Leave them out, or resend the same values, to edit the text, mentions or link previews; or delete the post and publish it again.
naver_clip_field_not_editable422PATCH /v1/posts/:id on a posted Naver Clip tried to change what an edit in Naver Clip Creators cannot: a new id in mediaIds (the video), options.naver_clip.draftOnly, a different options.naver_clip.coverMediaId or a different options.naver_clip.contentLink. field names which (video, draftOnly, cover or contentLink). Leave them out, or resend the same values, to edit the description, tags, category, visibility or comment setting; publish a new video as a new clip. Nothing was changed.
discord_forum_channeltargetThe Discord webhook belongs to a forum or media channel, which needs a new thread for every message. Uplika posts to regular text channels only. Create a webhook in a text channel, reconnect with it, and publish again. retryable is false.
naver_markdown_unknown422The Naver Blog body breaks the grammar: an unknown directive or {.attribute}, an attribute in the wrong place or with a bad value, an unclosed code fence, a @group with too few or too many images, and so on. Each item carries line (1-based), grammar.reason (the rule id) and grammar.params (the values in the message); the message is English and names the line. Nothing was published.
naver_category_unknown422options.naver_blog.category names a category the connected blog does not have. The response lists the blog's categories; pick one of those or call refresh_account if it was just created.
naver_category_ambiguous422options.naver_blog.category matches more than one category of the connected blog (a parent and a subcategory can have the same name). Nothing was published. The response lists the blog's categories with their ids; pass options.naver_blog.categoryId instead.
naver_form_unknown422options.naver_blog.form (or the forms argument of /v1/naver/layout) names a preset that does not exist. The message lists the ids; GET /v1/naver/forms describes them.
naver_form_required400Publishing to Naver Blog when nobody has picked a form yet. The error carries forms (id, name, when): show them, then publish again with options.naver_blog.form set, or pass options.naver_blog.layout: "as-is" to publish the markdown unchanged. The choice is remembered per workspace, so this is asked once.
content_required422POST /v1/naver/layout without content. Pass the markdown body.
help_not_found404GET /v1/help with an id that is not a question. Call it without arguments for the list.
invalid_locale400GET /v1/help with a locale other than en or ko.
invalid_category400GET /v1/help with a category it does not have. The message lists them.
invalid_topic400GET /v1/naver/grammar with a topic we do not know. The message lists the ids, and topics carries them as an array.
naver_wrong_blog400The Naver Blog link points at a different blog than the one connected here. We only touch posts on the connected blog. Over REST the body also carries ownerHandle and externalId for POST /v1/engagement/reply or /v1/engagement/like.
naver_wrong_login400The browser running the extension was signed in to a different Naver account than the blog this post was for, so nothing was written to Naver. Log in with the account that owns that blog. When the job is sent again and Naver asks for a login, the extension opens the Naver login window and names the account it needs.
naver_session_permission400Multi-account switching is on in the extension but its cookies permission was revoked. Open the uplika extension popup in that browser and turn it on again.
naver_rate_limited429Naver is limiting how often this blog can publish. This is Naver's own per-account limit, not ours, and it clears with time. The post may have been kept as a draft in Naver (a scheduled post that was due while the cap was still on is not sent at all and leaves no draft), so check there before publishing again later.
naver_not_allowed400Naver does not accept that action from this account. Liking your own post is the known case: the click is silently ignored, so we report it instead of pretending. Nothing was changed.
naver_follow_group_missing400You named a neighbor group (group) that this blog does not have, so nothing was clicked and no one was added. Uplika does not create groups: use a group you made on Naver, spelled as it appears, or leave group out. Trying again does the same thing.
naver_follow_blocked400That blog does not accept neighbor requests, Naver refused this one, or the neighbor group on this account that it was going into is full (make room in that group first). Trying again does the same thing until that changes.
naver_engagement_limited429Naver is limiting this blog's neighbor adds for today: the add-neighbor page kept coming back blank on the same day with no successful add in between, or Naver showed its own notice that this blog reached the number of neighbors it can add in a day. Uplika sets no limit of its own; this is Naver's. No more neighbor adds go out from that blog until midnight Korea time, and automations that add neighbors rest for the day. retryAfterSeconds is the time to midnight KST and until is that moment. A single blank page with no notice on it is naver_tab_lost instead, and sending it once more is safe.
naver_comment_gone404The comment you are replying to or liking is no longer on the post; it was deleted (the extension saw it marked deleted). Trying again does the same thing. Nothing was written to Naver.
naver_comment_not_found404The comment you are replying to or liking was not found on the post, so nothing was written to Naver. It may have been deleted, or it may sit on a part of a long comment list the extension did not open. Sending the same request again does the same thing; check the comment on the blog first.
upload_stalled503uplika could not finish sending the video to the channel: a YouTube resumable upload stopped moving for 30 minutes, or ran past 6 hours. Nothing was published. This is on our side, so retry_post is safe, and the video file is kept for 7 days. Recorded on the target's errorCode, not returned from a request.
platform_timeout503The channel did not answer in time: a container that never became ready, or a connection to the channel that never opened. Nothing was published. Try again. Recorded on the target's errorCode, not returned from a request.
naver_draft_unpublished400The post is a Naver draft (temp save). It has no views or comments until it is published, and it cannot be edited or deleted as a post. Publish it with publish_naver_draft (POST /v1/naver/drafts/{logNo}/publish).
naver_stats_unavailable400Naver's view stats have nothing for this post: it may be private, just published, or not on this blog. Trying again does the same thing; the other metrics and the stored history still come back.
naver_stats_permission403The uplika browser extension that is on does not have the Naver permission it needs to read view counts, so no view count was read. Ask the person to turn on the Naver permission in the extension (connecting Naver Blog once in that browser grants it), or to open the browser where it is already on.
naver_stats_unreachable400The browser extension could not reach Naver's view stats, so the view count was not read. This is usually temporary; check again in a moment.
naver_comments_closed400The Naver post is private or has comments turned off, so there are no comments to read or reply to. This is the post's state, not a failure.
naver_post_unavailable404Naver did not open that number as a post: it was deleted, is a draft, is scheduled, or belongs to another blog. Nothing was deleted and our record is unchanged. A record imported from that number in the same call is removed. On update_post this is also the code when Naver sent the edit screen to the blog's post list instead of opening the post; the target stays published with this code and a warning, and calling update_post again does the same thing.
naver_card_unavailable400The link card window did not open in the Naver editor, or putting the card in did not finish in time (the preview was slow or the page stopped answering). Sending the post again usually works. To post without a card, put the address on its own line instead of @card(…). A half-finished Naver draft may have been left.
naver_card_not_inserted400Naver took the address in the link card window but did not make a card from it; YouTube video addresses do this because Naver puts a video embed there instead. Nothing went out and sending it again gives the same result, so retryable is false: write the address on its own line or as [text](address) instead of @card(…). A half-finished Naver draft may have been left; list_naver_drafts shows it. Uplika already sends @card with a YouTube video address as a plain link and says so in the target warning.
naver_tab_lost400The Naver window closed, moved to another page or stopped answering before the publish button, or the editor did not load in time. Nothing went out (an edit leaves the post unchanged), so sending it again is safe. If it stopped while photos, videos, link cards or blocks were being put in, a half-finished Naver draft may have been left; list_naver_drafts shows it. This covers the Naver Clip Creators window too: a clip that stopped while its video was uploading may leave a half-uploaded video in the drafts of the Clip Creators content list, which list_naver_drafts does not show. For a reply it stopped before the reply was written, so no reply went out. Before an edit of a post written in Naver's editor, it also means the extension could not open Naver's publish panel to read the post's category, visibility and tags; sending the update again reads the post afresh. Uplika closes the Naver window it opened by itself when it is done; closing it partway stops the post.
naver_draft_unknown409The extension went quiet right after pressing Save as draft (the window closed, the page stopped answering, or the browser went away), so the draft may or may not be in Naver's draft list. Uplika looks in Naver's draft list first and recovers the draft when it is there; this code is what is left when the draft was not found or the list could not be read. Recorded on the target's errorCode with retryable false; retry_post answers 409 with this code until the call carries force: true. Check list_naver_drafts first; retrying without checking can leave two drafts.
naver_reply_unknown400A Naver reply step did not confirm in time (the reply command timed out, the page stopped answering, or the reply did not show up after it was submitted), so the reply may already be on the blog: in the post's comments for a comment on the post, or under the comment for a reply to a comment. Look there on the blog first (a secret reply shows only to the blog owner's login; list_replies may not show nested or secret replies). On a reply to our own post it stays on the target's errorCode with retryable false, and retry_post answers 409 with this code until the call carries force: true. On a reply to someone else's post, an inbox answer or an automation reply it comes back as 400. Sending it again without checking can post the reply twice.
naver_publish_unconfirmedtargetThe publish step in Naver did not confirm in time (the publish or confirm command timed out, or the page stopped answering after the confirm button may have been pressed), so whether the post went out is not known. For an edit, open the post; if it did not change, call update_post once more; sending an edit again does not make a second post. For a new post Uplika has already checked the blog's post list and the post is not there; a half-finished Naver draft may have been left, so check list_naver_drafts and send it again. retryable is true. A timeout while the publish panel was still being prepared is naver_publish_failed, not this code.
comments_closed400This post is not taking comments right now: a YouTube video whose comments were turned off, one set as made for kids (YouTube keeps comments off on those), or a private video (a scheduled video stays private until its publish time). Reading replies on a video with comments turned off answers 400 with this code. A reply YouTube refuses on such a video closes its target as failed with this errorCode and retryable false; that includes a comment on a video refused with 403 forbidden and no reason, which most often means the video is private or scheduled. This is the post's state, not a problem with the text, so sending it again gives the same result until the video's state changes; the account does not need reconnecting.
refresh_unsupported400This channel has nothing to refresh; its metadata comes from the platform on every call.
invalid_params400A request field is missing or the wrong shape. The message names it; problems lists each field when there are several. From an MCP tool whose path argument (an id, token or logNo) is empty, missing lists the required arguments still to fill and received lists the argument names that arrived, without their values. A tool that sends or changes something does nothing when it gets an argument name outside its schema: unknown lists those names and the message lists the names the tool takes. publish and update_post also refuse an options key the channel does not take, naming it in unknown as options.channel.key. REST PATCH /v1/automations/{id} also refuses a field it does not take, listing it in unknown.
quota_exceeded429A daily research quota is used up: 60 judge calls, 600 measured keywords (neighbor candidate searches use this quota too) or 20 blog diagnoses per person. Sends what (seeds, measured, diagnoses) and limit. Cached keywords and cached diagnoses do not count, and measurements that never reached Naver are refunded. Keyword expansion has no daily quota.
naver_seo_unavailable503Keyword research is not configured on this server (no Search Ad or API HUB keys). Type keywords by hand; the SEO check still works.
naver_api_error503Naver Search Ad or API HUB did not answer or refused our credentials. Try again later.
invalid_blog_id400blog is missing or is not a Naver blog id: 2-40 letters, digits, - or _, or a link to blog.naver.com that carries one. Nothing was fetched.
blog_not_found404No public Naver blog has that id, or it has no public posts. Naver answers an empty feed for unknown ids, so this is the same as a redirect away from the feed.
naver_rss_unreachable503The blog's RSS feed could not be read. The feed is read by the person's uplika browser extension when one is connected and new enough; our server cannot read Naver's feeds right now, so without a connected extension this fails. bridge, when present, says why the extension was not used: offline (paired false: no browser is connected, so ask the person to connect Naver Blog on the Connections page; paired true: that browser is off, and wake carries per-OS commands that open it if you have a shell on that computer), outdated (with installedVersion, requiredVersion, publishedVersion and awaitingRelease; when awaitingRelease is true the version is not on the store yet, so do not ask the person to update) or resting (retryAfterSeconds). If the extension read the feed and Naver answered an error, the message says which. Nothing is cached from a failed read.
naver_autocomplete_unavailable503Neither path could run: the person's uplika Chrome extension is not on (or cannot reach Naver autocomplete yet), and server-side autocomplete is switched off. Nothing was sent to Naver. Pass your own keyword list to judge or research_naver_keywords instead.
naver_autocomplete_paused429Naver started refusing our autocomplete calls, so the server is pausing them for everyone (5 minutes, doubling on repeat, up to an hour). Sends retryAfterSeconds and a Retry-After header. Pass your own keyword list meanwhile.
naver_autocomplete_busy429Autocomplete cannot take this call right now: the queue is too deep, an expansion is already running for you, our server already ran one for you in the last 60 seconds, our daily cap is used up, or your recent seeds all came back empty. The message says which. Sends retryAfterSeconds and a Retry-After header. The 60-second spacing applies only when our server answers; the person's uplika Chrome extension has none.
research_tool_disabled403Only for a research tool still in beta: the person has turned it off for MCP connectors and API keys (the screen always works). Released research tools have no switch and never answer this. Sends tool and enableUrl, the research screen with its details sheet open. Tell the person to open that link and turn it on, then say so; retrying before that returns the same error.
research_tool_not_toggleable409PUT /v1/research/tools/:id/agent on a research tool that is out of beta. Released research tools are always available to connectors and API keys, so there is nothing to turn on or off; the switch exists only while a tool is in beta.
research_quota_exceeded429A daily research quota is used up. Sends kind (for example youtube_searches) and limit. Cached searches do not count; the quota resets at the UTC day change.
youtube_quota_exhausted429Uplika's daily YouTube allowance, which everyone on Uplika shares, is used up. Search (YouTube research) and publishing run on separate Google projects, so one can run out while the other still works. On the publishing side it also answers reads, edits, deletes and link lookups, and a YouTube connection that cannot start sends connect_error=youtube_quota instead. Sends resetsAt, retryAfterSeconds and scope (all, or uploads when only new uploads are blocked), with a Retry-After header. It is not the person's Google account, and reconnecting does not help. Cached searches still answer; everything else waits for midnight Pacific time.
youtube_search_unavailable503YouTube search is not configured on this server (no YouTube Data API key). Nothing was sent to Google.
google_keywords_unavailable503Google keyword data cannot be read right now: the server has no Google Ads credentials, Google refused them, or Google failed or timed out. Try again later.
google_keywords_busy429Google keyword data is busy: the shared daily allowance or the queue is full, or Google asked us to slow down. Sends retryAfterSeconds and a Retry-After header.
ad_search_quota_exhausted429The person's daily ad searches are used up. Meta and Google ad searches share this one daily count. Sends kind (ad_searches), limit, used and resetsAt (midnight UTC). Cached searches, the saved history and transcripts already saved still answer.
ad_search_busy429Uplika's shared daily allowance for the ad data provider (Meta and Google ad searches alike) is used up. Sends resetsAt (midnight Pacific time) and a Retry-After header. Nothing is wrong with the person's account.
ad_search_unavailable503Ads cannot be read right now (Meta or Google ad search): this server has no provider key, the provider failed or timed out, refused the key or has no credit left, or it has been answering empty results in a row and is suspected broken. Nothing was charged to the person's daily searches. Try again later.
naver_search_busy429A Naver search check cannot start now: one is already running for this person (only one runs at a time; reason running, runId), or the daily allowance of Naver search pages is used up (reason daily_limit, limit, used). Sends retryAfterSeconds and a Retry-After header. Results already read are kept and come back from get_naver_visibility; calling check_naver_visibility again with the same keywords as the running check returns that check instead of starting another.
naver_search_blocked429Naver kept refusing search pages from the person's browser, so uplika is resting that browser for 10 minutes. Sends retryAfterSeconds and a Retry-After header. Only this person's browser is affected; results already read are kept.
naver_search_permission403The person's uplika Chrome extension is connected but does not have permission to reach Naver search. Ask the person to turn on the Naver permission in the extension (connecting Naver Blog once grants it). Nothing was searched.
naver_seo_busy429Our own daily cap for Naver Search Ad or API HUB calls is used up (it protects the shared credentials, separate from your personal quota). Sends service, retryAfterSeconds and a Retry-After header; the cap resets at the UTC day change.
refresh_timeout202refresh_account is still waiting for the browser extension after a minute. Not an error: the refresh keeps running. Call list_accounts again shortly.
refresh_failed503The browser extension could not re-read the blog. bridgeCode carries the extension's reason. Open blog.naver.com in that browser and try again.
naver_reply_media_not_supported422A reply to a Naver Blog post carried media, either in mediaIds or through a media: reference in the body. Naver comments are written into the comment box on the post page and take text only, so the media would be dropped without a trace. Publish it as its own post instead.
naver_too_many_tags422More than 30 tags. Sends limit and actual.
naver_tag_too_long422A tag over 30 characters. Sends limit.
naver_tag_has_space422Naver Blog tags cannot contain spaces. Join the words.
naver_scheduled_at_conflict422scheduledAt on the post and options.naver_blog.scheduledAt name different times. They mean the same thing (Uplika holds the post and sends it then); pass one of them.
naver_scheduled_at_mixed422options.naver_blog.scheduledAt on a post that also targets other channels. It now schedules the whole post on Uplika's side, so pass scheduledAt on the post to send every channel then, or publish the other channels separately.
naver_draft_and_schedule422options.naver_blog.draftOnly and options.naver_blog.scheduledAt cannot both be set. A Naver draft is not scheduled.
naver_font_size_out_of_range422options.naver_blog.fontSize must be 10-34.
naver_ui_changedtargetThe browser extension could not find or drive a control it expected in Naver's editor. Retrying will not help until the extension is updated. This fires from the pre-flight check when a control is really missing (an editor that was only slow to load is naver_tab_lost), which touches nothing, and also from mid-assembly, which can leave a half-built draft in Naver. A publish panel that closed before the confirm button was pressed is naver_publish_failed, not this code. Check the blog before assuming nothing happened.
naver_not_logged_intargetThe Naver login for that blog's account in the Chrome with the extension was signed out. While that blog is held, its posts are not failed but wait, and bridge.state is login_needed. The person presses Open login window on the Connections page and logs in to that account in the window that opens. Reads, and posts that waited 7 days, close with this code. A post that waited 7 days because the browser that has that blog's login was off also closes with this code; then turn that browser on, or press Open login window and log in to that blog in the browser that is on. After the login is back, retry_post.
naver_upload_failedtargetAn image, video or link card did not go into the editor. The extension tries to leave a Naver draft behind, but it does not report whether that worked, so treat the draft as likely and not certain. Open the blog before retry_post.
naver_publish_failedtargetThe editor was filled but Naver did not publish. The extension tries to leave a draft; that is likely, not certain. Check the blog before retry_post so it is not posted twice. Also used when the extension stopped before Naver's publish panel was ready (the prepare or tag-cleanup command timed out, the page stopped answering, or the browser went away during it), or when the panel did not open after the publish button was pressed: then the confirm button was never pressed, an edit left the post unchanged, and sending it again is safe. The message says which.
naver_verify_failedtargetThe job came back done without a post id, so we cannot confirm anything went live. The target is marked failed. Open the blog and look before retrying: a post may exist even though we could not read it back.
bridge_unsupportedtargetThe extension cannot handle this job, usually a file too large to hand to the editor. Retrying will not help.
bridge_losttargetThe browser extension went away mid-job. A draft may exist in Naver. Check it before retry_post. When it went away during the publish step, Uplika checks the blog's post list first: a post found there is recorded as published, and this code means it was not there (the publish button may not have been pressed).
bridge_stalledtargetThe extension stayed connected but the job stopped making progress. A draft may exist in Naver. Check it before retry_post.
bridge_timeouttargetNo browser extension came online within 7 days, so the queued post expired. retry_post once the browser is open.
naver_category_missingtargetThe category chosen for this post (options.naver_blog.categoryId) is not on this blog, so the publish panel could not select it and nothing went out. Pick a category this blog has (list_accounts shows them) and send it again. retryable is false.
naver_grammar_rejectedtargetThe extension's parser rejected one line of the Naver body (the message carries the line number and reason, for example an attribute this extension version does not know), so the post was not assembled and nothing went out. Fix that line and send it again; retry_post on its own does the same thing. retryable is false.
platform_activity_blockedtargetInstagram has temporarily restricted this account's activity (error code 4 with subcode 2207051). Unlike a plain app rate limit, waiting alone does not clear it: the person checks the notice in the Instagram app, and a retry fails until the restriction is lifted. retryable is false. The restriction can come back after the post already went up. When it comes back from the publish call, Uplika looks for the same post among the account's latest posts and, when it is there, records the target as published with a warning instead of this code. When this code stays, the post may still be on the account: check it before sending the post again.
facebook_identity_requiredtargetFacebook refused the post until the Facebook account that connected this Page confirms its identity (error 368 with subcode 4854002, "Confirm your identity before you can publish as this Page"). Changing the post does not help, and every post to that Page, scheduled ones included, fails the same way until the check is done in the Facebook app. The post's photos and videos are kept for 7 days. retryable is false; publish it again after the check.
facebook_post_unreachabletargetFacebook answered an in-place edit (update_post) or a comment on the post itself with error 100, subcode 33 ("Unsupported post request. Object with ID ... does not exist, cannot be loaded due to missing permissions, or does not support this operation"). Facebook keeps that post out of apps' reach: it may have been deleted or taken down, or it may still show on the Page, so we do not say it is gone. Nothing changed on Facebook and the same request fails the same way, so retryable is false. An edit keeps the target published with a warning that starts "The rewrite did not go through"; a comment ends failed. Check the post on the Page: if it is there, edit or comment in Facebook itself and do not publish it again; if it is gone, call delete_post to clear the record. list_replies answers 404 with the same code, and get_insights answers 200 with this code in noteCode, when Facebook gives the same error for reading a post (not a reel).
instagram_collaborator_unavailabletargetInstagram refused a collaborator or a tagged username when the post was created (error subcode 2207018): that username does not exist, is private, or is not a professional account. Nothing was posted. The error starts with our sentence and ends with "The channel said:" followed by Instagram's own words, which come in the connected account's language. Fix the name and publish again as a new post; retry_post would send the same names and fail the same way. retryable is false.
instagram_trial_reel_ineligibletargetInstagram refused options.instagram.trialReel for this account (error code 10, subcode 2207081, "Trial Reel Not Enough Followers"): the account does not meet Instagram's follower requirement for trial reels. Nothing was posted, and the connection is fine. The error starts with our sentence and ends with "The channel said:" followed by Instagram's own words. A normal reel goes to every follower, so ask the person before publishing the same media again as a new post without trialReel; the files are kept for 7 days. retry_post would send the trial setting again and fail the same way. retryable is false.
instagram_personal_accounttargetThe Instagram account was switched to a personal account (Instagram error code 10 saying the account type is not business or creator). Instagram only lets connected tools work with professional accounts, so nothing was posted. Switch the account back to a professional account (business or creator) in the Instagram app. The connection stays as it is, so there is no need to reconnect. Then send the same post again: the files are kept for 7 days, so retry_post works. retryable is false. While the account is personal, reading its posts and refresh_account answer the same name with a 403, and connecting a personal account comes back as connect_error=instagram_personal_account: switch it to a professional account first, then connect.
instagram_upload_failedtargetInstagram failed while processing the uploaded media and said only "Media upload has failed with error code N" (we have seen 2207082 and 2207085, which Meta's error table does not list). Nothing was posted, and the files are kept for 7 days. retryable is true. Call retry_post once. If the reel had audio and the video has no sound track of its own, Uplika sends options.instagram.audio.videoVolume 0 for it, the retry included. If it fails again with the same code, publish it as a new post: with audio, set videoVolume to 0, drop options.instagram.audio, or export the file again with a sound track; without audio, export the file again. Subcodes that point at the input (for example 2207026) stay platform_rejected_content.
instagram_publish_failedtargetInstagram answered the publish call with an internal error (code -1, subcode 2207085) after it had finished processing the media. Before closing the target, Uplika looks for the post among the account's latest posts; when it is there, the target is recorded as published with a warning instead of this code. When this code stays, the message says whether Uplika checked the list. retryable is true and the files are kept for 7 days. There is no automatic retry: call retry_post once, and if it fails the same way again on the same account, post it from the Instagram app. This is not instagram_upload_failed, which is Instagram failing while processing the media.
reply_parent_unavailabletargetThe channel no longer returns the post or comment this reply was for, most likely because it was deleted in the channel's app. Instagram sets it after reading the parent once to confirm it is gone; Threads sets it when it refuses to create the reply because it cannot find that post or comment. Nothing was posted. Sending it again or changing the text gives the same result, and retryable is false. Reply to a post or comment that is still there; if the post itself was deleted, delete_post on it clears our record.
youtube_daily_captargetThis YouTube target was closed by Uplika's shared daily YouTube limit (new uploads, or the allowance every YouTube request uses), whether it was scheduled or sent now; replies and edits close the same way. Nothing went out, and an edit leaves the video as it was. The limit resets at midnight Pacific time; retry_post after that. retryable is true.
youtube_channel_requiredtargetYouTube says the Google account behind this connection has no YouTube channel that can take uploads (a 401 "Unauthorized" with reason youtubeSignupRequired when the upload opens). Nothing was uploaded. The same name comes back as connect_error=youtube_channel_required when connecting YouTube finds no channel on the chosen Google account. Reconnecting the same Google account gives the same result: reconnect and pick the account that owns the channel (for a Brand Account, the channel itself), or finish creating the channel with that account. retryable is false. The video is kept for 7 days, so once the right channel is connected, retry_post sends the same video.
youtube_video_not_listedtargetAn edit of a YouTube video Uplika uploaded stopped because YouTube did not return the video when Uplika read it before writing. Nothing changed on the video and it keeps the privacy it had. A video that went up in the last few minutes is sometimes not listed in that read yet; wait a few minutes and call update_post again. Do not publish it again. If the video was deleted in YouTube Studio, call delete_post to clear the record. retryable is true.
youtube_language_rejectedtargetYouTube refused to open the upload for this target with a 400 that names no field (INVALID_REQUEST_METADATA), and options.youtube.defaultLanguage was set. The likely cause is that language code: YouTube takes language codes it knows, such as en-US or ko, and a country code such as US is not one. The video was not uploaded. The sentence is ours first, then the channel's own words after "The channel said:". Fix the code or leave it out and publish again as a new post; retry_post would send the same code. retryable is false.
thread_brokentargetAn earlier item of this chain did not go out on this account, so this item was never sent; the reason is on that earlier item. retry_post continues the chain from the item that failed, and items already up are not posted again. retryable is true. Recorded on the target's errorCode, not returned from a request.
naver_draft_overwrittentargetNaver saved a later post into this Naver Blog draft instead of starting a new draft, so the draft no longer holds this post. Uplika saw the later post's title on that draft number in Naver's draft list after the later post was picked up, gave the number to the later post, and closed this one. Also used when the draft is no longer in the blog's draft list: a publish of that draft number failed because Naver did not list it, and the extension had read the list. Nothing is deleted on Naver. retry_post saves it again as a new draft; retryable is true. Recorded on the target's errorCode, not returned from a request.
bridge_offline503A read or delete on Naver Blog, or a Naver search check, while the browser extension is offline. Nothing was queued. The extension is not answering: either its browser is closed, or the browser is open and the extension is turned off there (for example after an update or a permission prompt). Open the browser, or turn uplika on in its extension settings, then try again. The error detail of a Naver Blog read or delete carries bridge.wake: per-OS commands to open Chrome in the profile that has the extension, and a hint on what to call next. It is also this code when the browser that is on does not have that blog's Naver login and the browser that has it is off; then bridge.holderBrowser names that browser.
bridge_no_window503Naver Blog only: the browser with the extension is Edge and it refused to open a window because only its standalone sidebar is running. Nothing was opened on Naver. A read or a synchronous write answers 503 with this code; a publish, update or draft publish ends as a failed target with this errorCode and retryable false. Open an Edge browser window, then send it again.
bridge_window_unsupported503Naver Blog only: the browser with the extension does not let extensions open windows (ChatGPT Atlas works this way). Nothing was opened on Naver. For a publish, update or draft publish, when another browser with the extension holds the same Naver login and is on, Uplika hands the job to that browser once instead of failing. Otherwise a read or a synchronous write answers 503 with this code, and a publish, update or draft publish ends as a failed target with this errorCode and retryable false. Use the extension in Chrome, Edge or Whale, then send it again.
naver_clip_video_required422Naver Clip posts one video. Photos and text-only posts are not supported there; attach a video or publish to Naver Clip separately.
naver_clip_category_required422Naver Clip needs options.naver_clip.categoryId or options.naver_clip.category (the name). list_accounts returns them under naverClip.categories; there is no default. Not required when draftOnly is true.
naver_clip_category_unknown422options.naver_clip.category or categoryId is not one of the connected profile's Naver Clip categories. The response lists them; pick one, or call refresh_account if Naver changed the list.
naver_clip_category_ambiguous422options.naver_clip.category matches more than one Naver Clip category (the same second-level name under two first-level categories). Pass the full name like first › second, or categoryId. Nothing was published.
naver_clip_tag_invalid422A Naver Clip hashtag has a space, a symbol or an emoji. Naver Clip hashtags take letters, numbers and _ only.
naver_clip_cover_type422A Naver Clip cover (options.naver_clip.coverMediaId) must be JPEG or PNG, the two types the cover field takes. Sends types.
naver_clip_cover_too_large422A Naver Clip cover can be up to 9MB (the uploaded file). Sends limit, limitMb and actual.
naver_clip_too_many_tags422More than 5 hashtags, counting #words already in the description and options.naver_clip.tags together. Sends limit and actual.
naver_clip_description_too_short422The Naver Clip description, with options.naver_clip.tags appended as #tags, is shorter than minChars in GET /v1/platforms, counted in code points as minCharCount says (an emoji counts as one). Naver Clip refuses to post a shorter one and leaves it as a draft. Sends limit and actual. A draft (draftOnly), an edit and an empty description are not checked.
naver_clip_place_invalid422options.naver_clip.place or placeAddress has the wrong shape. reason says which: empty (blank text; uplika does not take a place off a clip), not_text, too_long (place is longer than the 40 characters the Naver Clip place search takes; limit has the number) or address_without_place (placeAddress without place). Pass the place's name as written on Naver Map, with words from its address in placeAddress when other places share the name. Nothing was published.
naver_clip_link_invalid422options.naver_clip.contentLink is not the address of a post on the blog of the same Naver account as the clip profile. reason says which: not_blog_post (another site, the blog's home page or not an address) or other_blog (a post on a different blog). Pass a post address from that blog, like https://blog.naver.com/<blogId>/<postNo>, or leave contentLink out. Nothing was published.
naver_clip_visibility_invalid422options.naver_clip.visibility is public or private. Any other value is refused rather than dropped, so a clip never goes out more public than asked. Nothing was published.
clip_no_profiletargetThe Naver account has no Naver Clip profile. The person creates one in Naver Clip Creators (clipcreators.naver.com) and connects Naver Clip again; uplika does not create it. Retrying will not help.
clip_profile_mismatchtargetThe connected Naver Clip profile is not on the Naver account signed in for that blog, so the extension stopped before uploading anything. Connect Naver Clip again. Retrying will not help.
clip_upload_failedtargetFetching, uploading or encoding the video, adding the content link or the place, or filling in the details, stopped before Post was pressed. The message names the step. Retry is fine; a half-uploaded video may be left as a draft in Clip Creators > Content.
clip_rejectedtargetNaver Clip Creators refused a value (for example the category) or the Post request itself; the message carries the page's own words or the HTTP status. Fix it and send it again. If a draft is left in Clip Creators > Content, you can also open it and press Post there. If the content link's post was not found in Naver Clip's blog search, nothing was uploaded; a post published in the last few minutes can take a few minutes to show up, so send it again a few minutes later with the same link; if the post is older, give it a unique title, pick another post, or leave the link out. Otherwise, retrying unchanged will not help.
published_as_imported_copytargetThe post is live on the channel. While it was going up, the same channel post was imported as a separate post, and that copy could not be merged back (an automation or another record points at it). Use the imported copy named in the target's error. retryable is false and retry_post answers 409 until force: true; send it again only after deleting it from the channel. The same content sent as a new post answers 409 duplicate_post for 10 minutes.
publish_outcome_unknowntargetPublishing stopped before the channel answered (for example the server restarted or went down in the middle of the call), and on this channel that call can already create the post, so it may be live. Instagram posts and Threads never get this code: their first call only prepares a container, so a stop there is recorded as nothing posted. Recorded on the target's errorCode with retryable false; retry_post answers 409 with this code until the call carries force: true. Check the channel first and pass force: true only if the post is not there. A retry is per post and force sends every failed target of it again, so if the post is there, publish the other channels as a new post instead.
clip_unconfirmedtargetPost was pressed but the clip did not show up in the clip list, or the page did not answer after Post. It may have gone up, so do not retry: check Clip Creators > Content first. retryable is false and retry_post answers 409 until force: true. The same content sent as a new post answers 409 duplicate_post for 10 minutes.
account_required400GET /v1/channels/publish-options or GET /v1/channels/instagram/audio was called without accountId. These values are per connected account, so there is no account-wide answer. A reply, hide, delete or like on a post that went to more than one channel answers it too when nothing says which channel's copy (accountId, a link to that copy, or whose comment it answers) or two of those disagree. Sends accounts [{ id, platform, handle }].
not_supported400The channel cannot do what you asked, and that is a fact about the channel rather than a failure to retry. Read GET /v1/platforms: each channel carries features, and a row with supported false says so ahead of time and carries the same sentence you get here. It comes back from publish-options (only TikTok has anything to look up), from the Instagram audio search for any other channel or for an Instagram account connected with Instagram login (feature audio is partial and this is its reason), replying to or reading the replies of a post on a channel whose API has no replies, liking or following on a channel where uplika does not offer it, and POST /v1/posts (also PATCH with options) whose options.x carries quoteTweetId, which is refused before any post is created even when no X account is picked, because uplika does not offer quote posts on X. A row with supported partial is refused the same way when the account does not meet its condition: liking from an Instagram account that was not connected through Facebook comes back with this code before the channel is called, and the message is that row's reason. DELETE /v1/posts/{id} on a post that went to several channels does the same when one of its accounts cannot delete there (an Instagram account connected through Instagram login, or a channel without a delete API): it refuses before calling any channel, deletes nothing, and the message ends with Nothing was deleted, unless that Instagram post is already gone from Instagram: then its record is cleared without a call and the other channels are deleted as usual.
reconsent_required409 · 422The connection was made before it was granted the permission this call needs, and connecting again can grant it. Sends accountId and missingScopes. Reconnect that account from the Connections page, then try again. POST /v1/posts answers it with 422 for an Instagram or Facebook account connected without the permission to publish, and the accountId says which account to reconnect or leave out. POST /v1/engagement/like answers it for an Instagram account connected through Facebook that lacks the like permission, and an automation with a mention trigger or a like step answers it for an account that lacks that permission; the body then also carries feature (like or mentions).
feature_in_review400The call needs a platform permission that is still in that platform's app review, and this connection does not hold it. Reconnecting does not help until the review passes, so do not retry and do not send the person to reconnect; everything else on the account keeps working. Sends feature, accountId and missingScopes. GET /v1/platforms shows the same thing ahead of time: the feature's row is supported partial with why app_review, and the message here starts with that row's reason. Accounts that already hold the permission are not refused. No feature is in review right now: liking on Instagram and Threads mentions passed Meta's review in October 2026, and a connection made without those permissions answers reconsent_required instead.
tiktok_privacy_requiredtargetoptions.tiktok.privacyLevel was missing. TikTok requires the person to choose visibility deliberately, so we have no default. This one is returned synchronously, before the post is created, so an agent can fix the call and send it again in the same turn. Call get_publish_options for the values this account may use.
tiktok_privacy_invalidtargetoptions.tiktok.privacyLevel is not one of the values this account may use right now. The allowed list differs per account and changes with the person's TikTok settings, so read it from get_publish_options rather than hard-coding.
tiktok_branded_privatetargetbrandContentToggle was set together with privacyLevel SELF_ONLY. TikTok does not allow branded content to be posted privately.
tiktok_interaction_disabledtargetdisableComment, disableDuet or disableStitch was set to false for something the creator turned off on their TikTok account. A post cannot re-enable it.
tiktok_title_requiredtargetA TikTok photo post needs options.tiktok.title, up to 90 characters. A video post has no title field and its text comes from content.
tiktok_title_too_longtargetoptions.tiktok.title is longer than 90 characters. TikTok counts a title in UTF-16 units, so an emoji outside the basic plane counts as two.
tiktok_title_not_supportedtargetoptions.tiktok.title was sent with a video. TikTok video posts have no title field, so the value would be dropped without a trace. The video's text comes from content.
tiktok_cannot_posttargetTikTok says this creator cannot post right now, usually a posting limit or a restriction on the account. We stop before sending anything, which is what TikTok's guidelines require. A server error or no answer from TikTok during this check is platform_unavailable, not this code. A rejected sign-in during this check is account_expired: reconnect the account.
tiktok_internal_errortargetTikTok had an internal error and did not post this: either its status check answered FAILED with fail_reason internal (TikTok documents it as a retryable error), or the first request failed with internal_error or another 5xx before TikTok accepted the post. Nothing was posted, and the files are kept for 7 days. retryable is true: retry_post once, and if the same code comes back, wait a while before trying again. Uplika does not retry it on its own, because TikTok has no way to delete a post that went up twice. A connection failure on our side is not this code.
tiktok_creator_captargetTikTok caps how many creators can publish through one app in a rolling 24 hours, and Uplika's cap was full (TikTok answers HTTP 403 reached_active_user_cap). The cap is for the whole app, not this account or post. TikTok answered before it accepted anything, so nothing was posted, and the files are kept for 7 days. At busy times the cap stays full for hours. retryable is true: call retry_post in a few hours. If it was a scheduled post sent on time, Uplika tries it again on its own every hour until 12 hours after the scheduled time, and a retry_post before then makes one try now and stops those tries. To have Uplika keep trying a post that was sent right away, publish it again to TikTok only with scheduledAt a few minutes ahead.
ghost_plan_limittargetGhost refused the Admin API key because the site's plan has no custom integrations (Ghost(Pro) Starter). The connection form answers with the same code. Upgrade to Publisher or use a self-hosted Ghost. retryable is false.
ghost_no_permissiontargetThe Ghost key is not allowed to do that (NoPermissionError). Reconnect with a custom integration's Admin API key or a staff token of a user who can publish. retryable is false.
ghost_update_collisiontargetupdate_post on a Ghost post met an edit made in Ghost Admin at the same moment, twice in a row (409 UpdateCollisionError). uplika does not overwrite it; close the post in the Ghost editor and send the edit again.
wordpress_app_passwords_unavailabletargetWordPress refused the application password because application passwords are turned off on the site or for that user (application_passwords_disabled). Turning them back on revives the same password. The connection form answers with the same code. retryable is false.
wordpress_blocked_by_hosttargetA firewall or security page in front of the WordPress site answered instead of WordPress (a refusal that is not WordPress JSON). The connection form answers with the same code. Allow REST API requests from uplika on the host or in the security plugin.
wordpress_publish_unconfirmedtargetWordPress did not answer the write in time and one lookup could not find a post with the exact title and body. The post may already be on the site. retryable is false and retry_post answers 409 until force: true. The same content sent as a new post answers 409 duplicate_post for 10 minutes. Check the site first.
wordpress_role_insufficienttargetThe connected WordPress user lacks a capability the call needs (rest_cannot_publish, rest_cannot_create, rest_cannot_edit or rest_cannot_delete), usually because its role was lowered. Give it Author or higher, or reconnect with such a user. The connection form answers with the same code. retryable is false.
wordpress_site_movedtargetThe WordPress site redirected the call to another address, so the stored site address is out of date. uplika does not follow redirects; reconnect with the new address. retryable is false.
wordpress_rest_unavailabletargetThe site does not answer the WordPress REST API routes uplika uses (404 rest_no_route), usually because a plugin or setting turned the REST API off. The connection form answers with the same code.
wordpress_upload_too_largetargetThe site refused a photo upload as too large (413, rest_upload_no_data, rest_upload_no_content_disposition, or the upload_max_filesize error). The host's upload limit is smaller than the size in GET /v1/platforms; use a smaller photo or raise the limit on the host.
wordpress_site_suspendedtargetWordPress.com has suspended or archived the site under its Terms of Service, so it does not take posts. uplika recognizes this from WordPress.com's own answer (connection_disabled), also when the write came back without the post. Only the site owner can get it lifted, through WordPress.com support. retryable is false; once the site is back, check it for the post before sending it again.
wordpress_tags_refusedtargetWordPress refused to attach the post's tags (403 rest_cannot_assign_term) on three sends. Before each resend uplika waited and looked the tag names up again one at a time, and the photos were uploaded only once. No post was created, so the same content can be sent again right away. Change or remove the tags; the user's role is not the cause, so there is no need to reconnect. retryable is false.
tiktok_reply_not_supportedtargetTikTok's public API has no way to reply to a post. Publishing a reply there would silently become a new post, so we refuse instead.
integration_not_connected404No Google Analytics property or Google Ads account is connected to this workspace. Sends connectUrl, where a person connects one.
integration_reconnect_required409Google ended this Analytics or Ads connection. Sends connectUrl; a person reconnects it there.
analytics_bad_request400Google rejected the report request, or uplika did before sending it. Sends reason, Google's own sentence when it came from Google, so you can fix a metric or dimension name.
analytics_no_access403The Google account that connected the property can no longer view it. The connection stays; it works again once someone gives the access back in Google Analytics.
analytics_quota_exhausted429The property's Analytics allowance is used up. Sends scope (hour or day), and resetAt for day.
analytics_upstream_unavailable503Google Analytics did not answer. Try again in a few minutes.
ad_budget_cap_unset409Turning something on or raising a budget needs a daily budget cap or the No limit choice, and neither is set. Only a person signed in to the dashboard sets it. Sends connectUrl.
ad_budget_cap_exceeded422The change would put the account's enabled daily budgets above the cap. Sends cap, wouldBe, currency and connectUrl. A person can raise the cap in the dashboard.
ad_budget_increase_too_large422One change raised a budget past the allowed multiple of the current amount. Sends maxRatio, current, requested and currency. Raise it in steps.
ad_budget_unreadable422Google gave no daily budget where Uplika needs one: for the campaign being raised (to apply the raise limit), or, when a cap is set, for a campaign in the account (to add up the total). Make the change in Google Ads.
ad_object_not_found400Nothing was read or changed. From set_ad_status or update_ad_budget over MCP: provider names a different ad network than the id belongs to (a Google Ads id looks like customers/123/campaigns/456 and a Meta id is digits only), so leave provider out. From get_ad (GET /v1/integrations/google_ads/objects/{id}): the id names a different Google Ads account than the connected one, or Google Ads has no such object in it. Read the ids again with list_ads or get_ad on the parent.
ad_terms_update_required409This Google Ads connection was made before Uplika could do this in Google Ads, and nobody has accepted the change yet. Sends dashboardUrl, accepted and required. Only a person signed in to the dashboard accepts it on the Google Ads card. Pausing and lowering budgets keep working.
ad_confirm_name_mismatch422delete_ad on a campaign or ad group: confirmName is not the current name. Nothing was removed, and the answer does not include the current name. Read it with get_ad and send it exactly. A missing confirmName is invalid_params.
ad_bidding_not_supported422set_ad_bidding: the campaign type does not take that strategy or field (Performance Max bids for conversions only, Demand Gen takes no max CPC, other types are changed in Google Ads). update_ad_campaign with maxCpc: the campaign does not use the Maximize clicks bid strategy, or it is a Demand Gen campaign. Nothing was changed. set_ad_bidding changes the bid strategy.
ad_targeting_not_supported422set_ad_targeting, update_ad_campaign or update_asset_group: the campaign type does not take that targeting or setting, for example topics on a Search ad group, countries on a Display ad group, or networks on a campaign that is not Search. The reply says what the type takes. Nothing was changed.
ad_extensions_not_supported422set_ad_extensions: the campaign type does not take that kind of extension, for example callouts on a Demand Gen campaign, which takes sitelinks only. The reply says what the type takes. Nothing was changed.
ad_media_unfit400Creating a Demand Gen, display or Performance Max campaign: an image does not fit its slot (shape, minimum size, format or file size), is not an Uplika media id of this workspace, or a video reference cannot be read as a YouTube video. Sends media, every item that did not fit with its slot and reason. Nothing was sent to Google. Uplika does not crop on its own: fit_ad_images (POST /v1/ads/images/fit) makes a copy in the slot's shape, which you send instead. Every line of fit_ad_images failing answers this code too, with the same media list.
ad_budget_below_minimum422Creating a Demand Gen campaign or changing its daily budget: the budget is below Google's minimum for the account currency. Sends minimum (in the account currency, not micros) and currency. Nothing was created or changed.
ad_conversion_tracking_missing422Creating a Performance Max campaign, or set_ad_bidding moving a campaign to a conversion strategy: no enabled conversion action that bidding counts recorded a conversion in the last 30 days, so the campaign would bid for conversions it cannot see. Sends reason: no_action (create one with create_conversion_action), no_recent_conversions (check the tag is on the site and try again after the first conversion), or google_not_enough (Google refused the strategy for too few conversions). Nothing was changed.
ad_object_removed409The object, or its parent, was removed in Google Ads, so it cannot be changed or get new ad groups, ads or keywords. Removing cannot be undone; make a new one instead.
ad_status_superseded409A pause for the same ad arrived while this turn-on waited, so it stays off. Send it again if you still want it on.
ads_no_access403The Google account that connected can no longer manage the ad account.
ads_two_step_required403Google Ads wants the connecting Google account to turn on 2-Step Verification before it manages this account.
ads_access_level_insufficient403uplika's Google Ads API access does not cover this account. This is on uplika's side; reconnecting will not change it.
ads_quota_exhausted429The Google Ads allowance for today is used up, for this workspace's share or for uplika as a whole. Sends retryAfter. Pausing by id still goes through unless Google itself refused it, and the message says which.
ads_upstream_rejected422Google Ads rejected the request. Sends googleErrors with Google's reasons. Do not send the same request again unchanged.
ads_upstream_unavailable503Google Ads did not answer, or asked uplika to wait. Read GET /v1/integrations/google_ads/objects before repeating a write.
invitation_channel400A connection link cannot connect these channels yet. Sends platforms. GET /v1/platforms lists, under connectInvite, the channels a link can connect today. Create the link without them.
invitation_bridge400These channels are never connected from a link: their posts are written by the Uplika extension in the browser that connected them. Sends platforms. Connect them in that browser instead.
invitation_limit429The daily cap on creating connection links is reached. Reuse a link that is still open, or try again after midnight UTC.
invitation_not_found404No connection link with that id in your workspaces.

내 키가 실제로 무엇을 보냈는지 어떻게 보나요

REST 와 MCP 호출이 요청·응답 본문과 함께 남습니다. 발행이 왜 거절됐는지 찾는 제일 빠른 길입니다. 채널이 한 말이 거기 그대로 들어 있습니다. 대시보드에서 한 일은 쓰기(발행 · 수정 · 삭제 · 업로드 · 설정 저장)와 실패, 조사 도구 사용만 남습니다. 로그 화면은 기본으로 대시보드 성공 줄을 숨기고, 「대시보드 요청 포함」 을 켜면 같이 보입니다. API 키 원문 같은 한 번만 보이는 값은 가려서 남깁니다.

GET/v1/logs

최근 API·에이전트 호출. 최신 순, 본문 포함. 대시보드 요청은 켜면 보입니다.

페이지 넘기기

이름타입설명
requestIdqueryOne call by the id an error response gave you.
outcomequeryfailed for 4xx and 5xx, ok for the rest. Omit for everything.
searchqueryMatches the path or the request id.
sincequeryYYYY-MM-DD. Calls from that day onward.
limitquery1-200, defaults to 50.
beforequeryA log id from a previous page's nextBefore.

자주 묻는 것

에러는 어떤 모양으로 오나요?

code 와 영어 message 를 가진 error 객체입니다. message 에 끼워 넣은 값은 따로 필드로도 오기 때문에, 우리 문장을 파싱하는 대신 자기 언어로 문장을 다시 만들 수 있습니다.

메시지가 왜 영어만 있나요?

응답이 언어를 타면 같은 요청이 묻는 사람에 따라 다르게 답하는 셈이라서입니다. 화면은 두 언어지만 API 는 아닙니다. message 가 아니라 code 로 그리세요.

rate_limited 를 받으면 어떻게 하나요?

기다렸다 다시 부르면 됩니다. 응답에 걸린 제한이 실려 오기 때문에 백오프를 짐작하는 대신 속도를 맞출 수 있습니다.