Add Hexia platform parser#60
Merged
Merged
Conversation
Owner
|
This is a great find, thank you (and for your other contributions as well)! Gonna put a few of these in test to see how it goes, I wonder if we're going to run into any rate limiting here. One small thing that is missing is that
|
Also sorted dict alphabetically
Owner
|
Ran into some issues with some of the websites: looks like not all results have all required keys and Mercatus gives me a 503. Others look fine so I'll add most to Hestia soon. |
xenbyte
pushed a commit
to xenbyte/hermes
that referenced
this pull request
Mar 31, 2026
Add Hexia platform parser
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As mentioned in #53. Wooniezie and many other websites just buy the platform from a common third party.
Endpoint to get the data, no data needs to be posted:
https://{corp}api.hexia.io/api/v1/actueel-aanbod?limit=99&sort=-publicationDateWhere
corpis the slug of the corporation which you want to parse. You can get this by simply filtering the request path in inspect element in your browser. The name is always appended withapiand is sent to hexia.io, though sometimes it's also zig365.nl, but using hexia.io seems to work anyway, so no special handling is needed. Current supported targets:To generate a direct link to the listing we need to map the corp to the full website path of the corporation which is different and not reported in the API. So for this I created a dictionary with mappings from the corp slug to the full listing URL, you can get this by simply opening a random listing in your browser.
To install this in the system it's the same as with the DAK endpoints, but instead of regions it's the corporate slugs.