Most job APIs stop at listings. Apply Guy lets your product or AI agent search current jobs, submit the real employer application, and receive the outcome through one API.
curl https://api.applyguy.ai/v1/applications \
-X POST \
-H "Authorization: Bearer $APPLYGUY_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: apply-$(uuidgen)" \
-d '{
"jobId": "951f7024-bbf7-4aa5-98fc-f45625584f9b",
"mode": "agent"
}'Search the catalog or pass a supported job URL, then create the application.
Use one contract while Apply Guy handles platform-specific forms and submission flows.
Follow every state by polling or signed webhooks, including agent answer rounds.
Not another listings feed
A read-only jobs endpoint is useful for search, analytics, and aggregation. It does not let an agent finish the user's task. Apply Guy connects discovery to a durable application resource and an employer-side submission.
How programmatic job applications workDeveloper API v1 serves the U.S. catalog. Filter by query, ATS, and work setting, fetch a full cached description by ID, or start from a supported U.S.-appropriate employer URL your agent found elsewhere.
Check ATS support, profile completeness, resume presence, inbox requirements, execution mode, and exact credit cost before creating the application.
Apply Guy maps candidate data, uploads files, resolves the discovered form, handles sessions and verification requirements, and submits to the employer.
Every request becomes a stateful resource. Poll it, cancel it before submission, or consume signed lifecycle webhooks in your own system.
Two execution modes
The form engine is the same. You choose who handles the non-deterministic answers.
Send the job and move on. Known candidate facts map directly; Apply Guy's resolver handles open-ended questions and unknown option sets from the saved profile context.
Apply Guy discovers the live questions and pauses only when judgment is needed. Your agent receives the prompt, options, constraints, and response schema, then returns the answer JSON.
Built for unattended workflows
Create a zero-balance developer account and one-time API key programmatically.
Issue or revoke keys with separate jobs, profile, applications, credits, and webhook scopes.
Buy any allowed dollar amount through hosted checkout, then read the live balance and rate.
Receive HMAC-signed state changes with delivery IDs and timestamps.
Compare outcomes, completion times, credit spend, ATSs, modes, and API keys over rolling ranges.
Create expiring, revocable read-only reports with operational aggregates and no candidate PII.
Questions developers ask first
Both. The jobs endpoints search Apply Guy's current catalog and return full cached job details. The applications endpoints add the write path: profile mapping, document upload, employer-form handling, submission, status, and signed webhooks.
Yes. Use agent mode. When the employer form needs a non-deterministic answer, Apply Guy pauses the application and returns the prompt, option lists, and a JSON Schema. Your agent returns valid JSON and Apply Guy resumes the same application.
Credits cost $1 for 20. Job search uses 0.05 credit per requested block of up to 25 results, and a job detail costs 0.01 credit only when found. A managed application uses 2 credits, or $0.10; an application using your own agent uses 1 credit, or $0.05. Preflight is free.
No browser extension is required. Apply Guy runs an HTTP-first application pipeline across 13 supported hiring platforms and handles the platform-specific forms, uploads, sessions, and submission details behind one API.
Poll the application resource or register a signed HTTPS webhook. Events cover queued, running, awaiting answers, succeeded, failed, and cancelled states.
Yes. Usage endpoints return application outcomes, resolved-outcome success percentage, completion-time percentiles, credit activity, time-series data, and breakdowns by ATS, mode, and API key. You can also create an expiring, revocable read-only report link containing operational aggregates and no candidate PII.
From search result to submitted
Start with the quickstart, create a scoped API key, and queue your first application with an idempotent HTTP request.