Reply to comment
Post a reply to a post or specific comment. Requires accountId in request body.
Idempotency: send an Idempotency-Key header to make retries safe (e.g. after a client-side timeout where delivery is unknown): same key + same body replays the original response (with Idempotent-Replayed: true) instead of posting the comment a second time; same key + different body returns 422; a key still in flight returns 409. Keys are retained for 24 hours and are scoped to the credential and to this exact path, so reusing a key against a different postId returns 422 rather than replaying the other post's response.
Only successful (2xx) responses are stored for replay. If the request throws or returns a non-2xx status the key is released, so the header protects the "request succeeded but the response was lost" case. After an ambiguous failure (a 5xx or a network timeout) list the post's comments before retrying with the same key, and treat an empty result as inconclusive rather than as proof nothing was posted.
Billing: Request; paid actions are priced in credits (see GET /v1/messaging/prices) · Rate limit: 60/min
Request
- Base URL: https://apihub.co.il
- URL: https://apihub.co.il/v1/messaging/inbox/comments/{postId}
- Auth: HTTP bearer
Path parameters
Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
Headers
Replay-safe: the same execution is returned instead of charging twice
Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…
Request body
Response
Completed
Changes
No recorded changes to this operation across all 2 revisions of this API.