WonderFence evaluate message
POST/v2/evaluate/message
Evaluate messages with application-specific policy enforcement. Every request must identify the application with app_id; only policies assigned to that application will be applied.
app_id takes the application's UUID from the Application Inventory. If you filled in the optional Application ID field when you added the application — your own id for it — you can send that instead. An id matching neither is rejected with a 400.
API response keys:
Each violation in the response is identified by its policy's API response key. The keys available to you depend on which policies your project has, so look them up rather than hardcoding a list: in WonderSuite go to Enforcement Policies and open a policy — its API Response Key is shown under the policy title.
Request
Responses
- 200
- 400
- 401
- 403
- 408
- 429
- 503
- 504
Successful evaluation with action and detections
Bad request - validation failed
Unauthorized - invalid or missing authentication credentials
Project has reached its limit of applications created from traffic
Request timeout - operation took too long to complete
Rate limit exceeded - too many requests
Service unavailable - service temporarily unavailable
Gateway timeout - upstream service did not respond in time