HiringCenter API

HiringCenter REST API (v2)

The HiringCenter v2 API is a REST API for managing:

• Prospects
• Notes
• Tasks
• Meetings
• Account metadata
• Webhook integrations

Base URL

https://api.hiringcenterpro.com/v2

---

Authentication

Create an API Key in your HiringCenter account by navigating to Settings -> API / Webhooks -> Add API Key.

Create an API Key (Video)

All endpoints require API Key authentication. The HiringCenter API uses Bearer token authentication for requests. Send your API key in the Authorization header:

• Authorization header

  Code
   
  Authorization: Bearer <YOUR_API_KEY>

API keys are hashed and stored securely. Each key is associated with an account and includes account-scoped permissions.

Example Requests

• List prospects

  Code
   
  curl -X GET \
    'https://api.hiringcenterpro.com/v2/prospects?limit=1' \
    -H 'Authorization: Bearer <YOUR_API_KEY>' \
    -H 'Accept: application/json'

• Create a prospect

  Code
   
  curl -X POST \
    'https://api.hiringcenterpro.com/v2/prospects' \
    -H 'Authorization: Bearer <YOUR_API_KEY>' \
    -H 'Content-Type: application/json' \
    -d '{
      "firstName": "Jane",
      "lastName": "Doe"
    }'

Rate Limiting

Requests are rate limited by authenticated identity to ensure fair usage and system stability:

• API key authentication: per API key
• Firebase authentication: per Firebase user
• Other auth types: per authenticated identity

Dual-window limits are enforced:

• 300 requests per minute (burst window)
• 6000 requests per hour (sustained window)

Rate Limit Headers

Use these response headers to monitor usage:

• RateLimit-Limit
• RateLimit-Remaining
• RateLimit-Reset

Rate Limit Exceeded Response

When a rate limit is exceeded, the API returns:

• Status Code: 429 Too Many Requests
• Headers:
  • Retry-After
  • RateLimit-Limit
  • RateLimit-Remaining
  • RateLimit-Reset
• Response Body:

Code
 
{
"error": "Too many requests",
"message": "Minute limit exceeded. Please try again later.",
"retryAfter": 30
}

Request and Response Conventions

• Requests and responses use application/json unless otherwise noted
• Timestamps are Unix time in milliseconds unless otherwise specified
• Standard error responses follow the Error schema