Get Post

Retrieve details and publishing status of a post group.

Endpoint

GET https://api.publora.com/api/v1/get-post/:postGroupId

Headers

Path Parameters

Response

{
  "success": true,
  "postGroupId": "507f1f77bcf86cd799439011",
  "status": "published",
  "scheduledTime": "2026-02-22T14:30:00.000Z",
  "platforms": ["twitter-123456789", "linkedin-ABC123"],
  "platformSettings": {
    "youtube": { "privacy": "public" }
  },
  "firstComment": {
    "text": "Full write-up with the numbers: https://example.com/launch",
    "platforms": ["linkedin"]
  },
  "firstComments": [
    { "text": "Full write-up with the numbers: https://example.com/launch", "platforms": ["linkedin"] }
  ],
  "posts": [
    {
      "_id": "663a1b2c3d4e5f6a7b8c9d01",
      "platform": "twitter",
      "platformId": "123456789",
      "content": "Excited to share our new product launch! 🚀",
      "status": "published",
      "postedId": "1234567890123456789",
      "permalink": null,
      "isThread": false,
      "threadParts": [],
      "firstCommentResult": null,
      "firstCommentResults": []
    },
    {
      "_id": "663a1b2c3d4e5f6a7b8c9d02",
      "platform": "linkedin",
      "platformId": "ABC123",
      "content": "Excited to share our new product launch! 🚀",
      "status": "published",
      "postedId": "urn:li:share:7654321",
      "permalink": null,
      "isThread": false,
      "threadParts": [],
      "firstCommentResult": {
        "status": "posted",
        "commentId": "urn:li:comment:(urn:li:activity:7654321,1234)",
        "skipReason": null,
        "error": null,
        "attemptedAt": "2026-02-22T14:30:04.120Z",
        "postedAt": "2026-02-22T14:30:05.310Z"
      },
      "firstCommentResults": [
        {
          "status": "posted",
          "commentId": "urn:li:comment:(urn:li:activity:7654321,1234)",
          "skipReason": null,
          "error": null,
          "attemptedAt": "2026-02-22T14:30:04.120Z",
          "postedAt": "2026-02-22T14:30:05.310Z"
        }
      ]
    }
  ],
  "media": []
}

Group-level fields

Read-after-write: scheduledTime, platforms and platformSettings echo what the server actually stored, not what you sent. A permitted past-time clamp may change scheduledTime; schedule-horizon violations are rejected, not adjusted. See past scheduled times.

Media inventory (media[])

One entry per attached file, in the order the files are attached to the post.

Per-platform fields (posts[])

Stable shape: platformId, postedId and permalink are always present on every posts[] entry. When a value is unavailable it is explicitly null — the key never disappears, so you can read it without existence checks.

permalink is not yet populated. The field is delivered end-to-end, but is currently null for essentially all posts pending a separate backfill. Treat a non-null permalink as a bonus, never a guarantee — to locate the live post today, resolve it from platform + platformId + postedId.

Note: With .lean(), the error field may be absent (undefined) for non-failed posts if the error subdocument was never populated — it will not necessarily be null. When a post has failed, the error field contains an error object with details about the failure.

Note: For draft and scheduled posts, postedId is null (present, but empty) since the post has not yet been published to the platform. Published posts normally carry a non-null postedId; a partially published X thread is the exception where a failed target can retain the head tweet ID in postedId.

Note: The platformId field returns the raw platform ID (e.g., "123456789"), not the compound format used by list-posts (e.g., "twitter-123456789"). See the list-posts endpoint for details on this difference.

Thread parts

X/Twitter and Meta Threads targets can publish one post as a chain of connected parts. get-post reports that progress per target.

{
  "_id": "663a1b2c3d4e5f6a7b8c9d04",
  "platform": "threads",
  "platformId": "17841412345678",
  "content": "The whole story, as submitted.\n\n---\n\nThe second half.",
  "status": "published",
  "postedId": "17900000000000001",
  "permalink": null,
  "isThread": true,
  "threadParts": [
    { "index": 0, "content": "The whole story, as submitted.", "status": "published", "publishedId": "17900000000000001" },
    { "index": 1, "content": "The second half.", "status": "published", "publishedId": "17900000000000002" }
  ]
}

postedId on the target is the first part's platform ID, which is also threadParts[0].publishedId. There is no single ID that addresses the whole chain.

After a partial failure, read the parts before acting. A chain that published some parts and then failed leaves those parts live on the platform, with status: "published" and a publishedId; the rest stay pending or failed and the target carries the error. A partially published chain is terminal and is not retried, and on Threads a re-entry guard additionally refuses any chain that already has published parts. Recreating the post would duplicate the parts that already exist — inspect threadParts and the live account, then publish only what is missing.

Note: threadParts is exposed by get-post only. list-posts does not include it, so fetch the group to inspect chain progress.

First comment result (posts[].firstCommentResult)

Read firstCommentResults[] in the same order as group firstComments[]. The legacy firstCommentResult mirrors item 0 and is null when no result applies. Comments become due on scheduler ticks in order; item N+1 waits until N is posted, and failure stops later items. A pending result may have a future dueAt.

Error codes specific to the comment: FIRST_COMMENT_PERMISSION_REQUIRED (the connection lacks the reply permission — reconnect it), FIRST_COMMENT_TARGET_UNAVAILABLE (the platform returned no ID for the published post), FIRST_COMMENT_NOT_ATTEMPTED (the publish was recovered late, so no comment was posted), FIRST_COMMENT_INTERRUPTED (the publishing worker stopped mid-way), FIRST_COMMENT_DEADLINE_EXCEEDED (the platform did not answer within the time budget). The general codes below (PLATFORM_AUTH_EXPIRED, RATE_LIMITED, X_REPLY_NOT_AUTHORIZED, …) can appear here too. A comment is never retried; the post itself is unaffected by a failed comment.

Failed Post Response

When a post fails, the response includes detailed error information:

{
  "success": true,
  "postGroupId": "507f1f77bcf86cd799439011",
  "posts": [
    {
      "_id": "663a1b2c3d4e5f6a7b8c9d03",
      "platform": "threads",
      "platformId": "17841412345678",
      "content": "Check out our new feature!",
      "status": "failed",
      "postedId": null,
      "permalink": null,
      "error": {
        "code": "PLATFORM_AUTH_EXPIRED",
        "message": "Error validating access token",
        "platformStatusCode": 401,
        "platformError": "Invalid OAuth access token",
        "failedAt": "2026-02-22T14:30:00.000Z",
        "retryable": false
      }
    }
  ]
}

Post Status Values

Note: The statuses above apply to individual platform posts. The post group itself can also have a status of partially_published, which occurs when some platform posts in the group succeeded while others failed. For example, if a post group targets Twitter, LinkedIn, and Threads, and the Threads post fails while the others succeed, the group status will be partially_published. Query individual posts within the group to determine which platforms succeeded or failed.

Error Codes

When status is failed, the error object contains:

Note: The error codes listed above are not exhaustive. The schema does not validate error codes, so additional codes beyond these eight may appear in the response. Always handle unknown codes gracefully.

Examples

JavaScript (fetch)

const postGroupId = '507f1f77bcf86cd799439011';
const response = await fetch(
  `https://api.publora.com/api/v1/get-post/${postGroupId}`,
  { headers: { 'x-publora-key': 'YOUR_API_KEY' } }
);
const data = await response.json();
 
for (const post of data.posts) {
  console.log(`${post.platform}: ${post.status}`);
  if (post.postedId) {
    console.log(`  Platform post ID: ${post.postedId}`);
  }
}

Python (requests)

import requests
 
post_group_id = '507f1f77bcf86cd799439011'
response = requests.get(
    f'https://api.publora.com/api/v1/get-post/{post_group_id}',
    headers={'x-publora-key': 'YOUR_API_KEY'}
)
data = response.json()
 
for post in data['posts']:
    print(f"{post['platform']}: {post['status']}")

cURL

curl https://api.publora.com/api/v1/get-post/507f1f77bcf86cd799439011 \
  -H "x-publora-key: YOUR_API_KEY"

Node.js (axios)

const axios = require('axios');
 
const { data } = await axios.get(
  `https://api.publora.com/api/v1/get-post/${postGroupId}`,
  { headers: { 'x-publora-key': 'YOUR_API_KEY' } }
);
// Check if all posts published successfully
const allPublished = data.posts.every(p => p.status === 'published');
console.log(`All published: ${allPublished}`);

Errors

Note: If x-publora-user-id matches the API key owner, no workspace check is triggered — the header is effectively a no-op in that case.

Note: A postGroupId that is not a valid MongoDB ObjectId returns 400 { "error": "Invalid post group ID" } before any lookup. Pass the IDs returned by create-post or list-posts.

Publora is built by Creative Content Crafts, Inc. Need AI-powered content creation for LinkedIn, Threads, and X? Try Co.Actor — the best AI service for authentic thought leadership at scale.