Jobifyre API Documentation

Access job offers and candidate submissions through our powerful REST API.

Quick Start Guide Authentication

Job Offers API

Access and search through of your job listings with powerful filtering options.

Candidate Submissions

Access to your candidate applications and manage recruitment submissions programmatically.

Support & Help

Get help from our developer support team and access tutorials.

Introduction

Welcome to the Jobifyre API documentation! Our RESTful API provides programmatic access to job offers and candidate submission management. Whether you're building a job board, career portal, or recruitment tool, our API makes it easy to integrate Jobifyre's data into your application.

What Can You Do With Our API?

Job Listings: Search, filter, and retrieve detailed job offer information
Candidate Submissions: Load candidate applications programmatically
Real-time Updates: Get the latest job postings as they're published

API Base URL: https://api.jobifyre.com
All API endpoints are relative to this base URL.

Authentication

To use the Jobifyre API, you need to authenticate your requests using an API key. You can obtain your API key by subscribing to one of our recruiter plans.

Getting Your API Key

Visit the Plans page and choose a subscription
Log in to your recruiter dashboard
Navigate to "API Settings" to view and manage your API key

API Key Format

Your API key follows this format:

jf_sk_comp[company_id]_[unique_token]

Example: jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0

Using Your API Key

Include your API key in the request header using X-API-Key:

HTTP Header

X-API-Key: jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0

Keep Your API Key Secret: Never expose your API key in client-side code or public repositories. Always make API calls from your backend server.

Quick Start

Get started with the Jobifyre API in minutes. Here's a simple example to fetch job offers:

cURL

curl -X GET "https://api.jobifyre.com/joboffers" \
  -H "X-API-Key: jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0" \
  -H "Content-Type: application/json"

JavaScript (Fetch API)

fetch('https://api.jobifyre.com/joboffers', {
  method: 'GET',
  headers: {
    'X-API-Key': 'jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0',
    'Content-Type': 'application/json'
  }
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error('Error:', error));

Python (Requests)

import requests

url = 'https://api.jobifyre.com/joboffers'
headers = {
    'X-API-Key': 'jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0',
    'Content-Type': 'application/json'
}

response = requests.get(url, headers=headers)
data = response.json()
print(data)

PHP

$curl = curl_init();

curl_setopt_array($curl, [
    CURLOPT_URL => 'https://api.jobifyre.com/joboffers',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'X-API-Key: jf_sk_comp12345_a1b2c3d4e5f6g7h8i9j0',
        'Content-Type: application/json'
    ],
]);

$response = curl_exec($curl);
curl_close($curl);

$data = json_decode($response, true);
print_r($data);

API Access & Rate Limits

The Jobifyre API is designed for reliable, high-performance access to job offers and candidate submissions. To ensure fair usage and system stability, we implement rate limiting.

Rate Limits

Rate Limit: 10 requests per minute per source IP address
Burst Allowance: Up to 10 requests can burst through before rate limiting kicks in

When you exceed the rate limit, you'll receive a 429 Too Many Requests response. Your application should implement proper retry logic with exponential backoff.

Rate Limit Headers

Each API response includes rate limit information in the headers:

HTTP Response Headers

X-RateLimit-Limit: 10
X-RateLimit-Remaining: 3
X-RateLimit-Reset: 1699372800

Best Practices

Efficient Queries: Use filters to reduce the number of requests needed
Error Handling: Implement proper handling for 429 responses with retry logic
Caching: Cache responses when appropriate to minimize API calls
Monitoring: Track your API usage to stay within rate limits
Batch Operations: Combine multiple operations into single requests when possible