Number Shield & stats
Set stricter limits
PUT
/v2/numbers/{numberId}/limits- Scope:
numbers:write - Idempotency-Key:optional
- changes settings
Applied on every send of the number on top of the Number Shield; the stricter value wins.
Parameters
Path
| Name | Type | Constraints | Description |
|---|---|---|---|
numberIdrequired | Typestring | Constraints— | DescriptionNumber id (GET /v2/numbers). |
Headers
| Name | Type | Constraints | Description |
|---|---|---|---|
Idempotency-Keyoptional | Typestring | Constraints≤ 191 chars | DescriptionYour unique id for this operation (≤ 191 visible ASCII). A retry with the same key and body returns the first answer with Idempotent-Replayed: true — it never runs twice. Kept 24 h. |
X-Request-Idoptional | Typestring | Constraints— | DescriptionOptional: your own request id, echoed back (otherwise we generate req_…). Quote it to support. |
Body
| Name | Type | Constraints | Description |
|---|---|---|---|
maxPerDayoptional | Typeinteger | null | Constraints≥ 1 | DescriptionYour own cap per local day (all message classes). null removes it. Can only make sending stricter. |
maxPerHouroptional | Typeinteger | null | Constraints≥ 1 | DescriptionYour own cap per local hour. null removes it. |
minGapSecondsoptional | Typeinteger | null | Constraints1–3600 | DescriptionMinimum seconds between two sends of the number (1–3600). The longer of yours and the Shield’s wins. |
Request
curl -X PUT "https://mursilat.com/api/v2/numbers/cm1abcd2345efgh6789ijkl/limits" \
-H "Authorization: Bearer $WASLA_API_KEY" \
-H "Idempotency-Key: order-1042-confirm" \
-H "Content-Type: application/json" \
-d '{
"maxPerDay": 150,
"maxPerHour": 20,
"minGapSeconds": 30
}'const res = await fetch('https://mursilat.com/api/v2/numbers/cm1abcd2345efgh6789ijkl/limits', {
method: 'PUT',
headers: {
Authorization: `Bearer ${process.env.WASLA_API_KEY}`,
'Idempotency-Key': 'order-1042-confirm',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"maxPerDay": 150,
"maxPerHour": 20,
"minGapSeconds": 30
}),
});
const data = await res.json();
if (!res.ok) throw new Error(`${data.error.code}: ${data.error.message}`);
console.log(data);import os
import requests
headers = {"Authorization": f"Bearer {os.environ['WASLA_API_KEY']}", "Idempotency-Key": "order-1042-confirm"}
res = requests.put(
"https://mursilat.com/api/v2/numbers/cm1abcd2345efgh6789ijkl/limits",
headers=headers,
json={
"maxPerDay": 150,
"maxPerHour": 20,
"minGapSeconds": 30
},
timeout=30,
)
data = res.json()
if not res.ok:
raise RuntimeError(f"{data['error']['code']}: {data['error']['message']}")
print(data)<?php
$ch = curl_init('https://mursilat.com/api/v2/numbers/cm1abcd2345efgh6789ijkl/limits');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'PUT',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('WASLA_API_KEY'),
'Idempotency-Key: order-1042-confirm',
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => json_encode([
'maxPerDay' => 150,
'maxPerHour' => 20,
'minGapSeconds' => 30
], JSON_UNESCAPED_UNICODE),
]);
$data = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
if ($status >= 400) { throw new Exception($data['error']['code'] . ': ' . $data['error']['message']); }
print_r($data);{
"maxPerDay": 150,
"maxPerHour": 20,
"minGapSeconds": 30
}Response
200Example
{
"numberId": "cm1abcd2345efgh6789ijkl",
"maxPerDay": 150,
"maxPerHour": 20,
"minGapSeconds": 30,
"updatedAt": "…"
}Response schema
Fields of the example answer. Expand objects and arrays.
responseobject5 fields
- numberIdstring "cm1abcd2345efgh6789ijkl"
- maxPerDayinteger 150
- maxPerHourinteger 20
- minGapSecondsinteger 30
- updatedAtstring "…"
Errors
Besides the authentication, rate-limit and validation errors every endpoint can return:
- 400LIMITS_INVALIDInvalid limits.
Number Shield & behaviour
Your limits are extra counters on every send of the number. They can only make sending stricter — the Number Shield caps always stay.
Try it
Send this request from your browser to the Mursilat API.
documented examplePreview — this copy of the docs isn’t on mursilat.com, so the console shows the documented example instead of calling the API.
Real requests use your real number and plan: they can send WhatsApp messages, spend quota and delete data. (changes settings)
Kept only in this tab’s memory: never saved, never put in the URL, sent only to mursilat.com. Reloading the page forgets it.