Skip to content
/
Merge employees

Push Security REST API (v1)

Overview

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.

Authentication

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.

Rate limits

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.

Errors

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.

Common Response Codes

HTTP CodeDescription
200 OKYour request was successfully processed.
400 Bad RequestYour request is missing something or is incorrect. Double-check your parameters.
429 Too Many RequestsYou've exceeded the rate limits. Consider implementing exponential backoffs in your API calls.
500 Server ErrorSomething's not right on our end.

Versioning

You're currently working with version 1 of the Push Security API. Should there be any breaking changes in the future, we'll bump up the API version number. If you hold an active API key, we'll send you notifications over email about the deprecation date for the older version.

Download OpenAPI description
rest-v1.json
rest-v1.yaml
Overview
URL
https://pushsecurity.com/contact/
support
support@pushsecurity.com
License
Commercial
Terms of Service
Languages
Servers
https://api.pushsecurity.com/

Accounts

These objects represent the accounts (owned by employees) in your organization.

Operations

Accounts (Other)

These objects represent the accounts (other) (owned by employees) in your organization.

Operations

Apps

These objects represent the apps that have been found in your organization.

Operations

Apps (Other)

These objects represent the apps (other) that have been found in your organization.

Operations

Browsers

These objects represent the browsers (used by employees) in your organization.

Operations

Browser Extensions

Operations

Detections

Operations

Employees

These objects represent the employees in your organization.

Operations

Delete an employee from a group

Request

Security
x-api-key
Path
idstringrequired

Unique identifier for the employee

Bodyapplication/jsonrequired

Delete an employee from a group.

groupstringrequired

The group to remove employee from.

Example: "Engineering team"
curl -i -X DELETE \
  'https://api.pushsecurity.com/v1/employees/{id}/groups' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY_HERE' \
  -d '{
    "group": "Engineering team"
  }'

Responses

OK. Returns all groups still associated with the employee after being removed.

Bodyapplication/json
groupsArray of stringsrequired

The groups associated with the employee.

Example: ["Other team"]
Response
application/json
{
  "groups": [
    "Other team"
  ]
}

Merge employees

Request

Security
x-api-key
Path
idstringrequired

Unique identifier for the employee

Bodyapplication/jsonrequired

Merge a list of employees with the primary one given.

secondaryEmployeeIdsArray of strings[ 1 .. 5 ] itemsrequired

A list of employee IDs.

Example: ["72d0347a-2663-4ef5-b1c5-df39163f1603","87569da6-fb7a-4df7-8ce2-246c14044911"]
curl -i -X POST \
  'https://api.pushsecurity.com/v1/employees/{id}/merge' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY_HERE' \
  -d '{
    "secondaryEmployeeIds": [
      "72d0347a-2663-4ef5-b1c5-df39163f1603",
      "87569da6-fb7a-4df7-8ce2-246c14044911"
    ]
  }'

Responses

OK. Returns the details of the primary employee.

Bodyapplication/json
idstring

Unique identifier for the employee

Example: "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0"
emailstring(email)

Primary email address of the employee

Example: "john.hill@example.com"
knownEmailsArray of strings

All the known email addresses of the employee

Example: ["john.hill@example.com","jhill@example.com"]
firstNamestring

First name of the employee

Example: "John"
lastNamestring

Last name of the employee

Example: "Hill"
departmentstring

Department - as provided by connected API integrations

Example: "Security Engineering"
locationstring

Location - as provided by connected API integrations

Example: "New York"
licensedboolean

Whether the employee is licensed on the Push platform

Example: true
groupsArray of strings

Groups the employee is in

Example: ["engineering","marketing"]
creationTimestampinteger

When this employee was created, formatted as a UNIX timestamp (in seconds)

Example: 1698669223
chatopsEnabledbooleanDeprecated

Whether the employee has ChatOps enabled

Deprecation notice: this value no longer does anything unless you still have access to the legacy Employee chat topics functionality on your account. It will be removed in the next API version.

Example: true
Response
application/json
{
  "id": "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0",
  "email": "john.hill@example.com",
  "knownEmails": [
    "john.hill@example.com",
    "jhill@example.com"
  ],
  "firstName": "John",
  "lastName": "Hill",
  "department": "Security Engineering",
  "location": "New York",
  "licensed": true,
  "chatopsEnabled": true,
  "groups": [
    "engineering",
    "marketing"
  ],
  "creationTimestamp": 1698669223
}

Unmerge employee

Request

Security
x-api-key
Path
idstringrequired

Unique identifier for the employee

Bodyapplication/jsonrequired

Unmerge an email address from a target employee

emailstringrequired

The email address to unmerge from the target employee

Example: "john.hill@example.com"
curl -i -X POST \
  'https://api.pushsecurity.com/v1/employees/{id}/unmerge' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY_HERE' \
  -d '{
    "email": "john.hill@example.com"
  }'

Responses

OK. Unmerge operation has completed successfully.

Bodyapplication/json
idstring

Unique identifier for the employee

Example: "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0"
emailstring(email)

Primary email address of the employee

Example: "john.hill@example.com"
knownEmailsArray of strings

All the known email addresses of the employee

Example: ["john.hill@example.com","jhill@example.com"]
firstNamestring

First name of the employee

Example: "John"
lastNamestring

Last name of the employee

Example: "Hill"
departmentstring

Department - as provided by connected API integrations

Example: "Security Engineering"
locationstring

Location - as provided by connected API integrations

Example: "New York"
licensedboolean

Whether the employee is licensed on the Push platform

Example: true
groupsArray of strings

Groups the employee is in

Example: ["engineering","marketing"]
creationTimestampinteger

When this employee was created, formatted as a UNIX timestamp (in seconds)

Example: 1698669223
chatopsEnabledbooleanDeprecated

Whether the employee has ChatOps enabled

Deprecation notice: this value no longer does anything unless you still have access to the legacy Employee chat topics functionality on your account. It will be removed in the next API version.

Example: true
Response
application/json
{
  "id": "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0",
  "email": "john.hill@example.com",
  "knownEmails": [
    "john.hill@example.com",
    "jhill@example.com"
  ],
  "firstName": "John",
  "lastName": "Hill",
  "department": "Security Engineering",
  "location": "New York",
  "licensed": true,
  "chatopsEnabled": true,
  "groups": [
    "engineering",
    "marketing"
  ],
  "creationTimestamp": 1698669223
}

Findings

These objects represent the findings that have been found in your organization.

Operations

URL blocking

These objects represent the blocked URLs configured in your organization.

Operations

Stolen credential detection

Manage custom stolen credentials that you have added to your organization for monitoring and enforcement.

Operations