Day 1 is assigned to a specific date by the WSP team based on your batch start date.
📅 Check your confirmation email for your full task schedule.
Haven't received it? Email hello@wa.expert and we'll sort it out quickly.
📅 Week 1 · Monday
day-01
What is WA.Expert?.
Today you'll learn: what WA.Expert is and why businesses pay for it — explained so clearly you could teach it to your parents by tonight.
⏱ ~20 mins
📖 Read + Quiz + Submit
✅ Need 3/5 to unlock
🔒 Wednesday only
Week
Week 2 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes
You don't need to write code to understand the API. You need to understand what it can do.
WA.Expert exposes an HTTP API that allows external systems to send messages, manage contacts, and trigger actions programmatically. As a 2-Month expert, you need to understand what the API can do — even if you are not writing the code. Understanding API capabilities is what allows you to design integrations, scope implementation projects, and advise clients on what is possible.
🤝
The WA.Expert API is a receptionist who speaks every language. Any external system — regardless of technology — can give instructions to WA.Expert by speaking the HTTP language. "Send this message to this number." "Add this contact." "Update this tag." All through standardised HTTP requests.
📤
POST /v1/messages
Send a template message, text, image, or document to any WhatsApp number. Most-used endpoint — the trigger for any externally-initiated WhatsApp communication.
👤
POST/GET /v1/contacts
Create or update a contact. Retrieve with full conversation history. Used by CRM integrations to sync contact data bidirectionally.
🏷
POST /v1/contacts/{id}/tags
Add or remove tags on a contact programmatically. Used to update CRM lifecycle stage automatically when an event occurs in an external system.
📊
GET /v1/messages/{id}/status
Retrieve delivery and read status for a specific message. Used for campaign analytics and delivery confirmation workflows.
🔑 Authentication: Every API call requires an API key in the Authorization header. API keys should never be hardcoded in client-side code or shared publicly. Treat API keys like passwords — rotate if compromised, restrict by IP where possible.
💡
Read the reference page below before taking the quiz.
What does POST /v1/messages allow an external system to do?
A
Receive incoming WhatsApp messages
B
Trigger WA.Expert to send a WhatsApp message (template, text, image, or document) to a specified phone number — the primary mechanism for all externally-triggered communication
C
Delete a contact from the CRM
D
Generate a bulk campaign report
✅ Send message endpoint is the most-used in any integration. Any external event that should trigger a WhatsApp — order confirmation, reminder, alert — uses this endpoint.
❌ POST /v1/messages sends a WhatsApp from an external trigger. External event → call this endpoint → WA.Expert delivers the message.
Question 2 of 5
Hospital's patient management system confirms an appointment. How does it send the confirmation WhatsApp via WA.Expert API?
A
Hospital manually copies phone number into WA.Expert
B
Patient management system fires POST /v1/messages with phone number, template name, and variable values (patient name, date, time, doctor name)
C
Hospital sends email to WA.Expert support
D
API polls hospital system every hour
✅ POST /v1/messages with phone + template name + variables. This is the exact integration pattern. External event → API call → WhatsApp delivered. Zero manual steps.
❌ POST /v1/messages with phone + template name + variables is the call. External system triggers it, WA.Expert delivers it. That is the integration pattern.
Question 3 of 5
Why should API keys never be stored in client-side code (browser JavaScript, mobile app)?
A
API keys are too long to store in code
B
Client-side code is accessible to anyone — API keys exposed there can be extracted and misused to send messages, access contacts, or consume API credits fraudulently
C
Client-side code runs too slowly
D
API keys don't work in client-side environments
✅ Security. Client-side code is readable by anyone who inspects the page. API keys in client-side code = public API keys = attackers can impersonate your system.
❌ Security is the reason. Client-side code is accessible to anyone. API keys stored there can be extracted and misused.
Question 4 of 5
Logistics company wants to update a contact's CRM tag from 'In Transit' to 'Delivered' automatically. Which API endpoint combination?
A
POST /v1/messages to send delivery confirmation only
B
POST /v1/messages to send the WhatsApp AND POST /v1/contacts/{id}/tags to update the CRM tag — both triggered simultaneously on delivery confirmation
C
GET /v1/contacts to retrieve the contact only
D
DELETE /v1/contacts/{id} to remove the delivered contact
✅ Two API calls simultaneously: send message (customer notification) + update tags (CRM lifecycle). Both triggered at the same delivery confirmation event.
❌ Two calls: POST /v1/messages (WhatsApp to customer) + POST /v1/contacts/tags (CRM update). Both triggered at the same time. Message + data update in one event.
Question 5 of 5
Non-technical client wants WA.Expert API for their e-commerce integration. Recommended approach?
A
They need to hire a developer
B
Use Make.com or Zapier with the WA.Expert API module — no-code platforms that make API calls to WA.Expert endpoints triggered by Shopify events, without writing code
C
Client should switch to a simpler platform
D
API integrations always require custom code
✅ Make.com or Zapier with WA.Expert's API module. Standard e-commerce integrations can be configured visually in under an hour without a developer.
❌ Make.com or Zapier is the answer. No-code API modules make WA.Expert calls triggered by Shopify events. No developer required for standard integrations.
–of 5
Answer all 5 questions, then check your score.
✏️ Your Task
🔒
Score 3/5 to unlock this
Complete the quiz above first. The moment you score 3 or more, this section unlocks.
🏅
🎉 Day 1 — done!
Day 2 opens on your assigned Tuesday.
📝 Today's Task
Someone in your family runs a small business. In 3–4 sentences, explain WA.Expert to them like you're actually WhatsApp-ing them right now. Your own words — not copied from the page.
Start like this: "So there's this platform I was reading about — it's basically for businesses that get too many WhatsApp messages to handle manually. It lets them..."
0 / 800
From your registration confirmation email. Can't find it?
Submitting before 11 PM IST on your assigned Wednesday counts as Day 9 complete.
Week 1 · Coming Tomorrow
Day 2 — WhatsApp App vs Business APIOpens Tuesday on your assigned date.