Find Post

Get Post by ID

Endpoint:

GET https://app.marketingblocks.co/api/v1/social-sparks/post/{post_id}

Retrieves detailed information about a specific social media post using its unique post_id. Requires the social-view-post permission.


Authentication

Type: Bearer Token

Authorization: Bearer <token>

Path Parameters

Parameter
Type
Required
Description
Example

post_id

string

yes

Unique identifier of the post to be retrieved.

1246


Example Request

cURL

curl --location --request GET \
'https://app.marketingblocks.co/api/v1/social-sparks/post/1246' \
--header 'Authorization: Bearer <token>'

Plain URL


Response Structure

The response is a JSON object with the following fields:

  • post (object): Contains details about the post.

  • status (boolean): Indicates if the request was successful.

Field
Type
Description

post_id

integer

The ID of the post.

channel_type

string

The type of channel (facebook, twitter, instagram, etc.).

channel_id

string

Unique identifier for the channel.

STATUS

string

The current status of the post (published, draft, failed).

permalink

string

Direct link to the post.


Example Response


Status

Description

pending

The post has been successfully created in the system but has not yet started the publishing process. It is waiting to be processed.

processing

The post is currently being processed for publishing. This may include media upload, API communication with the social platform, formatting, or validation steps.

scheduled

The post has been scheduled to be published at a specific date and time provided during post creation. It will automatically move to processing at the scheduled time.

queued

The post has been placed in a publishing queue and will be published in the next available time slot based on the user's queue or automation settings.

published

The post has been successfully published and is now live on the social media platform.

failed

The post failed to publish. The system will store an error message explaining the reason (e.g., API rejection, invalid media format, authentication error, or network failure).

Last updated