Using

`GET /config` — effective configuration of the running process. Admin only.

applies to v0.5.1

GET

/store-api/config

const url = 'https://example.com/store-api/config';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://example.com/store-api/config \
  --header 'Authorization: Bearer <token>'

The path carries no {domain} segment, so extract_domain returns None and the auth layer’s None-branch requires an admin role. The admin API key never appears in the body — redaction happens at the field level (AdminEntry.api_key’s #[serde(skip_serializing)] in config.rs), not in this handler.

Authorizations

bearer_auth

Responses

200

Config_path (resolved path, always set), config_file_loaded (whether a file existed there), and config (the effective LuraConfig — see config.rs for field docs)

application/json

object

Example ^generated

{}

401

Unauthorized

text/plain

string

403

Forbidden — Admin only