apikeys
5 endpoints · /api/v1/apikeys
Request examples are generated from each endpoint's REAL method and path. 5 endpoints have no hand-verified body example yet; their skeleton has no body — we do not invent field names.
Issue an API key for the active tenant (API-11). The full key is returned
Oturum
**once** in secret; only its prefix is shown thereafter.
İstek
curl -X POST "https://api.blesyum.com/api/v1/apikeys" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"Yanıt
{
"data": "…",
"trace_id": "01JC…"
}Rotate an API key (API-14): revoke + reissue with the same scopes.
OturumYol parametresi:
idİstek
curl -X POST "https://api.blesyum.com/api/v1/apikeys/<id>/rotate" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"Yanıt
{
"data": "…",
"trace_id": "01JC…"
}API anahtarı kapsam kataloğu (API-12) — **kiracının lisansına göre**.
Oturum
Panelin gömülü listesinin yerini alır: o liste CRM'in data_attributes.* kapsamlarını
kaçırmıştı ve kimse fark etmemişti (ölçüldü 2026-08-20). Kapsamın tek kaynağı
blesyum_apikeys::SCOPE_CATALOG.
İstek
curl -X GET "https://api.blesyum.com/api/v1/apikeys/scopes" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"Yanıt
{
"data": "…",
"trace_id": "01JC…"
}Bu sayfa işine yaradı mı?