security

16 uç · /api/erp/v1/security

İstek örnekleri ucun GERÇEK metodu ve yolundan üretilir. 16 ucun elle doğrulanmış gövde örneği henüz yok; o uçlarda iskelet gövdesizdir — uydurma bir alan yazmıyoruz.

GET/api/erp/v1/security/access-denials

Access denials

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/access-denials" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/access-rules

List access rules

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/access-rules" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

POST/api/erp/v1/security/access-rules

Add access rule

Oturum

İstek

curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/security/access-rules" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

DELETE/api/erp/v1/security/access-rules/{id}

Remove access rule

OturumYol parametresi: id

İstek

curl -X DELETE "https://{slug}.erp.blesyum.app/api/erp/v1/security/access-rules/<id>" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/api-keys

List api keys

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/api-keys" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

POST/api/erp/v1/security/api-keys

Issue api key

Oturum

İstek

curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/security/api-keys" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

DELETE/api/erp/v1/security/api-keys/{id}

Revoke api key

OturumYol parametresi: id

İstek

curl -X DELETE "https://{slug}.erp.blesyum.app/api/erp/v1/security/api-keys/<id>" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

POST/api/erp/v1/security/api-keys/{id}/rotate

Rotate api key

OturumYol parametresi: id

İstek

curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/security/api-keys/<id>/rotate" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/api-keys/usage

Api key usage

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/api-keys/usage" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/delegations

List delegations

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/delegations" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

POST/api/erp/v1/security/delegations

⭐ Vekâlet için AYRI bir izin aranmaz: kullanıcı ancak KENDİ tuttuğu izinleri

Oturum

devredebilir (aşağıdaki süzgeç), dolayısıyla devir bir yetki YÜKSELTMESİ olamaz. erp.security.manage şartı koysaydık, kendi onay yetkisini tatilde devretmek isteyen sıradan bir muhasebeci bunu yapamazdı — özelliğin varlık sebebi buydu.

İstek

curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/security/delegations" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

DELETE/api/erp/v1/security/delegations/{id}

Revoke delegation

OturumYol parametresi: id

İstek

curl -X DELETE "https://{slug}.erp.blesyum.app/api/erp/v1/security/delegations/<id>" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/field-policies

List field policies

Oturum

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/field-policies" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

POST/api/erp/v1/security/field-policies

Upsert field policy

Oturum

İstek

curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/security/field-policies" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

DELETE/api/erp/v1/security/field-policies/{id}

Remove field policy

OturumYol parametresi: id

İstek

curl -X DELETE "https://{slug}.erp.blesyum.app/api/erp/v1/security/field-policies/<id>" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

GET/api/erp/v1/security/my-permissions

Kullanıcının etkin izinleri — kendi izinleri ve VEKÂLETLE gelenler AYRI listelenir.

Oturum

⭐ Ayrı listelemek denetim sorusudur: "bu işlemi yapabiliyor olmam benim yetkim mi, bana devredilen mi" sorusunun cevabı kullanıcıya da görünmeli.

İstek

curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/security/my-permissions" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"

Yanıt

{
  "data": "…",
  "trace_id": "01JC…"
}

Bu sayfa işine yaradı mı?

Hâlâ takıldın mı? Destek al