Customer API Endpoints (Create, Read, Update) (Video 8)

00:00 Overview of Customer API surface
00:03 Introduction — all endpoints our controller will host
00:09 Create API — starting point of onboarding
00:16 201 Created — response for successful create
00:20 Read group — three endpoints explained
00:24 Get by ID — fetch full customer record
00:32 Exists by email — check if a customer exists
00:36 Exists by ID — boolean response for presence check
00:40 Security — read endpoints are not public
00:58 Update group — patch endpoints overview
01:03 Update customer profile
01:09 Patch KYC status
01:12 Security scopes on update endpoints
01:18 Health endpoint — simple probe for service health
01:30 Recap — full API surface: Create, Read, Update, Health
01:36 Next video — deep dive into Create API flow


In this video, we walk through the *Customer API endpoints* for our Digital Bank.
These APIs expose the Customer service securely, following proper scopes & permissions.

👉 API Groups:
1️⃣ Create group → register a new customer (KYC Pending)
2️⃣ Read group →
GET by id → fetch customer record
Exists by email → boolean response
Exists by customerId → boolean response
3️⃣ Update group →
PATCH profile update
PATCH KYC status update

⚠️ Note: All GET and PATCH endpoints are secure, not public. They require proper access scopes.


#springboot #microservices #banking #customerapi #springbootrest #digitalbank