Hernoem packages endpoint naar /api/v1/offerings
Continuous Integration / config (pull_request) Successful in 9s
Continuous Integration / prepare (pull_request) Successful in 1m14s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / build (pull_request) Successful in 2m1s
Continuous Integration / test (pull_request) Successful in 2m7s
Continuous Integration / deploy-production (pull_request) Skipped
Deploy / deploy (pull_request) Successful in 35s
Continuous Integration / deploy-test (pull_request) Successful in 36s

De frontend haalt de pakketten-data nu op via /api/v1/offerings i.p.v.
/api/v1/packages.
This commit is contained in:
2026-08-01 22:20:31 +02:00
parent cdec908d53
commit 99abf5dff0
4 changed files with 8 additions and 8 deletions
@@ -1,4 +1,4 @@
# Hand-off: Packages API (`GET /api/v1/packages`)
# Hand-off: Packages API (`GET /api/v1/offerings`)
**Audience**: whoever implements the CMS/backend that will serve package content.
**Status**: frontend is already wired up and waiting on this endpoint to exist.
@@ -19,10 +19,10 @@ it yet.
### Endpoint
```
GET /api/v1/packages
GET /api/v1/offerings
```
- **Same domain as the site, relative path.** The frontend calls `fetch('/api/v1/packages')`
- **Same domain as the site, relative path.** The frontend calls `fetch('/api/v1/offerings')`
with no protocol/host — it relies on the API being reachable under the *same* origin the
React app is served from, both on `test.slpsoftware.nl` and on production
(`slpsoftware.nl`). Today, both Pis only serve the static React build (see