MANSOQ Knowledge
← Technical API reference

Backend resource · STATIC DECLARATIONS

Consent API reference · mansoq-abdm-teleicu

Static source contract for Consent: 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-abdm-teleicu at /api/{installed_plugin_prefix}/consent/. 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
GET /api/{installed_plugin_prefix}/consent/ list standard external DRF mixin; library behavior review pending
POST /api/{installed_plugin_prefix}/consent/ create declared/inherited method
GET /api/{installed_plugin_prefix}/consent/{pk}/ retrieve standard external DRF mixin; library behavior review pending

list · GET

GET /api/{installed_plugin_prefix}/consent/ — action list. 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

serializer: ConsentRequestSerializer. Declared fields below; inherited fields are retained in the schema inventory.

Field Type Required Constraints
id serializers.CharField framework default read_only: true
encounter_id serializers.CharField framework default read_only: 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: IsAuthenticated.

create · POST

POST /api/{installed_plugin_prefix}/consent/ — 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

serializer: ConsentRequestSerializer. 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.

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: IsAuthenticated.

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

Declared refusal/error evidence: CaptchaRequiredException (dynamic detail; inspect source).

retrieve · GET

GET /api/{installed_plugin_prefix}/consent/{pk}/ — 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 pk router lookup string; semantic ID validation requires handler/schema review true

serializer: ConsentRequestSerializer. 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.

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: IsAuthenticated.

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.