> ## Documentation Index > Fetch the complete documentation index at: https://getanyapi.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # LinkedIn Post > Sell linkedin.post on AnyAPI: the request your endpoint receives, the response it must return, and what the real-request check judges. Fetch a single LinkedIn post or article by URL (title, text, author, like and comment counts, publish date). This page is the seller-facing summary of one catalog API, `linkedin.post`. The transport rules that apply to every API a seller serves - signed requests, the response envelope, timeouts, and body limits - are on [the operator endpoint contract](https://getanyapi.com/docs/sell/operator-endpoint-contract.md). ## The price you compete with AnyAPI publishes this API from **\$0.80 per 1,000 requests**. That is the price a buyer sees today, so it is the price your endpoint has to come in under to win traffic. ## The request your endpoint receives | Field | Type | Required | What it means | | - | - | - | - | | `requireFields` | array | no | Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `image`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a post that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. | | `url` | string | yes | Full LinkedIn post or article URL. | > [accordion] Full input JSON Schema > > ```json theme={"dark"} > { > "$schema": "https://json-schema.org/draft/2020-12/schema", > "$id": "https://getanyapi.com/schemas/linkedin.post.input.json", > "example": { > "url": "https://www.linkedin.com/posts/stripe_last-week-agent-traffic-surpassed-human-activity-7470882737390940160-2Nxs" > }, > "title": "LinkedIn post input", > "type": "object", > "additionalProperties": false, > "required": [ > "url" > ], > "properties": { > "url": { > "type": "string", > "description": "Full LinkedIn post or article URL." > }, > "requireFields": { > "type": "array", > "uniqueItems": true, > "items": { > "type": "string", > "enum": [ > "authorImage", > "image" > ] > }, > "description": "Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `image`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a post that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge." > } > } > } > ``` ## The response your endpoint must return | Field | Type | Always present | What it means | | - | - | - | - | | `data` | null or object | yes | The post result, or null when not found. | | `data.author` | string | yes | Name of the post author. | | `data.authorImage` | string or null | no | Author avatar or company logo image URL, or null when the serving source does not carry one. The query string is a signed token, so keep the URL intact. | | `data.authorUrl` | string | no | LinkedIn URL of the post author. | | `data.comments` | integer | yes | Number of comments on the post. | | `data.createdUtc` | number | yes | UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. | | `data.image` | string or null | no | First image attached to the post, or null when the serving source does not carry one. The query string is a signed token, so keep the URL intact. | | `data.likes` | integer | yes | Number of likes on the post. | | `data.text` | string | yes | Text content of the post. | | `data.title` | string | yes | Title of the post. | | `data.url` | string | yes | Canonical URL of the post. | | `found` | boolean | yes | Whether the post was found. | Extra fields are kept, missing declared fields fail. > [accordion] Full output JSON Schema > > ```json theme={"dark"} > { > "$schema": "https://json-schema.org/draft/2020-12/schema", > "$id": "https://getanyapi.com/schemas/linkedin.post.output.json", > "title": "LinkedIn post output", > "type": "object", > "additionalProperties": false, > "required": [ > "found", > "data" > ], > "properties": { > "found": { > "type": "boolean", > "description": "Whether the post was found." > }, > "data": { > "description": "The post result, or null when not found.", > "oneOf": [ > { > "type": "null" > }, > { > "type": "object", > "required": [ > "url", > "title", > "text", > "author", > "likes", > "comments", > "createdUtc" > ], > "properties": { > "url": { > "x-anyapi-must-populate": true, > "type": "string", > "description": "Canonical URL of the post." > }, > "title": { > "type": "string", > "description": "Title of the post." > }, > "text": { > "x-anyapi-must-populate": true, > "type": "string", > "description": "Text content of the post." > }, > "author": { > "x-anyapi-must-populate": true, > "type": "string", > "description": "Name of the post author." > }, > "likes": { > "type": "integer", > "description": "Number of likes on the post." > }, > "comments": { > "type": "integer", > "description": "Number of comments on the post." > }, > "createdUtc": { > "x-anyapi-must-populate": true, > "type": "number", > "description": "UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds." > }, > "authorUrl": { > "type": "string", > "description": "LinkedIn URL of the post author." > }, > "authorImage": { > "type": [ > "string", > "null" > ], > "description": "Author avatar or company logo image URL, or null when the serving source does not carry one. The query string is a signed token, so keep the URL intact." > }, > "image": { > "type": [ > "string", > "null" > ], > "description": "First image attached to the post, or null when the serving source does not carry one. The query string is a signed token, so keep the URL intact." > } > } > } > ] > } > } > } > ``` ## Fields that must never come back empty * `author` * `createdUtc` * `text` * `url` The repository marks these fields as ones every source must be able to fill. An empty value is only correct when the entity itself genuinely has nothing there. ## Not found, and how it differs from empty When the entity does not exist, answer 2xx with the not-found shape: ```json theme={"dark"} { "found": false, "data": null } ``` An empty result is not a not-found: when the entity exists but carries nothing, answer 2xx with `found: true` and the empty values. This output schema declares no `reason` field, so `found: false` is the whole not-found answer. ## Example request ```json theme={"dark"} { "url": "https://www.linkedin.com/posts/stripe_last-week-agent-traffic-surpassed-human-activity-7470882737390940160-2Nxs" } ``` The registration tests send this example to your endpoint, with the API's other test inputs. After that, the real-request check sends your endpoint real past customer inputs, and an AI reviewer compares each answer with AnyAPI's own answer to the same input. ## Next * [The operator endpoint contract](https://getanyapi.com/docs/sell/operator-endpoint-contract.md) for signing, budgets, and the real-request check. * [Every API open to sellers](https://getanyapi.com/docs/sell/apis/index.md). * Want to sell an API that is not on that list? Email [support@getanyapi.com](mailto:support@getanyapi.com). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.