Skip to main content
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": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.postsyncer.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Get Post by URL

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

​
post_url
string
required
Percent-encoded public permalink matching the stored platform post URL
​
include_comments
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

​
401
Unauthorized
Missing or invalid API token
​
403
Forbidden
Token does not have the posts ability
​
404
Not Found
No post with this URL in any accessible workspace