Skip to content

Monitoring Linkedin

GET
/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.

Authorizations

Parameters

Query Parameters

page
integer
default: 1 >= 1 <= 1000
limit
integer
default: 50 >= 1 <= 200
competitor_domain
Any of:
string
<= 255 characters
date_from
Any of:
string format: date
date_to
Any of:
string format: date

Header Parameters

X-Target-Org-Id
Any of:
string

Responses

200

Successful Response

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string