경량 웹훅으로서의 HTTPS 엔드포인트
학습자는 Atlas Function을 HTTPS 엔드포인트로 노출하고 웹훅 수신기로 사용하기 위한 요청 검증을 구성합니다.
경량 웹훅으로서의 HTTPS 엔드포인트은(는) CoddyKit의 무료 MongoDB Academy 강의입니다. 이것은 4개 중 4번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 MongoDB Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. MongoDB Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
What Are Atlas HTTPS Endpoints?
Atlas HTTPS Endpoints (formerly Webhooks) expose an Atlas Function as a publicly accessible URL that accepts HTTP requests. They let external services (GitHub, Stripe, Twilio, Shopify, custom CI/CD pipelines) call your Atlas Function by posting to a URL — turning your database into a lightweight API backend with no separate server required.
Creating an HTTPS Endpoint
In Atlas App Services, go to HTTPS Endpoints and click Add an Endpoint. Configure: Route (URL path, e.g., /api/orders), HTTP Method (GET, POST, PUT, DELETE, or ANY), Authentication (application auth, user auth, or no auth for public endpoints), and the Linked Function that handles the request. The generated URL looks like: https://data.mongodb-api.com/app/APP_ID/endpoint/api/orders.
// The HTTPS endpoint URL format:
// https://data.mongodb-api.com/app/{APP_ID}/endpoint{route}
// Example endpoint configuration:
// Route: /webhook/stripe
// HTTP Method: POST
// Auth: no auth (Stripe handles its own signature)
// Function: handleStripeWebhookThe Request Object
The linked function receives a single argument — the request object — which contains all HTTP request data: body (raw body or parsed JSON), headers (a map of header name to array of values), query (URL query parameters), httpMethod, and rawUrl. Parse the body with EJSON.parse(body.text()) for JSON payloads.
exports = async function(request) {
// Access headers, query params, and body
const contentType = request.headers['Content-Type']
const page = parseInt(request.query.page) || 1
const bodyText = request.body.text()
const payload = EJSON.parse(bodyText)
console.log('Received ' + request.httpMethod + ' with page=' + page)
console.log('Body:', JSON.stringify(payload))
}Returning a Response
The function's return value becomes the HTTP response. Return a plain object to send it as JSON (Atlas automatically serialises it with a 200 status). To control the status code and headers explicitly, use Atlas's Response object or return a specific shape. Always return a response — an undefined return becomes an empty 200.
exports = async function(request) {
// Simple JSON response (200 OK)
return { success: true, data: [1, 2, 3] }
// Custom status code and headers
// return {
// statusCode: 201,
// headers: { 'X-Request-Id': ['abc123'] },
// body: JSON.stringify({ id: newDoc._id })
// }
// Error response
// return {
// statusCode: 400,
// body: JSON.stringify({ error: 'Missing required field: email' })
// }
}Webhook Signature Validation
When acting as a webhook receiver for services like Stripe, GitHub, or Twilio, always validate the request signature before processing it. Each service sends a header (e.g., Stripe-Signature, X-Hub-Signature-256) that contains an HMAC of the request body signed with your webhook secret. Verify it before touching the database.
exports = async function(request) {
// Validate Stripe webhook signature
const sigHeader = request.headers['Stripe-Signature'][0]
const bodyText = request.body.text()
const webhookSecret = context.values.get('STRIPE_WEBHOOK_SECRET')
// Compute expected signature (simplified — use a library in real code)
const crypto = require('crypto')
const timestamp = sigHeader.split(',').find(p => p.startsWith('t=')).split('=')[1]
const expectedSig = crypto
.createHmac('sha256', webhookSecret)
.update(timestamp + '.' + bodyText)
.digest('hex')
const receivedSig = sigHeader.split(',').find(p => p.startsWith('v1=')).split('=')[1]
if (receivedSig !== expectedSig) {
return { statusCode: 401, body: JSON.stringify({ error: 'Invalid signature' }) }
}
// Safe to process
const event = EJSON.parse(bodyText)
// ...
}Authentication Options
HTTPS endpoints support several authentication modes: No Auth — public endpoint, anyone with the URL can call it (use signature validation). Application Auth — caller must provide an App Services API key or JWT token. User Auth — caller must be an authenticated App Services user, and context.user is populated. Choose based on the caller: external webhooks usually use No Auth + signature validation; internal services use API keys.
// Calling a user-authenticated endpoint from a client app
const response = await fetch(
'https://data.mongodb-api.com/app/APP_ID/endpoint/api/profile',
{
method: 'GET',
headers: {
'Authorization': 'Bearer ' + userJwtToken,
'Content-Type': 'application/json'
}
}
)
const data = await response.json()Building a Lightweight REST API
You can use HTTPS endpoints to build a lightweight REST API backed by MongoDB without any Node.js server. Each route gets its own endpoint (or you use a single ANY-method endpoint and parse the path/method in the function). This is suitable for low-traffic microservices, prototypes, and internal tools where the overhead of a full application server is not justified.
// Single ANY-method endpoint handles multiple routes
exports = async function(request) {
const db = context.services.get('mongodb-atlas').db('mydb')
const path = request.rawUrl.split('/endpoint')[1] // e.g., '/api/orders'
if (request.httpMethod === 'GET' && path === '/api/orders') {
const orders = await db.collection('orders').find({}).limit(20).toArray()
return { statusCode: 200, body: EJSON.stringify(orders) }
}
if (request.httpMethod === 'POST' && path === '/api/orders') {
const body = EJSON.parse(request.body.text())
const result = await db.collection('orders').insertOne(body)
return { statusCode: 201, body: JSON.stringify({ id: result.insertedId }) }
}
return { statusCode: 404, body: JSON.stringify({ error: 'Not found' }) }
}Idempotency for Webhook Receivers
External services often retry webhook deliveries if your endpoint returns an error or times out. This means your endpoint function may be called multiple times with the same event. Design it to be idempotent: use the event's unique ID as a deduplication key. Check if the event was already processed before doing work, and use upserts rather than inserts.
exports = async function(request) {
const event = EJSON.parse(request.body.text())
const db = context.services.get('mongodb-atlas').db('mydb')
// Idempotency check: has this event been processed?
const existing = await db.collection('processed_events').findOne({ _id: event.id })
if (existing) {
return { statusCode: 200, body: JSON.stringify({ status: 'already_processed' }) }
}
// Process the event
await handleEvent(db, event)
// Mark as processed (atomic upsert)
await db.collection('processed_events').updateOne(
{ _id: event.id },
{ $set: { processedAt: new Date(), type: event.type } },
{ upsert: true }
)
return { statusCode: 200, body: JSON.stringify({ status: 'ok' }) }
}CORS and Browser Access
If you call an HTTPS endpoint from a browser (SPA or mobile web app), you need to configure CORS headers. In the endpoint settings, enable CORS and specify allowed origins. Atlas will add the appropriate Access-Control-Allow-Origin headers to responses and handle OPTIONS preflight requests automatically.
// Manual CORS headers if you need custom control
exports = async function(request) {
const corsHeaders = {
'Access-Control-Allow-Origin': ['https://myapp.com'],
'Access-Control-Allow-Methods': ['GET, POST, OPTIONS'],
'Access-Control-Allow-Headers': ['Content-Type, Authorization']
}
// Handle preflight
if (request.httpMethod === 'OPTIONS') {
return { statusCode: 204, headers: corsHeaders, body: '' }
}
// Handle actual request
const data = await getData()
return { statusCode: 200, headers: corsHeaders,
body: JSON.stringify(data) }
}Rate Limiting and Abuse Prevention
Public HTTPS endpoints can be abused. Atlas has built-in rate limits (requests per second per endpoint), but for additional protection: validate request signatures for webhooks, add IP-based rate limiting by recording request counts per IP in MongoDB with a TTL index, and keep endpoint functions lightweight by offloading heavy processing to a database trigger or queue.
// Simple IP-based rate limiting
exports = async function(request) {
const ip = request.headers['X-Forwarded-For'][0]
const db = context.services.get('mongodb-atlas').db('mydb')
const windowMs = 60 * 1000 // 1 minute
const maxRequests = 30
const now = Date.now()
const record = await db.collection('rate_limits').findOneAndUpdate(
{ _id: ip, resetAt: { $gt: new Date(now) } },
{ $inc: { count: 1 }, $setOnInsert: { resetAt: new Date(now + windowMs) } },
{ upsert: true, returnDocument: 'after' }
)
if (record && record.count > maxRequests) {
return { statusCode: 429, body: JSON.stringify({ error: 'Rate limit exceeded' }) }
}
// Proceed...
}Logging and Debugging Endpoints
Use console.log() in your endpoint function for debugging — all output appears in the App Services execution log with a timestamp and invocation ID. For production, log the HTTP method, route, response status, and duration. Avoid logging sensitive data (API keys, passwords, full request bodies with PII). The execution log retains entries for 30 days in Atlas.
exports = async function(request) {
const start = Date.now()
const route = request.httpMethod + ' ' + request.rawUrl.split('/endpoint')[1]
try {
const result = await handleRequest(request)
console.log(JSON.stringify({ route, status: result.statusCode || 200, ms: Date.now() - start }))
return result
} catch (err) {
console.error(JSON.stringify({ route, status: 500, error: err.message, ms: Date.now() - start }))
return { statusCode: 500, body: JSON.stringify({ error: 'Internal server error' }) }
}
}Quick Check
Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.
Lesson Recap
In this lesson you learned: Atlas HTTPS Endpoints expose an Atlas Function as a public URL for receiving webhooks and building lightweight APIs, always validate webhook signatures using the service's HMAC header before processing the payload, and idempotency with a processed-events deduplication collection prevents duplicate side effects from retried webhook deliveries. Next up: Time Series Collections in MongoDB 5.0+.
자주 묻는 질문
“경량 웹훅으로서의 HTTPS 엔드포인트” 강의는 무료인가요?
네 — “경량 웹훅으로서의 HTTPS 엔드포인트” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 MongoDB Academy 강의 전체를 잠금 해제할 수 있습니다. MongoDB Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
“경량 웹훅으로서의 HTTPS 엔드포인트”에서 뭘 배우나요?
학습자는 Atlas Function을 HTTPS 엔드포인트로 노출하고 웹훅 수신기로 사용하기 위한 요청 검증을 구성합니다. 브라우저에서 직접 실행하는 실습 코드로 MongoDB Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
MongoDB Academy을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 MongoDB Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 4번째 강의입니다.
“경량 웹훅으로서의 HTTPS 엔드포인트” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 MongoDB Academy 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 MongoDB Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- 데이터베이스 트리거: CRUD 이벤트에 반응하기
- 예약된 트리거와 Cron 작업
- JavaScript로 Atlas Functions 작성하기
- 경량 웹훅으로서의 HTTPS 엔드포인트