Parameters
JSON body
Request body
application/jsoneventIdstringRequiredExternal event code identifier.
/bff/calendar/event-retry-access
Runs the same passcode-generation pipeline that the cron uses (connectPasscodeWithCalendarEvent). Returns the resulting lifecycle status: ready (primary code created), fallback_backup (gateway still offline, the lock's backup code is now linked), or failed (primary failed and no usable backup). Idempotent — safe to retry from the UI as a "fix it" button.
Calendar EventpostBffCalendarEvent-retry-access
Response schema
1 status code documented
200Success
statusstringRequiredFinal lock_access_status after this attempt: one of ready, fallback_backup, failed, manual_override, pending.
failureReasonstringOptionalUnderlying error message when status=failed.
passcodeIdnumberOptionalInternal id of the linked passcode (when present).
Response example
application/json{
"status": "example_status",
"failureReason": "example_failureReason",
"passcodeId": 0
}Request example
POST /bff/calendar/event-retry-access
curl -X POST "https://api.bizkithub.com/bff/calendar/event-retry-access" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"eventId": "example_eventId"
}'Need an API key?
All BizKitHub public API endpoints require authentication via API key.