Get post detail - Autotouch AI

This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.

This read endpoint uses the caller’s resolved LinkedIn connection and requires linkedin:read for developer API keys; authenticated user sessions are also accepted. No sender-account selector is accepted. The response is passed through from the provider; this API does not normalize it into a fixed post schema.

Path parameters

post_idrequired
string
Provider post ID. The handler documents LinkedIn `social_id` format such as `urn:li:activity:7177842619385757696`; URL-encode reserved characters in the path.

Name	Type	Description
post_idrequired	string	Provider post ID. The handler documents LinkedIn `social_id` format such as `urn:li:activity:7177842619385757696`; URL-encode reserved characters in the path.

Errors

Status	Meaning
401	Invalid API key or missing auth.
403	Developer API key lacks linkedin:read scope.
400	Organization/user context is missing or LinkedIn is not connected.
424	The connected account requires reconnect for this operation.
429	Account policy does not currently allow the request.
502	Fallback when the provider error has no HTTP status; a provider HTTP status may otherwise be returned.
503	Unipile LinkedIn integration is not configured.

Example

bash

curl -X GET "https://app.autotouch.ai/api/integrations/linkedin/posts/urn%3Ali%3Aactivity%3A7177842619385757696/detail" \
  -H "Authorization: Bearer stk_your_key_id.your_secret"

Response example

json

{
  "id": "urn:li:activity:7177842619385757696",
  "author": {
    "name": "Jane Doe",
    "headline": "VP Engineering at Acme Corp",
    "profile_url": "https://www.linkedin.com/in/janedoe"
  },
  "text": "Excited to share that we just closed our Series B...",
  "created_at": "2026-03-08T14:30:00Z",
  "likes_count": 142,
  "comments_count": 23,
  "shares_count": 8,
  "media": []
}