Test the credential already stored for a feed connection, changing
curl --request POST \ --url http://localhost:3001/admin/feed-connections/string/credentials/test \ --header 'Authorization: Bearer <token>'import requests
url = "http://localhost:3001/admin/feed-connections/string/credentials/test"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.json())use reqwest;
#[tokio::main]pub async fn main() { let url = "http://localhost:3001/admin/feed-connections/string/credentials/test";
let mut headers = reqwest::header::HeaderMap::new(); headers.insert("Authorization", "Bearer <token>".parse().unwrap());
let client = reqwest::Client::new(); let response = client.post(url) .headers(headers) .send() .await;
let results = response.unwrap() .json::<serde_json::Value>() .await .unwrap();
dbg!(results);}Nothing. See test_broker_connection_credentials — identical shape,
backed by load_feeds/test_feed instead of load_brokers/test_broker.
Unlike FIX, a stored Databento key genuinely gets tested here: test_feed
runs the same connect-and-auth handshake as the save path’s pre-write
check, so this can return a real pass or fail rather than NotTestable.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Feed connection code
Responses
Section titled “Responses”Test outcome for the stored credential
Response body for POST .../credentials/test.
object
Present on anything short of a clean pass: the broker’s rejection
reason, or why nothing was attempted. Never derived from submitted
input — see TestOutcome’s own doc comment.
Only meaningful when tested is true: whether it passed.
Whether a check was actually attempted — false for FIX.
Example generated
{ "message": "example", "ok": true, "tested": true}No credential is stored for this connection
Not found
The credential store could not be read, or the stored credential could not be decrypted