Complete API reference for integrating with SmartSearch
The SmartSearch Platform API provides many tools and resources that enable you to integrate with all the powerful capabilities within SmartSearch.
To start using the SmartSearch Platform API, you must use a valid API Key to send requests to the API endpoints.
error keyThe SmartSearch Platform API uses bearer tokens for authentication.
To generate a bearer token, you must make an authentication request to the account endpoint with the X-API-KEY request header and your API user and password in the request body.
POST /accounts
X-API-KEY: your-api-key-here
Content-Type: application/json
{
"userName": "your-username",
"password": "your-password"
}
Response:
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
Include the bearer token in the Authorization header for all subsequent requests:
GET /candidates
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
If the bearer token is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code.
The GET endpoints in the SmartSearch Platform API follow the OData standard while the PATCH endpoints utilize the JSON Patch format.
Important: PATCH requests require the Content-Type: application/json-patch+json header.
By default, the Platform API returns 1,000 records at any given time. If there are more than 1,000 results, it returns a link to get the next set of results.
All incoming timestamps in the SmartSearch Platform API must follow the ISO 8601 format. Below are examples of valid timestamp formats you may encounter or use:
2024-08-15T14:30:00Z2024-08-15Important: When sending timestamp data in requests, ensure it adheres to the ISO 8601 standard. If no timezone is specified, UTC is assumed by default.
In case you have questions, please email integrations@smartsearchinc.com.
View the complete API reference with all endpoints, request/response schemas, and code examples.
View Full API Documentation →