Appearance
Revoke a mobile device registration ​
This Mobile operation is available through DELETE /mobile/devices/{id}. Use the reference below to inspect its request contract and documented responses before connecting it to your application.
Request preparation ​
Send a DELETE request to /mobile/devices/{id} on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.
The declared request parameters are:
id(path, required): Use the type and constraints shown in the parameter reference.
No request body is declared in the current specification. Check the route and any documented parameters before sending the request rather than adding an arbitrary JSON payload.
Authentication and scope ​
The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.
Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.
Response handling ​
The documented responses for Revoke a mobile device registration are:
- 200: Revoked
- 404: Device not found
Before sending this deletion request, verify the exact resource and the consequences described for this operation. Use disposable test data for an initial integration check. Inspect the response before removing the record from your local interface, and do not assume that every delete operation has the same retention, cleanup, or recovery behavior.
If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.
Revoke a mobile device registration​
DELETE
/mobile/devices/{id}
Authorizations​
BearerAuth
JWT token from login
Type
HTTP (bearer)
or
AccessToken
Personal access token. Value: Token <your-token>
Type
API Key (header: Authorization)
Parameters​
Path Parameters
id*
Type
Requiredstring
Responses​
Revoked
application/json
JSON"device": "string"
{
 Â
}