Zernio
Zernio
API Reference

Mentions

List mentionsGETReply to a mentionPOST
Dashboard
llms.txtOpenAPI
OverviewPlatformsAPI ReferenceResources
Mentions

List mentions

Returns mentions of your connected organization accounts, delivered via platform webhooks. Currently supports LinkedIn organization mentions.

Requires Inbox addon.

GET
/v1/inbox/mentions

Authorization

bearerAuth
AuthorizationBearer <token>

API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.

In: header

Query Parameters

accountId?string

Filter by account ID

profileId?string

Filter by profile ID

sortOrder?string

Sort order by publishedAt

Default"desc"

Value in

  • "asc"
  • "desc"
limit?integer
Range1 <= value <= 100
Default25
cursor?string

Cursor for pagination (ID of the last item from the previous page)

Response Body

application/json

application/json

import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.mentions.listInboxMentions();console.log(data);
{  "data": [    {      "id": "string",      "platform": "linkedin",      "accountId": "string",      "accountUsername": "string",      "content": "string",      "permalink": "string",      "authorUrn": "string",      "authorName": "string",      "authorUsername": "string",      "authorPicture": "string",      "organizationalEntity": "string",      "publishedAt": "2019-08-24T14:15:22Z",      "createdAt": "2019-08-24T14:15:22Z"    }  ],  "pagination": {    "hasMore": true,    "cursor": "string"  },  "meta": {    "total": 0,    "sortOrder": "asc"  }}
Was this page helpful?

Reply to review

Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than replaying the other review'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) fetch the review before retrying with the same key, and treat a missing reply as inconclusive rather than as proof nothing was sent.

Reply to a mention

Reply to a mention of the connected account. Supported on Instagram only. Two shapes, selected by whether `commentId` is present: - **Comment mention** (someone @mentioned the account inside a comment): pass both `mediaId` and `commentId`. Instagram posts a reply under that comment. - **Caption mention** (someone @mentioned the account in their media caption, so no comment exists): pass `mediaId` only. Instagram posts a comment on their media. Story mentions are not supported by Instagram's API. `GET /v1/inbox/mentions` currently returns LinkedIn mentions only and does not surface Instagram mentions. Source `mediaId` and `commentId` from Instagram's `comments` webhook, which is where mention notifications are delivered for accounts connected through Instagram Login.