Upload a logo for the employer in Loket.nl
A documented Loket.nl operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Upload a logo for the employer
- POSTChanges data · Employer
api.loket.nl/providers/employers/{employerId}/logo
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Loket.nl operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Loket.nl operations
- Send an invite for an employer userPOST · changes data
- Create an applicationset for a userPOST · changes data
- Post user photoPOST · changes data
- Delete a specific user recordDELETE · changes data
- Resend or change the status of an invite for an employer userPATCH · changes data
- Create an SSO or Azure AD user for an employerPOST · changes data
- Edit current userPUT · changes data
- Add an external tenant for a provider userPATCH · changes data
Questions
- Can HumDay upload a logo for the employer in Loket.nl?
- Yes. This operation is published in Loket.nl's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Loket.nl data?
- Yes — this is a POST operation, so it changes something in Loket.nl. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Loket.nl account.
Where this came from
Read from a published API description for Loket.nl at developer.loket.nl/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.