Availability Exceptions API reference · mansoq-core

Declared route and availability

This resource is declared in mansoq-core at /api/v1/facility/{facility_external_id}/schedule_exceptions/. verified core mount in config/urls.py A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

list · GET

GET /api/v1/facility/{facility_external_id}/schedule_exceptions/ — action list. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

response: AvailabilityExceptionReadSpec. Declared fields below; inherited fields are retained in the schema inventory.

Observed authorization checks: can_list_schedule. Helper/queryset evidence is included; this is not proof of complete security review.

Declared refusal/error evidence: ValidationError: resource_type and resource_id are required; PermissionDenied: You do not have permission to list schedule.

create · POST

POST /api/v1/facility/{facility_external_id}/schedule_exceptions/ — action create. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

request: AvailabilityExceptionWriteSpec. Declared fields below; inherited fields are retained in the schema inventory.

response: AvailabilityExceptionReadSpec. Declared fields below; inherited fields are retained in the schema inventory.

The declared field table is shown at its first occurrence in this reference; this operation links the same schema.

Observed authorization checks: can_list_schedule, can_write_schedule. Helper/queryset evidence is included; this is not proof of complete security review.

Declared refusal/error evidence: ValidationError: resource_type and resource_id are required; PermissionDenied: You do not have permission to list schedule; PermissionDenied: You do not have permission to create schedule; ValidationError: There are bookings during this exception.

retrieve · GET

GET /api/v1/facility/{facility_external_id}/schedule_exceptions/{external_id}/ — action retrieve. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

response: AvailabilityExceptionReadSpec. Declared fields below; inherited fields are retained in the schema inventory.

The declared field table is shown at its first occurrence in this reference; this operation links the same schema.

Observed authorization checks: can_list_schedule. Helper/queryset evidence is included; this is not proof of complete security review.

Declared refusal/error evidence: ValidationError: resource_type and resource_id are required; PermissionDenied: You do not have permission to list schedule; PermissionDenied: You do not have permission to update schedule.

destroy · DELETE

DELETE /api/v1/facility/{facility_external_id}/schedule_exceptions/{external_id}/ — action destroy. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

Observed authorization checks: can_list_schedule, can_write_schedule. Helper/queryset evidence is included; this is not proof of complete security review.

Explicit response statuses in observed code: status.HTTP_204_NO_CONTENT. Other branches/framework exception handling may differ.

Declared refusal/error evidence: ValidationError: resource_type and resource_id are required; PermissionDenied: You do not have permission to list schedule; PermissionDenied: You do not have permission to update schedule.

upsert · POST

POST /api/v1/facility/{facility_external_id}/schedule_exceptions/upsert/ — action upsert. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

Observed authorization checks: can_list_schedule, can_write_schedule. Helper/queryset evidence is included; this is not proof of complete security review.

Explicit response statuses in observed code: 400. Other branches/framework exception handling may differ.

Declared refusal/error evidence: RestFrameworkValidationError: Invalid request data; RestFrameworkValidationError: No datapoints provided; RestFrameworkValidationError: Too many datapoints provided; ValidationError: resource_type and resource_id are required; PermissionDenied: You do not have permission to list schedule; PermissionDenied: You do not have permission to create schedule; ValidationError: There are bookings during this exception.

Conditional gates: conditional/computed expression; inspect pinned declaration comparison settings.MAX_DATAPOINTS_PER_UPSERT.

Integration review checklist

Confirm the installed route and full schema; review authentication, organization/facility scoping, all accepted fields, value-state and date/time semantics, idempotency, pagination, response/exception branches and the allowed correction/reversal workflow. Test positive and negative cases with synthetic data. This source reference does not establish external certification or replace an illustrated user procedure.