MANSOQ Knowledge
← Technical API reference

Backend resource · STATIC DECLARATIONS

Sandbox API reference · mansoq-experience-be

Static source contract for Sandbox: 3 declared or inherited operation mappings, schema/field evidence and authorization/refusal references. Deployment and behavioral review remain explicit.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Declared route and availability

This resource is declared in mansoq-experience-be at /api/{installed_plugin_prefix}/sandbox/. plugin/local mount; actual prefix and enablement require deployment verification A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

Method Path Action Evidence
POST /api/{installed_plugin_prefix}/sandbox/ create declared/inherited method
GET /api/{installed_plugin_prefix}/sandbox/{external_id}/ retrieve declared/inherited method
DELETE /api/{installed_plugin_prefix}/sandbox/{external_id}/ destroy declared/inherited method

create · POST

POST /api/{installed_plugin_prefix}/sandbox/ — action create. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location Parameter Type Required
deployment mount installed_plugin_prefix deployment-selected mount prefix true

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

Location Field Declared/inferred read type Requiredness evidence
query is_facility_empty not declared at read site not established
body is_facility_empty not declared at read site not established
body facility_name not declared at read site not established
query facility_name not declared at read site not established

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Class policy declarations: permission_classes: IsSuperUser; authentication_classes: BasicAuthentication, SessionAuthentication.

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

retrieve · GET

GET /api/{installed_plugin_prefix}/sandbox/{external_id}/ — action retrieve. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location Parameter Type Required
deployment mount installed_plugin_prefix deployment-selected mount prefix true
path external_id router lookup string; semantic ID validation requires handler/schema review true

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Class policy declarations: permission_classes: IsSuperUser; authentication_classes: BasicAuthentication, SessionAuthentication.

destroy · DELETE

DELETE /api/{installed_plugin_prefix}/sandbox/{external_id}/ — action destroy. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location Parameter Type Required
deployment mount installed_plugin_prefix deployment-selected mount prefix true
path external_id router lookup string; semantic ID validation requires handler/schema review true

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Class policy declarations: permission_classes: IsSuperUser; authentication_classes: BasicAuthentication, SessionAuthentication.

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

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.

Pinned source evidence

Links require access to the private source repository.