Archive API Endpoint
Phil Langlois
The issue with Create Post endpoint, is that it needs to post something in the comments to close a conversation. Therefore, it's not possible to archive/close from API without the conversation becoming unread again (because of that API post). Having a dedicated API endpoint for archiving without creating a post would make sense.
Martin Spütz
Problem:
When using POST /v1/posts with "close: true" to archive conversations
programmatically, a notification is always generated in the UI.
For automated workflows (document processing, CRM sync, ticket systems),
this creates notification spam for team members.
Current workaround:
Setting notification: { title: " ", body: " " } still shows a notification,
just with empty content.
Proposed solutions (in order of preference):
1. PATCH /v1/conversations/:id endpoint
- Allows state changes (close, labels, assignees) without creating posts
- Clean REST semantics
- Silent by default, audit trail via optional separate post
2. "silent" parameter on POST /v1/posts
- silent: true suppresses UI notification
- Post still created for audit trail
- Backwards compatible
Use case:
Automated document scanner processes emails, extracts data, then archives
the conversation.