APIリファレンスは英語のみで提供されています。
https://api.
v1 のすべてのエンドポイントを、パラメーター、リクエストとレスポンスの例、返される可能性のあるエラーとともに掲載しています。エンドポイントの説明は英語です。
Your API key, presented as a Bearer token. Keys are per-account and carry a plan; the plan decides which endpoints answer and what your quota is. Never embed a key in a browser client — it is a credential, and a browser cannot keep one.
Authorization: Bearer $WAMBESHA_API_KEY公開デモキーに対応しているエンドポイントでは、「試してみる」のスニペットにデモキーが含まれているため、そのまま実行できます。それ以外のスニペットには、ご自身のキーが必要です。デモキーは API のお試し専用です。毎日ローテーションされ、いつでも無効化される可能性があり、本番環境では決して使用しないでください。構築するものにはすべて、ご自身のキーを使用してください。
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.
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.
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).
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.
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.
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).
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.
すべてのエラーは同じ本文を持ちます。HTTP ステータス、分岐に使える安定したコード、人が読むためのメッセージ、そして値が誤っていた場合のフィールドエラーです。お問い合わせの際に特定のリクエストをお伝えいただくには、そのレスポンスの X-Request-ID ヘッダーをご利用ください。
記録されたレスポンス
GET/v1/search
{
"timestamp": "2026-09-27T12:00:00Z",
"status": 400,
"error": "Bad Request",
"message": "Enter at least 2 characters to search.",
"path": "/v1/search",
"errors": [
{
"field": "q",
"rejectedValue": "a",
"message": "Enter at least 2 characters to search."
}
],
"metadata": {
"errorCode": "CATALOG_SEARCH_QUERY_TOO_SHORT"
},
"code": "validation-failed"
}400
v1 に互換性を損なう変更が入ることはありません。v1 の中では、パス、必須パラメーター、レスポンスのフィールドは変わりません。新しいフィールドやエンドポイントが追加されることはあり、その場合はまず変更履歴で告知します。 バージョン管理の仕組み
/v1/discover filters on. Spends no verification.missing rather than failing the call. Spends no verification.