SDK - Enforcement Update
Endpoint
/i/sdk-config/update-enforcement
Overview
Updates SDK enforcement overrides for an app.
Authentication
Countly API supports three authentication methods:
api_key=YOUR_API_KEYauth_token=YOUR_AUTH_TOKENcountly-token: YOUR_AUTH_TOKEN
Permissions
Requires sdk Update permission.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | String | Yes (or use auth_token) | API key for authentication. |
auth_token | String | No | Auth token as query parameter or countly-token header. |
app_id | String | Yes | App id. |
enforcement | String (JSON Object) or Object | Yes | Enforcement object to save. |
Response
Success Response
{
"result": "Success"
}
Response Fields
| Field | Type | Description |
|---|---|---|
result | String | Success when enforcement is saved. |
Error Responses
400
{
"result": "Missing parameter \"app_id\""
}
400
{
"result": "Error parsing enforcement"
}
400
{
"result": "Wrong enforcement format"
}
500
{
"result": "Error saving enforcement to database"
}
Behavior/Processing
- Parses
enforcementwhen provided as JSON string. - Removes unknown keys and persists only valid SDK option keys.
Database Collections
| Collection | Used for | Data touched by this endpoint |
|---|---|---|
countly_out.sdk_enforcement | Enforcement storage | Upserts app enforcement as { _id: app_id, enforcement: ... }. |
Examples
Update enforcement overrides
/i/sdk-config/update-enforcement?api_key=YOUR_API_KEY&app_id=6991c75b024cb89cdc04efd2&enforcement={"tracking":false,"crt":false,"eqs":100}
Related Endpoints
Last Updated
2026-03-05