feat(api): define Feed/Chatter API protocol endpoints#734
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ription) Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Define Feed/Chatter API endpoints for CRUD, reactions, subscription
feat(api): define Feed/Chatter API protocol endpoints
Feb 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR completes the Feed/Chatter API protocol by defining 8 HTTP endpoint specifications to complement the data models introduced in PR#732. The API follows Airtable/Salesforce Chatter patterns for unified activity timelines.
Changes:
- Adds complete Feed/Chatter API endpoint definitions with Zod-first schemas, cursor pagination, and comprehensive error codes
- Introduces enhanced contract registry pattern that includes HTTP method and path alongside input/output schemas for improved SDK/documentation generation
- Updates ROADMAP.md to reflect Feed API completion
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
packages/spec/src/api/feed-api.zod.ts |
Defines 8 Feed API endpoints (CRUD, Reactions, Subscription) with complete request/response schemas, path parameters, error codes, and enhanced contract registry following existing patterns |
packages/spec/src/api/feed-api.test.ts |
Comprehensive test suite with 45 tests covering all schemas, validation rules, defaults, pagination, and edge cases |
packages/spec/src/api/index.ts |
Exports feed-api module following existing export conventions |
ROADMAP.md |
Updates API Protocol section to document Feed API (Feed CRUD, Reactions, Subscription) completion |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feed/Chatter data models and UI props landed in PR#732 but lack corresponding API endpoint contracts. This adds the HTTP interface specification for Feed CRUD, Reactions, and Subscription.
src/api/feed-api.zod.ts8 endpoints following existing contract patterns (
BaseResponseSchema.extend(), Zod-first,.describe()annotations):GET /feed(cursor pagination + type filter),POST /feed,PUT /feed/:feedId,DELETE /feed/:feedIdPOST /feed/:feedId/reactions,DELETE /feed/:feedId/reactions/:emojiPOST /subscribe,DELETE /subscribeAll under base path
/api/data/:object/:recordId/.Reuses existing data-layer schemas (
FeedItemSchema,ReactionSchema,MentionSchema,RecordSubscriptionSchema) — no duplication.Includes
FeedApiErrorCodeenum andFeedApiContractsregistry for SDK/doc generation:Other changes
src/api/index.ts— exportfeed-api.zodROADMAP.md— API Protocol line updatedOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.