Employee Data
Employee Posts API
11 min
overview this section covers basic information about employee posts api to learn more about the api and its endpoints, follow the links below employee posts api /#employee posts api endpoints find information about employee posts api endpoints employee posts api /#request types i nformation about available request types employee posts api /#rate limits i nformation about available rate limits employee posts api /#credits and tokens information about api credits and tokens employee posts api endpoints our api is a data retrieval tool the endpoints do not support analytic features employee posts api features two search and one collect endpoints for searching and collecting relevant posts of employee data request type endpoint post /v2/post employee/search/filter post /v2/post employee/search/es dsl get /v2/post employee/collect/{post id} request types a ll employee posts api requests must be made over https requests made over http will fail employee posts api supports two types of requests search endpoints support post requests only collect endpoints support the get r equests only request type endpoint function post /v2/post employee/search/filter search for relevant employee posts using search filters post /v2/post employee/search/es dsl search for relevant employee posts using elasticsearch dsl schema get /v2/post employee/collect/{post id} collect employee posts data using ids rate limits employee posts api endpoints restrict the number of requests allowed per second search endpoints collection endpoints 18 requests per second 54 requests per second authorization to start using our api, you need an api key your account manager or sales representative will generate the key for you upon your request for the api plan all requests to the employee posts api must contain an authorization header that consists of an apikey authentication string and the api key authorization header h āapikey {api key}ā authorization header headers={"apikey {api key}"} general authorization templates import requests api endpoint = "api endpoint" api key = {api key} headers = { "apikey" api key } response = requests get(api endpoint, headers=headers) \# print the response content or handle it as needed print(response text)require 'net/http' require 'uri' uri = uri parse("api endpoint") http = net http new(uri host, uri port) request = net http get new(uri request uri) api key = {api key} request\['apikey'] = api key response = http request(request) puts response bodyconst https = require('https'); const apiendpoint = 'api endpoint'; const apikey = {api key}; const options = { headers { 'apikey' apikey } }; https get(apiendpoint, options, (response) => { let data = ''; response on('data', (chunk) => { data += chunk; }); response on('end', () => { console log(data); }); });\<?php $apiendpoint = "api endpoint"; $apikey = {api key}; $options = \[ 'http' => \[ 'header' => "apikey $apikey" ] ]; $context = stream context create($options); $response = file get contents($apiendpoint, false, $context); ?> use any api compatible tool to authorize and start querying the api credits and tokens one search credits are deducted for one successful (200) request in the search endpoint /v2/post employee/search/filter /v2/post employee/search/es dsl one collection credits are deducted for one successful (200) request in the collection endpoints /v2/post employee/collect/{post id} discuss your credit needs with your account manager where can i see my credit balance? every search and collect response contains an x credits remaining header that shows the number of credits left in your account you can find the credit balance by clicking headers in the postman application example of remaining credits header x credits remaining 9973 data dictionary and samples explore data points in employee posts api data dictionary employee posts api docid\ ccwhq6wtosmnzu6ldbbe2 sample employee posts api docid\ ikm 8czmi1zc 6qo ghue