Print Download PDF Send Feedback

Previous

Next

Introduction

In This Section:

Accessing the API

Global Request Headers

JSON Request and Response Structure

Request Object Structure

Response Object Structure

Response Status Codes

Best Practices

The Check Point Threat Prevention API lets you use Threat Prevention products through cloud web services. The request/response API has functionality similar to Next Generation Threat Extraction (NGTX) and SandBlast appliances.

For further inquiry or information, contact Check Point Support at CheckMates - SandBlast API.

Note - On local gateways, if local API for Threat Extraction or SSL certificate is required, enable and use the API according to sk113599 and sk137032.

For more information on Check Point Threat Emulation API on local gateways, see sk167161.

General Details:

All services use the HTTP POST method, unless stated otherwise.

The body of requests and responses is in JSON format, unless stated otherwise.

All services have mandatory headers and request body fields. If you do not enter values for mandatory variables, there will be errors. Optional variables have predefined defaults.

The response to some requests includes detailed status messages in the response body.

License:

NGTX and TEX packages include the API usage license.

To evaluate the cloud service, contact Check Point for an Evaluation API Key.

On local gateways, see sk113599 to generate an API key for Threat Extraction use.