LinkedIn Commentaires de la publication API
Listez les commentaires d’une publication LinkedIn - texte complet, nom/URL/intitulé de poste de l’auteur du commentaire, horodatages et engagement.
2,90 $US/1k req, paiement à la requête, sans abonnement.
Pinned by author
Priya Nakamura
Head of Finance Engineering at Northwind Financial
This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.
Sep 18, 2025214Reply
Marcus Delgado
Product Manager, Billing at Cedarlane Health
Great conversation. Curious whether the same approach to dunning applies once you are dealing with multi-currency subscriptions, that is where we keep hitting edge cases.
Sep 17, 202558Reply
Vantage Robotics
Autonomous inspection drones
We are hosting a follow-up session on this exact topic next month. Would love to have some of the folks in this thread join the panel.
Sep 17, 202519Reply
{"id": "7477792100112233445","commentary": "This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.","url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29","createdUtc": 1758153600,"pinned": true,"edited": false,"actor": {...},"engagement": {...}}
Tarifs et fournisseurs
Tarifs de l’API LinkedIn Commentaires de la publication : une API, 4 fournisseurs interchangeables
Le fournisseur le moins cher répond en premier. S’il échoue, le suivant prend le relais dans le même appel.
plafonné à 0,144 $US par requête1 résultat0,00144 $US50 résultats0,072 $US100 résultatsplafond de 0,144 $USVous payez ce qui vous revient. Baissez la limite pour payer moins - et aucune requête ne peut coûter plus que le plafond, quelle que soit la quantité renvoyée.4HoneybeeSecours 399,56% de disponibilité4043ms p5011,8% des appels11,8%905 appels2,40 $US/1k résultatsjusqu’à 0,24 $US / requêteFacturé par résultat renvoyé0,0024 $US par résultat
plafonné à 0,24 $US par requête1 résultat0,0024 $US50 résultats0,12 $US100 résultatsplafond de 0,24 $USVous payez ce qui vous revient. Baissez la limite pour payer moins - et aucune requête ne peut coûter plus que le plafond, quelle que soit la quantité renvoyée.
Essayer
Obtenez LinkedIn Commentaires de la publication en une requête
Cet exemple affiche 19 champs sur 20. Voir tous les champs
{
"found": true,
"data": {
"items": [
{
"id": "7477792100112233445",
"commentary": "This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29",
"createdUtc": 1758153600,
"pinned": true,
"edited": false,
"actor": {
"id": "ACoAAB99887766ccddeeff",
"name": "Priya Nakamura",
"type": "profile",
"linkedinUrl": "https://www.linkedin.com/in/priya-nakamura-fin",
"position": "Head of Finance Engineering at Northwind Financial",
"image": "https://media.licdn.com/dms/image/C4E03AQZ9n2h/dp_200/0/167?e=175"
},
"engagement": {
"likes": 214,
"comments": 6
}
},
{
"id": "7477792200223344556",
"commentary": "Great conversation. Curious whether the same approach to dunning applies once you are dealing with multi-currency subscriptions, that is where we keep hitting edge cases.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792200223344556%29",
"createdUtc": 1758150000,
"pinned": false,
"edited": true,
"actor": {
"id": "ACoAAB88776655bbccddee",
"name": "Marcus Delgado",
"type": "profile",
"linkedinUrl": "https://www.linkedin.com/in/marcus-delgado-payments",
"position": "Product Manager, Billing at Cedarlane Health",
"image": "https://media.licdn.com/dms/image/C4E03AQY8n2h/dp_200/0/167?e=175"
},
"engagement": {
"likes": 58,
"comments": 2
}
},
{
"id": "7477792300334455667",
"commentary": "We are hosting a follow-up session on this exact topic next month. Would love to have some of the folks in this thread join the panel.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792300334455667%29",
"createdUtc": 1758146400,
"pinned": false,
"edited": false,
"actor": {
"id": "urn:li:organization:4471203",
"name": "Vantage Robotics",
"type": "company",
"linkedinUrl": "https://www.linkedin.com/company/vantage-robotics",
"position": "Autonomous inspection drones",
"image": "https://media.licdn.com/dms/image/C560BAQF7n2h/logo_200/0/167?e=175"
},
"engagement": {
"likes": 19,
"comments": 0
}
}
]
}
}Référence complète des paramètres et de la réponse : chaque champ, type et exemple de cet endpoint.
Référence
Une requête, une seule forme de réponse.
Chaque champ que vous envoyez et chaque champ que vous recevez, avec un vrai exemple.
Dernière vérification : 2026-11-21 · disponibilité et latence mesurées sur 30d
Corps de la requête
JSON, envoyé à cet endpoint.
- urlstring
https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ
URL complète de la publication LinkedIn dont lister les commentaires.
- limitinteger
10
Nombre maximal de commentaires à renvoyer.
- postedLimitenum
Ne renvoie que les commentaires publiés dans cette fenêtre (any par défaut).
Réponse
JSON, une valeur d’exemple par champ.
The commenter (a profile or a company).
- idstring
ACoAAB99887766ccddeeff
LinkedIn identifier of the commenter.
- imagestring
https://media.licdn.com/dms/image/C4E03AQZ9n2h/dp_200/0/167?e=175
Profile picture URL of the commenter. Populated whenever the provider has data for the entity.
- linkedinUrlstring
https://www.linkedin.com/in/priya-nakamura-fin
Canonical LinkedIn URL of the commenter. Populated whenever the provider has data for the entity.
- namestring
Priya Nakamura
Display name of the commenter. Populated whenever the provider has data for the entity.
- positionstring
Head of Finance Engineering at Northwind Financial
Commenter's headline or job title as displayed. Populated whenever the provider has data for the entity.
- typestring
profile
Commenter kind, e.g. 'profile' or 'company'.
The post's comments. Populated whenever the provider has data for the entity.
- commentarystring
This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.
Full text of the comment. Populated whenever the provider has data for the entity.
- createdUtcnumber
1758153600
UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.
- editedboolean
false
Whether the comment has been edited.
- idstring
7477792100112233445
Unique identifier of the comment. Populated whenever the provider has data for the entity.
- pinnedboolean
true
Whether the comment is pinned on the post.
- urlstring
https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29
Canonical permalink URL of the comment. Populated whenever the provider has data for the entity.
Engagement metrics for the comment.
- commentsinteger
6
Number of replies to the comment.
- likesinteger
214
Number of likes on the comment.
- foundboolean
true
Whether comments were found for the post.
- reason"not_found"
Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.
Vous vendez cette API ? Consultez le schéma complet que votre endpoint doit renvoyer.
FAQ
À propos de l’API LinkedIn Commentaires de la publication
L’API LinkedIn Commentaires de la publication d’AnyAPI renvoie des données LinkedIn en JSON normalisé à partir d’un appel POST à /v1/run/linkedin.post_comments. Listez les commentaires d’une publication LinkedIn - texte complet, nom/URL/intitulé de poste de l’auteur du commentaire, horodatages et engagement. AnyAPI route chaque requête sur 4 sources et bascule automatiquement quand l’une échoue. Elle coûte à partir de 2,90 $US pour 1 000 requêtes, en dollars US, sans abonnement et sans minimum mensuel. Ces 30 derniers jours, 99,9% des appels LinkedIn Commentaires de la publication passés par AnyAPI ont réussi, avec un temps de réponse médian de 2,1 secondes, sur 7 644 appels mesurés.