Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / CRM

Add people from Stripe or PostHog

Adds people your own Stripe or PostHog knows to a list of people, each with why in the list's Signal column (made when missing): customers who canceled (stripe_canceled), who asked to cancel at the end of their period (stripe_canceling), new customers (stripe_new), or people who signed up, as PostHog first saw them (posthog_signups), in the last days you say, newest first, at most 200 a call. Only people with an email are added, each recorded as coming from that service, which Troopy only reads. Needs it connected in Settings > Apps.

post/api/v1/lists/{id}/signals

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 lists add-signals
MCP tooltroopy_add_list_signals
Rate limit10 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.

Path parameters

id*string

A 24-character id

Body

application/json
source*enum<string>

stripe_canceledstripe_cancelingstripe_newposthog_signups

daysinteger

How far back to look, in days

Default 30 · At least 1 · At most 365

Response

200 · application/json
data*object
4 properties
found*integer

People with an email the service gave

added*integer
updated*integer
skipped*integer

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.
404 not_foundCheck the path and any id in it. Every operation is listed in /api/v1/openapi.json.
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.