Hey! I’ve worked with the indeed api before, and yeah, the rate limits can be a pain. You *definitely* need a publisher account—it’s not optional.
For rate limiting, I’d recommend using exponential backoff. Like, if you hit a limit, wait a bit and try again. Also, track your calls with something like Redis to avoid going over.
Pagination is way safer than fetching everything at once. The indeed api docs are vague, but I’ve found 10-20 results per page works best.
Caching? Totally worth it. Job data doesn’t update *that* often, so even a 1-hour cache can save you tons of calls.
For rate limiting, I’d recommend using exponential backoff. Like, if you hit a limit, wait a bit and try again. Also, track your calls with something like Redis to avoid going over.
Pagination is way safer than fetching everything at once. The indeed api docs are vague, but I’ve found 10-20 results per page works best.
Caching? Totally worth it. Job data doesn’t update *that* often, so even a 1-hour cache can save you tons of calls.