These objects represent the accounts (owned by employees) in your organization.
/
Delete an employee from a...
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. |
Download OpenAPI description
Overview
URL
support
License
Languages
Servers
https://api.pushsecurity.com/
- https://api.pushsecurity.com/v1/employees/{id}/groups
- curl
- Python
- Node.js
curl -i -X POST \
'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"
}'Response
application/json
{ "groups": [ "Engineering team", "Marketing team" ] }
- https://api.pushsecurity.com/v1/employees/{id}/groups
- curl
- Python
- Node.js
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"
}'Response
application/json
{ "groups": [ "Other team" ] }
- https://api.pushsecurity.com/v1/employees/{id}/merge
- curl
- Python
- Node.js
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"
]
}'OK. Returns the details of the primary employee.
All the known email addresses of the employee
Example: ["john.hill@example.com","jhill@example.com"]
Department - as provided by connected API integrations
Example: "Security Engineering"
When this employee was created, formatted as a UNIX timestamp (in seconds)
Example: 1698669223
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 }