Create ModSecurity rule
POST/api/v3/hostings/:hosting_id/modsecurity/rules
Required scopes: hosting:write
Disables the ModSecurity rule rule_number on the hosting, so that ModSecurity no longer applies it, and returns the rule with included true. Responds 200 instead of 201 when the hosting already had the rule, found by a scan or added before
Request
Responses
- 200
- 201
- 400
- 401
- 403
- 404
- 429
- 500
The rule was already in the firewall of the hosting
Created
Response Headers
URL of the created resource
The request is not valid: error 1000 with the errors for each field in meta.errors, error 1001 (or 1) for other invalid input
The access token is missing, invalid, expired or revoked (error 1100): request a new token and retry once
The access token is valid but not enough: missing scope (error 1101), token for the other API (error 1102), missing permission, feature not included in the plan, operation not available to sub-accounts, internal API without administrator privileges or IP address not allowed (error 1601). A new token does not change the result
The resource does not exist or does not belong to the account (error 1200)
Too many requests (error 1300): retry after the seconds in the Retry-After header
Response Headers
Seconds to wait before retrying
Unexpected server error (error 1500)