These objects represent the accounts (owned by employees) in your organization.
Push Security REST API (v1)
The Push Security REST API provides programmatic access to the administrative functionality of the Push platform. This API adheres to RESTful principles, featuring resource-oriented URLs that are predictable and easy to navigate.
The API uses JSON-formatted request bodies and responses along with standard HTTP response codes, authentication methods, and HTTP verbs.
Rate limits are in place to ensure consistent performance for all users.
To interact with the Push Security API, you'll need an API key for authentication. To create or manage your API keys, go to the Settings page in the Push admin console.
When generating a new key, you have two permission levels to choose from: Read only and Full access. A Read only key lets you make GET requests, while Full access allows for all types of requests.
To authenticate your API requests, include a header named x-api-key and set its value to your API key.
All API calls must be made over HTTPS.
The Push Security API enforces rate limiting to ensure equitable access and maintain performance. Each user is permitted up to 10 API requests per second, with a temporary burst capacity that allows an additional 10 requests for brief intervals.
If you surpass these limits, the API will return a 429 status code as an indication.
The Push Security API uses standard HTTP response codes to signal the outcome of an API call. Here's what you need to know:
2xx codes: These indicate that your request was successful.
4xx codes: A client-side issue, usually because something is missing or incorrect in your request.
5xx codes: These suggest a problem on our end, although these occurrences are infrequent.
| HTTP Code | Description |
|---|---|
| 200 OK | Your request was successfully processed. |
| 400 Bad Request | Your request is missing something or is incorrect. Double-check your parameters. |
| 429 Too Many Requests | You've exceeded the rate limits. Consider implementing exponential backoffs in your API calls. |
| 500 Server Error | Something's not right on our end. |
- https://api.pushsecurity.com/v1/detections/{id}
- curl
- Python
- Node.js
curl -i -X GET \
'https://api.pushsecurity.com/v1/detections/{id}' \
-H 'x-api-key: YOUR_API_KEY_HERE'OK
Identifier for the employee that triggered the detection.
This object represents an employee in your organization.
Unique identifier for the employee
Primary email address of the employee
Department - as provided by connected API integrations
When this employee was created, formatted as a UNIX timestamp (in seconds)
Identifier of the browser that was used when the detection was triggered.
The type of detection
The response for the detection
When the detection was created. Formatted as a UNIX timestamp (in seconds).
The classification of the detection.
The events associated with the detection.
Identifier of the detection event.
When the event was created. Formatted as a UNIX timestamp (in seconds).
The type of detection event.
Identifier of the account that the detection event is associated with.
The type of app that the detection event is associated with.
All possible ENUM values for control modes.
The description of the detection event. Note: this is subject to change and should not be used to match on this object.
The response for the detection event.
The email associated with the account related to the detection event.
The URL that the detection event was triggered on.
The legitimate login page URL that was cloned.
The metadata associated with the detection event.
{ "id": "c478966c-f927-411c-b919-179832d3d50c", "employeeId": "37cda962-7e78-49bc-8721-1becd16276a3", "employee": { "id": "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0", "email": "john.hill@example.com", "firstName": "John", "lastName": "Hill", "department": "Security Engineering", "location": "New York", "licensed": true, "chatopsEnabled": true, "creationTimestamp": 1698669223 }, "browserId": "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0", "severity": "LOW", "detectionType": "PHISHING", "response": "BLOCKED", "creationTimestamp": 1698604061, "archived": true, "classification": "FALSE_POSITIVE", "events": [ { "id": "c478966c-f927-411c-b919-179832d3d50c", "creationTimestamp": 1698604061, "detectionEventType": "PHISHING_TOOL_DETECTED", "accountId": "37cda962-7e78-49bc-8721-1becd16276a3", "appType": "PUSH_SECURITY", "phishingToolIndicator": "AITM_TOOL_EVILGINX_01", "controlMode": "INFORM", "description": "Phishing attempt detected", "clonedLoginPageIndicator": "MICROSOFT_01", "response": "BLOCKED", "email": "john.hill@example.com", "url": "https://example.com/phishing", "referrerUrl": "https://mail.google.com", "clonedLoginPageUrls": [ "https://example.com/phishing" ], "sourceIpAddress": "8.158.25.38", "metadata": "{\"source_type\": \"Telegram\", \"breach_type\": \"Stealer Malware Logs\", \"breach_publication_date\": \"2025-04-01\"}", "experimental": false } ] }
- https://api.pushsecurity.com/v1/detections/{id}
- curl
- Python
- Node.js
curl -i -X PATCH \
'https://api.pushsecurity.com/v1/detections/{id}' \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-d '{}'OK
Identifier for the employee that triggered the detection.
Identifier of the browser that was used when the detection was triggered.
The type of detection.
The response to the detection.
The classification of the detection.
When the detection was created. Formatted as a UNIX timestamp (in seconds).
{ "id": "c478966c-f927-411c-b919-179832d3d50c", "employeeId": "37cda962-7e78-49bc-8721-1becd16276a3", "browserId": "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0", "severity": "HIGH", "detectionType": "PHISHING", "response": "BLOCKED", "classification": "FALSE_POSITIVE", "creationTimestamp": 1698604061, "archived": true }