Proposal: API Access with Authentication

[rorar]

It could be really useful to expose CV Manager data through a simple, secure API.

This would allow users to:

• integrate their CV data with other tools (e.g. personal websites, job application automations)
• programmatically update or sync multiple CVs
• build custom workflows on top of the app

A possible approach:

• provide a REST API for core resources (CVs, entries, exports)
• support authentication via API keys or OAuth
• allow scoped access (read-only vs read/write)
• optionally include rate limiting and basic audit logging

This could open the door for integrations and power-user use cases, while keeping it optional for users who just want a simple UI.

[vincentmakes]

That's already the case - ex for the public side:

Endpoints (all under /api/*, defined in src/server.js:1598–1673):
• GET /api/profile — name, title, bio, location, linkedin, languages, picture (no email/phone)
• GET /api/experiences — visible experiences only
• GET /api/certifications
• GET /api/education
• GET /api/skills — categories + skills
• GET /api/projects
• GET /api/timeline
• GET /api/custom-sections
• GET /api/sections and /api/sections/order — visibility + ordering
• GET /api/settings and /api/settings/:key
• GET /api/layout-types, /api/social-platforms
• GET /api/cv — aggregated full CV
• GET /api/datasets/slug/:slug[/:lang] and /api/datasets/id/:id — fetch a specific saved dataset (if marked public)

Admin side:

•	Profile — GET/PUT /api/profile, picture upload/delete/select, GET /api/profile-pictures
•	Experiences — full CRUD + /logo upload/delete/select + /api/logos* management (apply-global, propagate)
•	Certifications — full CRUD + /logo endpoints + /api/cert-logos/*
•	Education — full CRUD + /logo endpoints + /api/edu-logos/*
•	Skills — full CRUD on categories + skills
•	Projects — full CRUD
•	Sections — GET/PUT /api/sections/:name, /print, /order, /rename
•	Custom sections & items — full CRUD, item pictures
•	Settings — GET/PUT /api/settings/:key
•	Theme — GET/PUT /api/theme (with propagation rules)
•	Datasets — CRUD, /default, /save, /public, /language, /siblings, slug/id lookups
•	Reorder — PUT /api/reorder/:type
•	Timeline — GET /api/timeline
•	Exports — POST /api/export/ats-pdf, GET /api/export/static-site
•	Version — GET /api/version (checks GitHub for updates)
•	Misc — /api/layout-types, /api/social-platforms