Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Brain

Suggest a competitor

Suggests a competitor for a person to add. It waits under Suggested in Brain > Brand > Competitors, and counts only after a person adds it. The site of the business, a site that it has as a competitor, a site that a person dismissed, and a site that many businesses share are refused. 20 suggestions wait at most.

post/api/v1/brand/competitors/suggestions

Authorization

HeaderAuthorization: Bearer <API key>
Or the headerX-API-Key: <API key>
API keyMake one in Troopy under Settings > API keys. It acts as you, in its workspace.

Other ways to call it

CLItroopy brand competitor-suggest
MCP tooltroopy_suggest_competitor
Rate limit60 calls in 60 seconds, for each key
RetriesSend an Idempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.

Body

application/json
name*string

Its name, as its site writes it

At least 1 characters · At most 80 characters

site*string

Its website or its domain, like rival.com

At least 3 characters · At most 300 characters

why*string

Why it competes with the business, in one or two sentences: whom it sells to, and what

At least 1 characters · At most 300 characters

Response

201 · application/json
data*object
6 properties
id*string

A 24-character id

name*string
site*string
why*string

Why the teammate thinks that it competes, in the teammate's words

by*object

Who wrote it

3 properties
type*enum<string>

personagentapi

id*string
name*string
at*string

ISO 8601 date and time

Errors

400 invalid_inputFix the field named in detail. Each operation's schema is in /api/v1/openapi.json.
401 unauthorizedSend an API key as `Authorization: Bearer tr_live_...`. Create one in Troopy under Settings.
403 forbiddenThe key lacks a scope this operation needs, or its owner lacks the role. detail says which; create a key with the scope, or ask an organization owner or admin.
409 conflictThis Idempotency-Key was used for a different request, or that request is still running. Use a new key for a new request.
429 rate_limitedWait the number of seconds in Retry-After, then retry.