← Technical API reference

Backend resource · STATIC DECLARATIONS

Accept Transfer API reference · mansoq-odoo-connector

Static source contract for Accept Transfer: 2 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-odoo-connector at /api/care/cash/transfer/{transfer_id}/accept. service-local decorator; application/router mount prefix and deployment base require verification A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

Method Path Action Evidence
PUT /api/care/cash/transfer/{transfer_id}/accept accept_transfer service HTTP decorator
POST /api/care/cash/transfer/{transfer_id}/accept accept_transfer service HTTP decorator

accept_transfer · PUT

Accept a pending transfer.

PUT /api/care/cash/transfer/{transfer_id}/accept — action accept_transfer. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location Parameter Type Required
path transfer_id integer true

Route policy declarations: type=http, auth=public, csrf=false. These declaration flags do not replace handler, middleware, API-key or deployment security review.

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

Location Field Declared/inferred read type Requiredness evidence
header Authorization 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.

accept_transfer · POST

Accept a pending transfer.

POST /api/care/cash/transfer/{transfer_id}/accept — action accept_transfer. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location Parameter Type Required
path transfer_id integer true

Route policy declarations: type=http, auth=public, csrf=false. These declaration flags do not replace handler, middleware, API-key or deployment security review.

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

Location Field Declared/inferred read type Requiredness evidence
header Authorization 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.

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.