ERP

statement-schedules

5 endpoints · /api/erp/v1/statement-schedules

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.

GET/api/erp/v1/statement-schedules

Zamanlayıcıları listele. erp.parties.view.

Oturum
İstek
curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/statement-schedules" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"
Yanıt
{
  "data": "…",
  "trace_id": "01JC…"
}
POST/api/erp/v1/statement-schedules

Periyodik ekstre zamanlayıcısı oluştur. erp.parties.manage.

Oturum
İstek
curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/statement-schedules" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"
Yanıt
{
  "data": "…",
  "trace_id": "01JC…"
}
GET/api/erp/v1/statement-schedules/{id}

Tek zamanlayıcı getir. erp.parties.view.

OturumYol parametresi: id
İstek
curl -X GET "https://{slug}.erp.blesyum.app/api/erp/v1/statement-schedules/<id>" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"
Yanıt
{
  "data": "…",
  "trace_id": "01JC…"
}
POST/api/erp/v1/statement-schedules/{id}/active

Zamanlayıcıyı aktif/pasif yap. erp.parties.manage.

OturumYol parametresi: id
İstek
curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/statement-schedules/<id>/active" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"
Yanıt
{
  "data": "…",
  "trace_id": "01JC…"
}
POST/api/erp/v1/statement-schedules/tick

Due zamanlayıcıları tikle (worker simülasyonu; canlı cron-tetik = EF15). erp.parties.manage.

Oturum
İstek
curl -X POST "https://{slug}.erp.blesyum.app/api/erp/v1/statement-schedules/tick" \
  -H "Authorization: Bearer <oturum-token>" \
  -H "Accept: application/json"
Yanıt
{
  "data": "…",
  "trace_id": "01JC…"
}
Bu sayfa işine yaradı mı?