How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Uplika Posts API

The Posts API from Uplika — 37 operation(s) for posts.

Uplika Posts API is one of 10 APIs that Uplika publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Posts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 41 operations across 37 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.uplika.com.

41 operations 37 paths 1 schemas 1 DELETE23 GET2 PATCH14 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.uplika.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Uplika Posts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey). By default, every request must be authenticated.

  • apiKey — An API key from the dashboard.

Paths & Operations 41

Across 37 paths, the API surfaces 41 operations — 1 DELETE, 23 GET, 2 PATCH, 14 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Posts 41
GET
/v1/posts
Recent publishes, newest first. Replies are not listed as posts
getV1Posts 7 params → default
POST
/v1/posts
Publish to one or more connected accounts
postV1Posts body → default
GET
/v1/posts/{id}
One publish with the status of each target
getV1PostsById 1 param → default
PATCH
/v1/posts/{id}
Change a scheduled or draft post before it goes out.
patchV1PostsById 1 param body → default
DELETE
/v1/posts/{id}
Delete the post from the channel and mark our record deleted
deleteV1PostsById 1 param → default
POST
/v1/posts/{id}/publish
Send a scheduled or draft post right now.
postV1PostsByIdPublish 1 param body → default
POST
/v1/posts/{id}/retry
Retry the targets that failed. Targets that already went out are skipped.
postV1PostsByIdRetry 1 param → default
GET
/v1/posts/{id}/thread
One post with its replies and metrics in a single call
getV1PostsByIdThread 1 param → default
GET
/v1/channels/posts
What is on the channel right now, including posts written in the app
getV1ChannelsPosts 2 params → default
GET
/v1/channels/quota
How much of the 24 hour allowance the channel says is used
getV1ChannelsQuota → default
GET
/v1/channels/bridge
Whether the Naver Blog bridge (browser extension) is online, and how to wake…
getV1ChannelsBridge → default
GET
/v1/channels/publish-options
What a channel needs to know before you publish to it.
getV1ChannelsPublishOptions 1 param body → default
GET
/v1/channels/instagram/audio
Music and original sounds one Instagram account can put on a reel, for…
getV1ChannelsInstagramAudio 5 params body → default
POST
/v1/accounts/select
Pick which connected channels to publish to
postV1AccountsSelect → default
POST
/v1/accounts/:id/refresh
Re-read a channel's metadata, such as Naver Blog categories or Pinterest boards.
postV1Accounts:idRefresh body → default
PUT
/v1/accounts/:id/pinterest/default-board
Set the board a Pinterest connection pins to when a post leaves out…
putV1Accounts:idPinterestDefaultBoard body → default
GET
/v1/naver/blog/diagnose
Read a Naver blog's public RSS feed (its latest posts, at most 50) and say…
getV1NaverBlogDiagnose body → default
POST
/v1/naver/keywords/judge
Measure Naver search keywords and pick a set for one post.
postV1NaverKeywordsJudge body → default
POST
/v1/naver/keywords/measure
Same measurement without the verdict and sets.
postV1NaverKeywordsMeasure body → default
POST
/v1/naver/keywords/expand
Expand seed keywords one level through Naver autocomplete, for agents and API…
postV1NaverKeywordsExpand body → default
GET
/v1/naver/keywords/reports
List the keyword research you saved (judge with save: true), newest first…
getV1NaverKeywordsReports body → default
GET
/v1/naver/keywords/history
The measurement history of one keyword: one point per day it was actually…
getV1NaverKeywordsHistory body → default
GET
/v1/research/youtube/search
Search YouTube for a keyword and get the top videos with views, subscribers…
getV1ResearchYoutubeSearch body → default
GET
/v1/research/youtube/reports
The person's saved YouTube searches, newest first: when, the search and its…
getV1ResearchYoutubeReports body → default
GET
/v1/research/youtube/reports/{id}
One saved search with the videos as they were and the prompt built from them
getV1ResearchYoutubeReportsById 1 param → default
POST
/v1/naver/visibility/checks
Checks up to 10 keywords on Naver's integrated search through the person's…
postV1NaverVisibilityChecks body → default
GET
/v1/naver/visibility/runs/{runId}
One check: status (running, done, partial, failed), how many keywords came…
getV1NaverVisibilityRunsByRunId 1 param → default
GET
/v1/naver/visibility/runs
This person's recent checks, newest first: kind, keyword count, how many came…
getV1NaverVisibilityRuns body → default
POST
/v1/naver/visibility/scan
Starts a blog's report card: reads its latest posts from the public RSS feed…
postV1NaverVisibilityScan body → default
GET
/v1/naver/visibility/blog
A blog's report card from what was recorded: cards (AI citation rate, search…
getV1NaverVisibilityBlog body → default
GET
/v1/naver/visibility/posts/{blogId}/{logNo}
One post's record: the post being watched (main keyword and where it came…
getV1NaverVisibilityPostsByBlogIdByLogNo 2 params → default
PATCH
/v1/naver/visibility/posts/{blogId}/{logNo}
Sets a post's main keyword, the one its checks search for.
patchV1NaverVisibilityPostsByBlogIdByLogNo 2 params body → default
GET
/v1/naver/visibility/keywords
Every check of one keyword by this person, newest first, each with the AI…
getV1NaverVisibilityKeywords body → default
POST
/v1/naver/seo/check
Run the Naver Blog placement checks on a Markdown body before publishing…
postV1NaverSeoCheck body → default
POST
/v1/naver/layout
See how a body will be laid out before publishing.
postV1NaverLayout body → default
GET
/v1/naver/forms
The seven post forms we ship.
getV1NaverForms → default
GET
/v1/naver/drafts
The drafts in the blog's draft box: posts saved with draftOnly and anything…
getV1NaverDrafts → default
POST
/v1/naver/drafts/{logNo}/publish
Publishes a draft from the draft box exactly as it is in Naver: the extension…
postV1NaverDraftsByLogNoPublish 1 param body → default
GET
/v1/naver/grammar
What the Naver Blog body understands: directives, block and inline markup…
getV1NaverGrammar body → default
POST
/v1/naver/forms/extract
Read a public Naver Blog post and hand back its form.
postV1NaverFormsExtract body → default
GET
/v1/naver/forms/snapshot
When a reference post was last read, and how many blocks and photos it had.
getV1NaverFormsSnapshot body → default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uplika-com-posts-api-openapi.yml Raw ↑

Other APIs Uplika publishes across the network.

Uplika API
Uplika Automations API
Uplika Connecting channels API
Uplika Errors API
Uplika Inbox and contacts API
Uplika Media API
Uplika Platforms API
Uplika Replies and insights API
Uplika Troubleshooting and FAQ API
Where this information came from

This is an independent, third-party profile of Uplika Posts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.