What the developer wrote
Authored by Nicolas Dorier
Update docs
What changed, and why it matters
This commit only updates the API documentation file (a Swagger/OpenAPI template) to add a description for a newly documented setting called 'storeQuota'. It does not change any server code, permissions, or behavior. There is no security issue in this change.
No action needed. This is a non-functional documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one property, ‘storeQuota’, to the user schema in BTCPayServer/wwwroot/swagger/v1/swagger.template.users.json. It is a nullable number described as a per-user override for the maximum number of stores a user can create. This is purely a documentation update for an existing API field and contains no executable code changes.
Changed components
BTCPayServer/wwwroot/swagger/v1/swagger.template.users.jsonInspect captured patch +5 / −0
diff --git a/BTCPayServer/wwwroot/swagger/v1/swagger.template.users.json b/BTCPayServer/wwwroot/swagger/v1/swagger.template.users.json
index 1ae38b0..6486cc4 100644
--- a/BTCPayServer/wwwroot/swagger/v1/swagger.template.users.json
+++ b/BTCPayServer/wwwroot/swagger/v1/swagger.template.users.json
@@ -547,6 +547,11 @@
"type": "boolean",
"description": "True if the instance requires approval to log in"
},
+ "storeQuota": {
+ "type": "number",
+ "nullable": true,
+ "description": "Per-user override for the max number of stores this user can create. Null means the server default applies"
+ },
"created": {
"type": "number",
"nullable": true,
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.