LuckyFit Public Integration API

LuckyFit public integration API.

All endpoints are mounted under the /api prefix and require organization network-key authentication (Api-Key header). The key identifies the "network" (root organization) and may optionally restrict access to specific branches. Without a valid key the API returns 401 Unauthorized with a body of { "success": false, "session_expired": true, ... }.

Response format

Endpoints do not use HTTP status codes for business logic: on a validation error they typically return 200 OK with success: false and a message in error. There are two envelopes:

• data envelope (send_data_response): { success, data, error, total }.
• crud envelope (send_crud_response): { success, data, error, error_code, total, summary }.

Branch resolution (organization_id)

For create/update operations, if organization_id is omitted the branch is resolved automatically: if the Api-Key is restricted to exactly one branch, that branch is used; if the network has exactly one branch, that branch is used; otherwise an explicit organization_id is required.