Improved
LinkedIn Comments — Comment & Post Timestamps Now Populated
5 days ago by ReadMe API
⚠️ Breaking — new timestamp fields added, previously-null field now populated.
LinkedIn Comments (contact) signals now include actual posting timestamps. Previously, detected_at (when Autobound ingested the signal, typically 1-3 weeks after posting) was the only time reference.
New & Updated Fields
| Field | Type | Change | Description |
|---|---|---|---|
data.comment_posted_at | string (ISO 8601) | New | When the comment was actually posted on LinkedIn |
data.parent_post.posted_date | string (ISO 8601) | Now populated | When the parent post was published (field existed but was always null) |
Example
{
"data": {
"comment_posted_at": "2026-04-27T00:03:51.002Z",
"parent_post": {
"posted_date": "2026-04-24T00:21:40.232Z"
}
}
}All other fields unchanged. View full schema →
Effective: May 12, 2026 delivery onward (autobound-linkedin-comments-contact-v2 bucket).
Action required: If you filter on posted_date IS NULL or parse posted_date as a date-only string, update your logic. The field is now a full ISO 8601 datetime with milliseconds.
