Talroo Docs Navigation Guide
Official Documentation: https://docs.talroo.com/api/search
This guide highlights where to find and how to use the most important parts of Talroo's documentation so you can integrate quickly and avoid common pitfalls. It points you to authentication parameters, the Search API parameters that materially impact relevance and pagination, and the response fields and headers.
Core APIs
Search API (Main endpoint for job retrieval)
Endpoint: /api/search
Based on the type of publisher, the requests must be sent to either:
| Domain | Use Case |
|---|---|
bulk.jobs2careers.com/api | API-SMS, API-Email, API-PUSH (asynchronous messaging) |
api.jobs2careers.com/api | API, API-REG (real-time search) |
Both have the same functionality but are on different domains to optimize to the diverse usage patterns of asynchronous messaging (ex. daily emails) and real-time search.
T-Value Reporting API
For tracking campaign performance. See T-Values for details.
Critical Search Parameters Often Missed
| Parameter | Description |
|---|---|
pid | Provide for user personalization (not in basic examples) |
start | For pagination (0-indexed - do not omit job 0 as it is the top-ranked job) |
commute | Traffic-sensitive travel time filters (in minutes: 15, 30, 45, 60) |
Not using pid and missing personalization benefits.
Key Response Fields to Parse
| Field | Description |
|---|---|
id | Unique job identifier for tracking |
price | Representation of the CPC |
url | The URL needed to register a click on the job |
Not saving and using the Click URL correctly.
Integration Checklist
Before going live, ensure:
- Authentication: Proper
id,passpassed to API call - Proper error handling (4xx, 5xx responses)
- Key parameters (
q,l) properly formatted - T-values for campaign tracking
- PID parameter for personalizing content is present, salted, and secure
Common Integration Mistakes
| Mistake | Impact |
|---|---|
| Using incorrect authentication | Use the id and password associated with the affiliate |
| Invalid Locations | Locations must be in the format of <city,state> or <zipcode> |
| Poor Tracking | Misunderstanding conversion and/or t-value tracking leads to incorrect conclusions |
| Personalization Management | New session or new PID per query breaks personalization |
Quick Troubleshooting
| Symptom | Likely Cause | Check |
|---|---|---|
| No jobs returned | Bad location parameter | Format: "City, ST" or "12345" |
| Low CTR | Poor relevance | Add query terms, check location |
| 400 errors | Bad URL or request parameters | Review user/pass and other parameters |
| Truncated results | Missing pagination | Use start parameter |
| No personalization | Missing or inconsistent pid | Pass consistent pid values |