How to obtain a Partner API key and authenticate requests with the X-Api-Key header.
| API Key | Label | Last Used | |
|---|---|---|---|
Every request to the Partner API must include an API key.
Getting a key
Partner API keys are issued by request — reach out to your Apploi contact or
[email protected] to get one. There is currently no
self-service way to generate a key.
Sending your key
Send your key in the X-Api-Key header on every request:
curl https://partners.apploi.com/applicants \
-H "X-Api-Key: YOUR_API_KEY"import requests
response = requests.get(
"https://partners.apploi.com/applicants",
headers={"X-Api-Key": "YOUR_API_KEY"},
)const response = await fetch("https://partners.apploi.com/applicants", {
headers: { "X-Api-Key": "YOUR_API_KEY" },
});require "net/http"
require "uri"
uri = URI("https://partners.apploi.com/applicants")
request = Net::HTTP::Get.new(uri)
request["X-Api-Key"] = "YOUR_API_KEY"
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) do |http|
http.request(request)
endDeprecated: Authorization: Bearer and /v1/users/login
Authorization: Bearer and /v1/users/loginSome parts of the API — the /easy-apply endpoint and POST /v1/users/login — also
accept an Authorization: Bearer <token> header, using a token obtained from either
endpoint's own response. This flow is deprecated and being sunset. New integrations
should authenticate with X-Api-Key instead. If you're still using the bearer-token flow,
plan to migrate — watch for a follow-up communication with removal timelines.
Authentication failures
| Status | When it happens |
|---|---|
403 Forbidden ({"message": "Forbidden"}) | Your X-Api-Key header is missing, invalid, or not enabled for this environment. This is the only authentication failure code for the X-Api-Key flow. |
401 Unauthorized | Only ever returned by a failed POST /v1/users/login call — the deprecated login flow. No other endpoint returns 401. |
See Errors & Troubleshooting for the full
status-code catalog, including how to tell the different 403 cases apart.

