Wambesha

API संदर्भ केवल अंग्रेज़ी में उपलब्ध है।

Accountrequests

GET/v1/account/requests

केवल कॉल कोटा

The last requests made with your keys - method, endpoint, status, latency - kept for 7 days. Never charged.

पैरामीटर

limitintegerवैकल्पिकडिफ़ॉल्ट: 50
Requests to return, 1-200, newest first. Default 50.
और
How many recent requests to return, newest first, 1-200. Default 50.
errorsOnlybooleanवैकल्पिकडिफ़ॉल्ट: false
true returns only non-2xx responses.
और
Narrow to non-2xx responses, which is the reason most people open this.

रिस्पॉन्स फ़ील्ड

itemsRequestTailEntry[]
retentionDaysinteger · int64
errorsOnlyboolean

रिस्पॉन्स हेडर

X-Request-ID
The id of this request, on every response - success or error. Quote it to support: it is how we find your request in our logs. An X-Request-ID you send is honoured and echoed back, so you can use your own; otherwise we generate one. /v1 error bodies carry no trace id of their own.
X-Quota-Reset
RFC 3339 instant at which the billing period rolls. Present on every response to a request whose key was metered - every 2xx, every error a handler returned, and the quota 429. Absent on a refusal that happens before metering: a missing or unknown key (401), a restricted key or a plan that does not carry the endpoint (403), a public demo-key gate refusal, and the pre-authentication flood throttle.
X-Calls-Remaining
Requests left in the period after this one, never below 0. Present whenever X-Quota-Reset is (see there for when a response carries no quota headers).
X-Verifications-Remaining
How many verifications you can still make before a limit stops you. The daily limit and the monthly allowance are counted separately; this is whichever of the two runs out first. Sent whenever X-Quota-Reset is.
X-Quota-Grace
true when THIS request fell inside the 10% grace band above a monthly ceiling. A grace request is served and is not billed; treat true as "back off now", not as headroom. Always true or false, never absent when the other quota headers are present.
Retry-After429
Seconds to wait before retrying. On every 429 - the quota hard stop, the public demo key's limits, and the pre-authentication flood throttle (which carries this header alone, because no key has been read yet).
X-Demo-Challenge-Modeकेवल डेमो कुंजी के साथ
Sent only on responses to the public demo key. The value interactive asks the documentation page to show the visible verification widget - it is sent once a browser has made more than five runs in ten minutes or has received a 429. The page then repeats the header, X-Demo-Challenge-Mode: interactive, on its next request, with the widget's token in X-Demo-Challenge. Requests made with your own key never receive it.

त्रुटियाँ

विवरण

Timestamp, endpoint, status, latency, which key, and whether a verification was spent.

Never response bodies and never full query strings. This is for debugging your own integration, not a transcript of it. Retention is short and is stated in the response rather than left to be discovered.

इसे आज़माएं

डेमो कुंजी लोड हो रही है…

curl "https://api.wambesha.com/v1/account/requests" \
  -H "Authorization: Bearer YOUR_API_KEY"

उदाहरण

{
  "items": [
    {
      "at": "2026-09-27T16:21:33Z",
      "endpoint": "/v1/account/usage",
      "method": "GET",
      "status": 200,
      "latencyMs": 19,
      "keyId": "5c1d7e00-0c17-4d0c-9c17-00000000cafe",
      "verificationSpent": false,
      "errorCode": null
    },
    {
      "at": "2026-09-27T16:21:33Z",
      "endpoint": "/v1/account",
      "method": "GET",
      "status": 200,
      "latencyMs": 26,
      "keyId": "5c1d7e00-0c17-4d0c-9c17-00000000cafe",
      "verificationSpent": false,
      "errorCode": null
    }
  ],
  "retentionDays": 7,
  "errorsOnly": false
}