GET /v1/config/log-sources/{id}/sources

Discover available log groups, indexes, or selectors using a saved log source's credentials

Discovers what's available in the underlying log platform for a saved log source — log groups, indexes, label values, and so on — without re-sending credentials. Use this to refresh the available list when editing a source, or to spot newly created log groups since the source was last configured.

For unsaved credentials (e.g. mid-create flow), use the dashboard's Add log source form — the autocomplete there browses available log groups, indexes, or labels as you type credentials in.

Authentication

API key with config:read permission.

Endpoint

GET /v1/config/log-sources/{id}/sources

Path parameters

Param	Type	Notes
`id`	UUID	The log source id

Response

200 OK

{
  "success": true,
  "data": [
    {
      "id": "/aws/lambda/checkout-api",
      "name": "/aws/lambda/checkout-api",
      "type": "log-group"
    },
    {
      "id": "/aws/lambda/billing-worker",
      "name": "/aws/lambda/billing-worker",
      "type": "log-group"
    }
  ]
}

Field	Type	Notes
`id`	string	The value to put in `sources` when updating the log source
`name`	string	Display label (often the same as `id`)
`type`	string	Platform-specific kind (e.g. `log-group`, `index`, `label-value`)

The result is capped at 200 entries.

Always returns an array — empty if the saved source has no discoverable entries. Use the test endpoint to confirm credentials are still valid.

Error responses

Status	`error.code`	When
400	`VALIDATION_ERROR`	`id` is not a UUID
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:read`
404	`NOT_FOUND`	No log source with that id in your tenant

Example

curl https://api.sigsentry.com/v1/config/log-sources/ls_a1b2c3/sources \
  -H "Authorization: Bearer ss_secret_..."