Disconnect the plugin user
POST /logout
Optional reference path for manifest logoutUrl. The browser directly POSTs an object whose optional jwtToken is its App Connect CRM-session token, not the plugin bearer. The value can be absent, and a separately hosted plugin generally cannot validate it; treat it as opaque and secret and use a trusted plugin-owned correlation or session mechanism. Ambient shared Axios headers are not a supported identity contract. The UI changes to logged out only when the response body contains successful: true. Restrict CORS appropriately.
Operation ID: logoutPluginUser
Authorization: None
Request body
Browser logout body. jwtToken is an optional App Connect CRM-session token, not the plugin bearer credential; it can be omitted and must be treated as secret and opaque.
Required: Yes
Content type: application/json
Schema: PluginLogoutRequest
{
"jwtToken": "app-connect-user-session-token"
}
Responses
| Status | Description | Body |
|---|---|---|
200 |
Logout processing completed. The client considers the user disconnected only when the JSON body contains successful: true. | PluginAuthStateResponse |
400 |
The logout request could not be processed. | — |
500 |
The plugin could not disconnect the user. | — |