Spend Enforcement Check

GET

/metering-service/api/v2/organizations/{organization_id}/spend/users/{user_id}/enforcement

Checks whether a user may run a query given their organization's spend limits, and returns an ALLOW / WARN / BLOCK decision.

Every decision, including a block, returns HTTP 200. A deny is expressed as allowed=false / action=BLOCK in the body, never as a 4xx/5xx. WARN is allowed=true (the user is past a soft limit but may proceed). A user who has not reached any limit is allowed.

user_message is a sentence for the end user describing the decision, or null when there is nothing to report.

Requires only the service key; no user token is needed.

Path Parameters

organization_id: The Ejento AI organization ID.

user_id: The Ejento user the query is attributed to.

Returns

JSON Response: the admission decision (allowed, action, reason, billing_period, resets_at, user_message) in a success envelope.

Current Version

2.0.0

Request

Path Params

Header Params

Responses

🟢200

application/json

Successful Response

Bodyapplication/json

🟠401

🟠403

🟠422

🔴500

Request Example

Shell

JavaScript

Java

Swift

curl --location --globoff 'https:///metering-service/api/v2/organizations//spend/users//enforcement' \
--header 'Ocp-Apim-Subscription-Key: ' \
--header 'Authorization: Bearer '

Response Example

200 - Example 1

{
    "success": true,
    "message": "string",
    "data": {
        "allowed": true,
        "action": "ALLOW",
        "reason": "USER_LIMIT",
        "billing_period": "string",
        "resets_at": "2019-08-24T14:15:22.123Z",
        "user_message": "string"
    }
}

Get Spend Limits

Set Org Spend Limit