Data sources

📄️The account's data source credentials

Owner/admin: the account's data source credentials (masked) by provider and priority, with health, the providers with their fields, and the settings

📄️Add a credential

Owner/admin: add a credential (last in its provider's order unless priority is given). Listening runs of the platform's system actor get up to 3 healthy keys per provider in order: YOUTUBE_API_KEYS, IG_GRAPH_KEYS, REDDIT_KEYS, a platform setting (JSON lists) plus the first key's YOUTUBE_API_KEY, IG_GRAPH_TOKEN + IG_BUSINESS_ACCOUNT_ID, REDDIT_CLIENT_ID + REDDIT_CLIENT_SECRET, a platform setting; the actor tries the next key on quota or invalid errors

📄️Change any of prefer_vendor

Owner/admin: change any of prefer_vendor (a project's own wins), credential_mode, pinned_credentials ({ provider: id | null }) and on_keys_exhausted. Returns the settings

📄️The order keys are tried in

Owner/admin: the order keys are tried in. `ids` first to last; the account's other keys keep their order after them. Returns the list like GET

📄️Probe the key now

Owner/admin: probe the key now and store its health. 20/min

📄️Change label, is_enabled, priority or secret fields

Owner/admin: change label, is_enabled, priority or secret fields (fields left out or empty keep their value; provider cannot change; a new secret starts healthy)

📄️Delete data source

Owner/admin: delete