home

Mobile Endpoint Security

Mobile Endpoint SecuritySecurity Service Edge
Mobile Endpoint SecuritySecurity Service Edge

Lookout Product Documentation

Find answers about using and optimizing Lookout products.

Show Contents

Mobile Endpoint Security

Mobile Risk API v2 Overview

REST Conventions

The following table describes general conventions related to the Lookout Mobile Risk API’s RESTful style:

Convention Meaning
Endpoint Endpoints use plural nouns for resource names, e.g., /events, unless existing Lookout conventions apply, e.g., /health.
Fields Fields are named using a camelcase format, e.g., emailAddress.
Dates Date values are formatted based on the ISO-8601 standard of yyyymmdd, e.g., 20170510.
Links

Where appropriate, links are shown in the

style, e.g., https://api.lookout.com/devices/1.

Objects

Objects are shown and defined using a discriminator field type as in this JSON object example:

{ 
  "type": "device",
  "id": "1",
  "platform": "Android",
  "emailAddress": "owner@example.com",
}

Last updated: September 30, 2024

lookout-footer

Legal Privacy Policy Cookie Policy Transparency Report Compliance Info Compliance Info (Gov)

© 2024 Lookout, Inc. LOOKOUT®, the Lookout Shield Design®, LOOKOUT with Shield Design® and the Lookout multi-color/multi-shaded Wingspan Design® are registered trademarks of Lookout, Inc. in the United States and other countries. DAY OF SHECURITY®, LOOKOUT MOBILE SECURITY®, and POWERED BY LOOKOUT® are registered trademarks of Lookout, Inc. in the United States. Lookout, Inc. maintains common law trademark rights in EVERYTHING IS OK, PROTECTED BY LOOKOUT, CIPHERCLOUD, and the 4 Bar Shield Design.