402) instead of finding out from the error.
No request parameters. GET only.
Response Fields
object
Team identity:
id, name, created_at, timezone_string, and intention.string
The effective plan after expiry is applied: one of
free, growth, expert, ultimate, or pro (legacy, same limits as growth). If plan.configured is a paid plan but plan.expiry is in the past, plan.type is free. Read the numbers from limits rather than mapping the plan name yourself. Per-plan values are in Rate Limits.string
The plan as configured, before expiry is considered.
boolean
When
true, plan limits are not enforced for this team and every plan-based max in limits is null. limits.profiles_per_watchlist is the one exception: it is a hard cap on a single list rather than a plan limit, so it stays 200 for bypass teams too.object
max watchlists allowed on the effective plan (all four types combined) and used, the current count. max is null when limits are bypassed. When used >= max, the next watchlist create returns 402.object
Maximum and current team member count.
object
Maximum posts collected per watchlist per week on the effective plan: 2,000 on free, 15,000 on every paid plan. It counts posts scored relevance 4 or higher.
object
Maximum active auto-engagement rules per watchlist on the effective plan. There is no API endpoint for these rules: they are created in the OutX app only, and this number is reported here for reference. To automate engagement from code, poll
GET /api-posts and call POST /api-like or POST /api-comment on the posts you pick, which is your own loop rather than a rule. See Use cases.object
max profiles and companies the team may track at once and used, the current count. Counted across every people and company watchlist the team owns, so spreading profiles over new watchlists does not raise it. max is null when limits are bypassed. Check this before a people or company create: when used plus the profiles you are about to send exceeds max, the create returns 402.object
max profiles a single people watchlist may hold, always 200. A hard cap rather than a plan limit, so it does not change with the plan and is not nulled for bypass teams. Exceeding it returns 400, not 402. There is no used on this entry: read profiles_count from the watchlist’s own GET.