Request
- Base URL: https://us.posthog.com
- URL: https://us.posthog.com/api/projects/{project_id}/signals/source_configs/{id}/
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
A UUID string identifying this signal source config.
Project ID of the project you're trying to access. To find the ID of the project, make a call to /api/projects/.
Request body
- session_replay - Session replay
- llm_analytics - LLM analytics
- github - GitHub
- linear - Linear
- jira - Jira
- zendesk - Zendesk
- conversations - Conversations
- error_tracking - Error tracking
- pganalyze - pganalyze
- signals_scout - Signals scout
- signals_check - Report check
- logs - Logs
- health_checks - Health checks
- endpoints - Endpoints
- replay_vision - Replay Vision
- analytics - Product analytics
- freshdesk - Freshdesk
- freshservice - Freshservice
- front - Front
- gorgias - Gorgias
- kustomer - Kustomer
- dixa - Dixa
- plain - Plain
- gitlab - GitLab
- gitea - Gitea
- shortcut - Shortcut
- sentry - Sentry
- rollbar - Rollbar
- bugsnag - Bugsnag
- honeybadger - Honeybadger
- raygun - Raygun
- snyk - Snyk
- sonarqube - SonarQube
- semgrep - Semgrep
- rapid7_insightvm - Rapid7 InsightVM
- featurebase - Featurebase
- frill - Frill
- aha - Aha
- uservoice - UserVoice
- productboard - Productboard
- canny - Canny
- asknicely - AskNicely
- retently - Retently
- appfigures - Appfigures
- appfollow - AppFollow
- judgeme_reviews - Judge.me
- intercom - Intercom
- hubspot - HubSpot
- engineering_analytics - Engineering analytics
- google_search_console - Google Search Console
- session_analysis_cluster - Session analysis cluster
- evaluation_report - Evaluation report
- issue - Issue
- ticket - Ticket
- issue_created - Issue created
- issue_reopened - Issue reopened
- issue_spiking - Issue spiking
- cross_source_issue - Cross source issue
- alert_state_change - Alert state change
- health_issue - Health issue
- endpoint_execution_failed - Endpoint execution failed
- endpoint_breakdown_limit_exceeded - Endpoint breakdown limit exceeded
- scanner_finding - Scanner finding
- anomaly_investigation - Anomaly investigation
- feedback - Feedback
- review - Review
- ci_flaky_check - CI flaky check
- ci_broken_default_branch - CI broken default branch
- ci_duration_regression - CI duration regression
- search_opportunity - Search opportunity
Per-source settings as a JSON object. Keys read by the emission actionability gate on sources that define one (most data warehouse imports, and Conversations): steering (string, max 2000 characters) holds the team's preferences about this source's records in plain language: what matters, what to skip, what's out of scope. The emission actionability gate applies it when deciding which records become signals; rules apply from the next sync and nothing already emitted is retracted. default_not_actionable (boolean, default false) flips the gate's default: instead of keeping every record the steering rules don't exclude, only records that clearly match the team's preferences are kept. Other sources store these keys without reading them yet; future pipeline stages will consume the same steering text. Some sources read additional keys, for example recording_filters and sample_rate for session analysis. The Linear issue source (source_product=linear, source_type=issue) reads linear_team_ids (list of Linear team id strings, max 100): the warehouse still syncs the whole Linear workspace, but only issues from those teams become signals. Omit the key or pass an empty list to use every team. Get the ids from the Linear integration's teams endpoint.
Response
- session_replay - Session replay
- llm_analytics - LLM analytics
- github - GitHub
- linear - Linear
- jira - Jira
- zendesk - Zendesk
- conversations - Conversations
- error_tracking - Error tracking
- pganalyze - pganalyze
- signals_scout - Signals scout
- signals_check - Report check
- logs - Logs
- health_checks - Health checks
- endpoints - Endpoints
- replay_vision - Replay Vision
- analytics - Product analytics
- freshdesk - Freshdesk
- freshservice - Freshservice
- front - Front
- gorgias - Gorgias
- kustomer - Kustomer
- dixa - Dixa
- plain - Plain
- gitlab - GitLab
- gitea - Gitea
- shortcut - Shortcut
- sentry - Sentry
- rollbar - Rollbar
- bugsnag - Bugsnag
- honeybadger - Honeybadger
- raygun - Raygun
- snyk - Snyk
- sonarqube - SonarQube
- semgrep - Semgrep
- rapid7_insightvm - Rapid7 InsightVM
- featurebase - Featurebase
- frill - Frill
- aha - Aha
- uservoice - UserVoice
- productboard - Productboard
- canny - Canny
- asknicely - AskNicely
- retently - Retently
- appfigures - Appfigures
- appfollow - AppFollow
- judgeme_reviews - Judge.me
- intercom - Intercom
- hubspot - HubSpot
- engineering_analytics - Engineering analytics
- google_search_console - Google Search Console
- session_analysis_cluster - Session analysis cluster
- evaluation_report - Evaluation report
- issue - Issue
- ticket - Ticket
- issue_created - Issue created
- issue_reopened - Issue reopened
- issue_spiking - Issue spiking
- cross_source_issue - Cross source issue
- alert_state_change - Alert state change
- health_issue - Health issue
- endpoint_execution_failed - Endpoint execution failed
- endpoint_breakdown_limit_exceeded - Endpoint breakdown limit exceeded
- scanner_finding - Scanner finding
- anomaly_investigation - Anomaly investigation
- feedback - Feedback
- review - Review
- ci_flaky_check - CI flaky check
- ci_broken_default_branch - CI broken default branch
- ci_duration_regression - CI duration regression
- search_opportunity - Search opportunity
Per-source settings as a JSON object. Keys read by the emission actionability gate on sources that define one (most data warehouse imports, and Conversations): steering (string, max 2000 characters) holds the team's preferences about this source's records in plain language: what matters, what to skip, what's out of scope. The emission actionability gate applies it when deciding which records become signals; rules apply from the next sync and nothing already emitted is retracted. default_not_actionable (boolean, default false) flips the gate's default: instead of keeping every record the steering rules don't exclude, only records that clearly match the team's preferences are kept. Other sources store these keys without reading them yet; future pipeline stages will consume the same steering text. Some sources read additional keys, for example recording_filters and sample_rate for session analysis. The Linear issue source (source_product=linear, source_type=issue) reads linear_team_ids (list of Linear team id strings, max 100): the warehouse still syncs the whole Linear workspace, but only issues from those teams become signals. Omit the key or pass an empty list to use every team. Get the ids from the Linear integration's teams endpoint.
Changes
No recorded changes to this operation across all 1 revision of this API.