Why should you care?

REST is predictable for CRUD on accounts, products, and appointments; tooling (Postman, OpenAPI) is mature.

See it live — copy this example

Paste into your MeanVerse project (Angular + Express + MongoDB), then run with ng serve / node / mongosh as noted.

// Resource-oriented routes
GET    /api/v1/accounts           -> list
GET    /api/v1/accounts/:id       -> one
POST   /api/v1/accounts           -> create (201 + Location header)
PATCH  /api/v1/accounts/:id       -> partial update
DELETE /api/v1/accounts/:id       -> remove (204)

// POST response
res.status(201).location(`/api/v1/accounts/${doc.id}`).json(doc);

What happened?

• Nouns in URLs, verbs in HTTP methods.
• 201 Created includes new resource URL.
• PATCH sends only changed fields unlike PUT replace.

Practice next

1. Design nouns first: accounts, transfers, invoices.
2. Use pagination query ?page=1&limit=20 on lists.
3. Version prefix /api/v1 for breaking changes.
4. Add HATEOAS _links on account responses.
5. Implement If-Match ETag for optimistic concurrency.

Remember

REST = resources + HTTP semantics. Status codes communicate outcome. MeanVerse Angular HttpClient maps cleanly to REST.

Partner integration

External fintech reads MeanVerse accounts via REST OpenAPI.

Outcome: Stable v1 contract; v2 adds fields without breaking partners.