Lock / Unlock Entity Record

Locks or unlocks an entity record on behalf of an installed app.

Intended for third-party app integrations: an installed app can lock a specific record of any entity it has access to (preventing further edits) or unlock it again. Send true in the lock path segment to lock the record; any other value unlocks it.

Authenticated with an OAuth bearer token. The response is always HTTP 200 with a { status, msg } object — inspect status to tell success from the two failure cases (the app is not installed/active for the site, or the record was not found).

Responses

🟢200Success

application/json

Lock/unlock outcome. Example bodies:

Locked:

{ "status": true, "msg": "Record locked successfully" }

Unlocked:

{ "status": true, "msg": "Record unlocked successfully" }

App not installed/inactive (still HTTP 200):

{ "status": false, "msg": "App is not installed or inactive" }

Record not found (still HTTP 200):

{ "status": false, "msg": "Record not found" }

Bodyapplication/json

🟠401Unauthorized

curl --location --globoff 'https://.daftara.com/v2/api/apps-manager/123/product/456/true' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ' \ --header 'apikey: ' \ --header 'Content-Type: application/json'

Lock / Unlock Entity Record

Request

Responses