cancel
Showing results for 
Search instead for 
Did you mean: 
Post a Question
Employee
Employee

SandBlast Mobile API Documnetation

If you have a customer or a partner that is interested in integrating the information about mobile device risk on their network as analysed by the SBM  solution: 

For example if a device is High/medium risk you want the user to be disabled from access the wifi network/application until the device is cleared from risk.

You can use REST API from any system to get that info. If you have a working SBM solution you can use the following attached  documents:

  1. Create_api_key.PDF - Use this to generate the CSRFtoken-Session ID pair that is required in order to call the other REST API calls.
  2. external_api.PDF - List of all API calls and the required format

Enjoy

Smiley Happy

Tags (2)
6 Replies
Employee+
Employee+

Re: SandBlast Mobile API Documnetation

Great work Yuval! Smiley Happy These APIs can be easily used for dozens of different needs!

0 Kudos
Admin
Admin

Re: SandBlast Mobile API Documnetation

Thanks for sharing.

API all the things  

0 Kudos
Employee
Employee

Re: SandBlast Mobile API Documnetation

Hello, colleagues!

We have one 3rd party MDM solution here, how can we push initial configuration to installed app, i.e. server name and registration key?

Is there any document, describing this and possible integrations with 3rd party MDMs using REST API?

0 Kudos
Employee+
Employee+

Re: SandBlast Mobile API Documnetation

Hi! Sure we can! 

Please send me an email (danieldor@checkpoint.com) and I will send you the relevant guide according to the MDM you have. We have Out of the box integration with 6 MDMs at the moment: AirWatch, MobileIron, MaaS360, Intune, BES, Xen Mobile.

D

0 Kudos
Admin
Admin

Re: SandBlast Mobile API Documnetation

Or you can post it here 🙂

0 Kudos
Employee+
Employee+

Re: SandBlast Mobile API Documnetation

Good point Moti!

What we can do is as follows:

  1. The integration will be from the MDM’s side, in which they will use our API (attached) to detect the current risk score of the device.
  2. What they can do, is to use the SBM API to pull the device health score using the email or IMEI of the device. Email or IMEI is the only unique identifier we have both in SBM and MDM sides.
  3. Using the risk score, they can decide what to do next with the device based on the “score” coming from SandBlast Mobile.

We have other third parties that use our API to do some sort of integration with our solution. This is the fastest way to integrate without developing anything from SBM side.