Radar

Monitoring Linkedin

Competitor LinkedIn posts (listener store first, then corpus fallback).

Every filter is forwarded as a RESOLVED value. Called directly (not via FastAPI), omitted date_from/date_to params would keep their Query sentinels, and the cb handler's date_from > date_to guard then raises TypeError (Query vs Query) -> a 500 on every call. Passing the coerced date/None values instead lets the guard emit a clean 422 on an inverted range and exposes the page/domain/date filters the cb route supports.

get/radar/monitoring/linkedin

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/radar/monitoring/linkedin
  • Auth: HTTP bearer

Query parameters

pageinteger
limitinteger
competitor_domainstring nullable
date_fromstring date nullable
date_tostring date nullable

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 2 revisions of this API.