Get Post by URL

curl -X GET "https://postsyncer.com/api/v1/posts/by-url/https%3A%2F%2Fx.com%2Fuser%2Fstatus%2F1234567890?include_comments=false" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

{
  "401": {},
  "403": {},
  "404": {}
}

GET

posts

by-url

{post_url}

curl -X GET "https://postsyncer.com/api/v1/posts/by-url/https%3A%2F%2Fx.com%2Fuser%2Fstatus%2F1234567890?include_comments=false" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

{
  "401": {},
  "403": {},
  "404": {}
}

Returns the same payload as Get Post, but looks up the record by the exact post_url saved on a published platform row (platform_posts.post_url), scoped to workspaces your token can access. Use this when you have a share link (for example https://x.com/user/status/123) instead of the internal PostSyncer post id.

Path encoding

The URL must be passed as one path segment. Percent-encode it (RFC 3986), so slashes and colons become %2F, %3A, etc.

Request

string

required

Percent-encoded public permalink matching the stored platform post URL

boolean

default:"false"

Same as Get Post: include comments and CRM contact info when true

curl -X GET "https://postsyncer.com/api/v1/posts/by-url/https%3A%2F%2Fx.com%2Fuser%2Fstatus%2F1234567890?include_comments=false" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Response

Same fields as Get Post.

Error Codes

Unauthorized

Missing or invalid API token

Forbidden

Token does not have the posts ability

Not Found

No post with this URL in any accessible workspace

Start here

Guides

MCP

API reference

Get Post by URL

Get Post by URL

Path encoding

Request

Response

Error Codes

​Get Post by URL

​Path encoding

​Request

​Response

​Error Codes

Get Post by URL

Path encoding

Request

Response

Error Codes