Thread in #engineering

5 participants · Last reply 2:15 PM

Today at 9:28 AM Engineer # engineering

Hey team, just deployed the new API endpoint. Here's the endpoint structure for review:

JavaScript 
GET /api/v2/channels/:id/messages
Authorization: Bearer <token>

// Response
{
  "messages": [...],
  "cursor": "eyJpZCI6Mj...",
  "has_more": true
}
5 replies
9:33 AM

Nice! I tested the cursor-based pagination — works great. One thing: should we add rate limiting headers to the response? Something like X-RateLimit-Remaining.

9:41

Great call @Alice! I'll add the rate limit headers in the next commit. Also adding X-Request-ID for tracing.

9:45 AM

Tested on the iOS client — responses are fast! Looks solid 👍 Can we also document the error codes? I saw a few undocumented 4xx responses in the staging logs.

10:12 AM

Added the endpoint to the Postman collection and shared with the team. Also set up an automated smoke test in the CI pipeline — it runs on every PR now 🎯

API-v2-Postman-Collection.json

48 KB · JSON · 10:12 AM

New
2:15 PM Latest

Updated with rate-limit headers and full error code docs in the wiki. Sending to QA now — @Carol and @Priya can you run regression on your end? 🙏

You