Skip to main content

Displaying Your Open Roles on Your Website

This guide explains how to pull your active job openings from Atlas and display them on your website or job board. This is a little technical so you may need a developer to help, but we will support you as best we can.

Overview

Atlas provides two public API endpoints that allow you to fetch your open roles without any authentication. These are designed specifically for public-facing use cases like career pages and job boards.

  • List all open roles — returns a paginated list of all your active public projects

  • Get a single role's details — returns the full details of one specific project

For full endpoint details, refer to the API documentation here


How it works:

Step 1 — Get your Agency ID

Every request requires your Agency ID in the URL. You can find this by asking our Customer Support team via our chat. It looks something like this: b666cbed-ee88-4bef-95d0-435bd1984f45

Step 2 — Fetch your open roles

Send a GET request to the following URL, replacing {agencyId} with your own:

GET https://api.recruitwithatlas.com/api/v1/public/{agencyId}/projects

This will return a paginated list of all your active public roles. You can control how many results come back using the page and pageSize query parameters (maximum 100 per page).

Step 3 — Display each role

Each item in the list contains everything you need to render a full job card on your website — job title, location, contract type, seniority, work mode, salary, and more. You do not need to make an extra request per role.

Step 4 — Link to individual role pages (optional)

If you want each job listing to have its own page with full details, you can use the single project endpoint, passing both your agencyId and the role's id:

GET https://api.recruitwithatlas.com/api/v1/public/{agencyId}/projects/{id}

This returns the same data shape as the list, so you can use the same rendering logic.


Things to keep in mind

  • Only roles where public is true and state is active will appear

  • Both endpoints require no API key or authentication

  • If a project ID doesn't exist, isn't public, or doesn't belong to your agency, a 404 response is returned

Did this answer your question?