So you want to automate your job application game? Smart move! The GigRadar Public API lets you build your own custom workflows, integrations, and applications that work exactly how you want them to.
What Can You Actually Do With This?
1. 📬 Manage Multiple Webhooks
The Problem: GigRadar dashboard does not allow you to connect multiple webhooks
The Solution: Connect through API and manage your webhooks programmatically.
2. ✍️ Build Your Own Application Factory
The Problem: You want to create applications with YOUR cover letters, YOUR AI, YOUR style or build an AI agent that's integrated deep into your agency flows. But you still want GigRadar to handle the boring parts (validation, scheduling, submission).
The Solution: Generate your cover letter however you want (your own AI, templates, copy-paste from ChatGPT, custom RAG, whatever), then send it to GigRadar. We'll handle all the validation, scheduling, and submission magic.
Real-World Use Cases:
The AI Enthusiast: "I want to use GPT-995 to generate custom cover letters, then send them via GigRadar"
The Template Master: "I have 5 cover letter templates—let me pick the right one for each job"
The Bid Strategist: "I want to bid $log(X)-(inf/-⍶*3) for hourly jobs but $(Y-⍷) for fixed-price projects"
The Context Nerd: "I want to feed the entire Roman history before XVI century to the context of my AI" (because that's what clients really need)
The Timing Ninja: "I want to schedule my proposals exactly at 9:01 because that's when my clients open their Upwork page"
How It Works:
Opportunity comes in (via webhook or however you found it)
You generate your cover letter (your way!)
Send it to GigRadar with your bid and optional schedule
GigRadar handles validation, timing, and submission
Track the status until it's sent (or handle errors if something goes wrong)
Next Steps: Check out the application creation docs for requirements and options.
3. 🎯 Custom Job Qualification workflow
Build a flexible, opinionated pipeline to decide which opportunities deserve your time.
The Problem: Not every job is worth an application. You need consistent, automated scoring to filter noise and focus on high‑fit leads.
The Solution: Use GigRadar’s API to fetch opportunity details, enrich context, score with your rules/AI, then route to “apply,” “review,” or “ignore.”
How it may work for you:
Ingest
Receive opportunities via webhook.
Normalize fields: client history, budget, tags, skills, connects needed, deadline.
Enrich (optional)
Pull client meta (hire rate, average spend, location, recent activity).
Add your internal signals: niche tags, past success patterns, blacklist/whitelist.
Launch custom web agents to collect additional data from Upwork..
Score
Rule-based: weight by budget fit, timezone overlap, required skills match, connects cost.
AI-based: run an LLM rubric on job description vs team strengths and prior wins.
Output a single score 0–100 with reason codes (e.g., “low budget,” “skills mismatch,” “urgent deadline”).
Decide
Score ≥ 80 → queue for auto-application creation via API.
60–79 → send to “human review” with prefilled draft.
< 60 → archive with reason; don’t waste connects.
Apply or Route
If “apply,” call application creation with selected template or AI-generated letter, bid, and schedule.
If “review,” post to your internal dashboard with highlights and suggested angle.
Feedback Loop
After results (sent/declined/replied/hired), push outcomes back into your model to refine weights and prompts.
Example Signals To Use:
Must‑have skills match: ≥ 70% required keywords present.
Budget sanity: min hourly ≥ your floor; fixed ≥ effort estimate.
Client credibility: hire rate, average spend, verified payment, response time.
Strategic fit: niche alignment, long‑term potential, past positive history.
Timing: fresh post, low competition, your team availability.
Next Steps: Implement your scorer, then connect to GigRadar API ↗ for the opportunities and application endpoints.
4. 👀 Keep Tabs on Your Applications
The Problem: You submitted an application, but did it actually go through? Is it stuck? Did something break?
The Solution: Poll the application status to see exactly what's happening. Know when it's sent, when it fails, and why.
How It Works:
Create or schedule an application or wait for GigRadar to send it
Periodically check its status (poll the API)
Detect success (application sent ✅) or failure (error details ❌)
Do something with that info (celebrate, retry, log, dashboard - your choice)
Next Steps: See the status polling guide for best practices.
🎯 Getting Started (5-Minute Setup)
Subscribe to API plan
Contact our team to purchase the API add-on to your main subscription.
Get Your API Key 🗝️
Go to Settings → API Access in your GigRadar account
Click "Generate API Key"
Copy it somewhere safe (you'll only see it once!)
Play Around 🧪
Visit the interactive API docs
Try endpoints directly in your browser (no code needed!)
See real requests and responses
Pick Your Adventure 🗺️
Want instant notifications? → Start with webhooks
Want custom applications? → Jump to application creation
Want to analyze opportunities? → Check out the opportunity endpoint
Build Something Cool 🚀
Follow the detailed guides in the API docs
Start simple, iterate, make it awesome, share what you've built in our community!
⚠️ Important Stuff
Rate Limits:
Default: 30 requests per minute, 1,000 per day
Check the response headers to see your limits
Don't worry, it's usually plenty unless you're doing something wild
Security:
Always use HTTPS for webhooks
Recommended to add authentication to your webhook endpoints (basic auth is fine)
Don't commit your API key to GitHub (we've all done it - don't be that person)
Auto-Bidder Warning:
⚠️ CRITICAL: Turn off auto-bidder in your scanner settings if you're using the API to create applications
Having both enabled = duplicate applications = confusion = 🤦♂️
Subscription:
API access requires an active subscription
Keys automatically disable when subscription expires (but come back when you renew—no data loss!)
🆘 Need Help?
Full API Docs: https://api.gigradar.io/public-api/v1/docs
Support Email: [email protected]
Debugging: Include your request ID (
X-GigRadar-Request-Idheader) when reporting issues - it helps us help you faster!
Ready to build something awesome? 🎉 Head over to the complete API documentation and start automating your way to more opportunities!