By hand
From each business page: “Publish a job offer” in the Jobs section, “Publish a course” in the Training section. Handy for a few listings.
With every plan
Back to the plan Grands comptes
The listings of all your branches, published from your software and kept up to date on their own
You add, change or remove a job offer or a course in your software: heyalink does the same on the branch’s business page. Nothing is typed twice.
You choose, branch by branch. You can also combine both on the same business page.
From each business page: “Publish a job offer” in the Jobs section, “Publish a course” in the Training section. Handy for a few listings.
With every plan
Your recruitment or training software sends your listings to heyalink, each one to its branch’s business page. Added, changed or removed on your side, a listing is too on heyalink.
Both APIs are included in Grands comptes
Several branches, several business pages, one software: each listing goes to the right place.
Each branch has its business page and its keys. A listing sent with a branch’s key only appears on its page.
A listing added, changed, filled or removed in your software is too on heyalink, for all your branches at once.
The API tab of your space shows each business page: its keys, its webhooks, its source, and what is left to do (a site to prove, a key to create, a failing webhook).
When the invoice reaches the cap you chose, new listings wait offline, whether they come through the APIs or by hand.
Each listing carries your reference, its code on your side. Sending the same reference twice updates the listing: it is never published twice.
Included in Grands comptes
| What you do | The call |
|---|---|
| Publish a job offer, or update it | PUT /offres/{reference} |
| Read a job offer and its status | GET /offres/{reference} |
| List your job offers, page by page | GET /offres |
| Say a job offer is filled: it leaves heyalink | POST /offres/{reference}/pourvue |
| Archive a job offer: it leaves heyalink and comes back if you send it again | POST /offres/{reference}/archivage |
| Remove a job offer | DELETE /offres/{reference} |
| Send up to 100 job offers and 100 removals in a single call | POST /offres/lot |
| Send the full list of your references: job offers published through the API that are not in it are archived | POST /offres/synchronisation |
Included in Grands comptes Pro Formation
| What you do | The call |
|---|---|
| Publish a course, or update it | PUT /formations/{reference} |
| Read a course and its status | GET /formations/{reference} |
| List your courses, page by page | GET /formations |
| Say a session is full: the course leaves heyalink | POST /formations/{reference}/pourvue |
| Archive a course: it leaves heyalink and comes back if you send it again | POST /formations/{reference}/archivage |
| Remove a course | DELETE /formations/{reference} |
| Send up to 100 courses and 100 removals in one call | POST /formations/lot |
| Send the full list of your references: API courses missing from it are archived | POST /formations/synchronisation |
| Send your LHEO catalogue as it is, 5 MB at most | POST /formations/lheo |
The same tools for both APIs, on each business page.
Three are required, for a job offer as for a course. The others file your listings better in searches and filters.
titredescriptionlieucode_postal type_contrat duree_nombre duree_unite temps_de_travail teletravailalternanceexperience_mois date_expiration lien_candidature description_poste description_missions description_profil description_avantages salairesalaire_min salaire_max salaire_periode metiermetier_code famille_code code_rome secteurtitrepresentationlienorganismemodelieucode_postal duree_heures debutprixphoto_url photo_base64 pour_qui niveau_d_entree niveau_entree prerequisobjectifsinfos_pratiques metiermetier_code famille_code code_rome financementstype_certification code_rncp code_rs certificationdiplomeniveau_certification attestationalternanceWhen a detail is missing, heyalink infers it when it can (the occupation, from the ROME code or the title, for example) and tells you. It is never presented as yours.
The business page logo and a listing’s image are added on heyalink: they do not go through the API.
The Jobs API is reserved for Grands comptes
The Training API is included in Grands comptes Pro Formation
If the plan stops, your keys no longer answer, but they are not deleted. Everything resumes when the plan resumes.
Everything needed to connect your software. The documentation is readable without an account, even before subscribing.
https://heyalink.com/api/emploi/v1https://heyalink.com/api/formation/v1OpenAPI specifications Jobs API Training API
Ready-to-use examples Job offers in JSON Courses in JSON LHEO catalogue Jobs API Postman collection Training API Postman collection
Not necessarily. If your careers page, your recruitment software or your course catalogue already has an address, paste it on the API screen of the business page. Then add to your site the tag or the file that proves it is yours. For the API, whoever runs your software handles it with the documentation.
Yes, on the same business page. A synchronisation only touches listings that came the same way: those typed by hand stay as they are.
Yes, like the others: each job offer and each course online counts to the day, according to the Grands comptes grid. Pending listings do not count.
Yes. The test key gives the same answers as a real key and publishes nothing.
No. An invited developer only opens the API screens of your business pages: no amounts, no invoices, no team.
Subscription : €499 excl. VAT per month. Then your online listings, to the day.