Is your feature request related to a problem? Please describe.
Yes.
Using the GOWS engine, message pinning is not implemented.
Calling:
POST /api/{session}/chats/{chatId}/messages/{messageId}/pin
returns:
501 Not Implemented
with:
"The method is not implemented by 'GOWS' engine"
This is a problem because bots using GOWS can send messages successfully, but cannot pin important messages (welcome messages, rules, onboarding messages, key offers, etc).
Describe the solution you'd like
Support message pinning in the GOWS engine for:
POST /api/{session}/chats/{chatId}/messages/{messageId}/pin
and ideally also unpin support.
If implementation is not currently planned, then please document explicitly in the engine support matrix that this endpoint is unavailable in GOWS.
Describe alternatives you've considered
Current alternatives considered:
-
Switch from GOWS to another engine (not ideal).
-
Detect engine=GOWS and disable pin logic in application code (current workaround).
-
Use a fallback behavior in the bot (send message without pinning), but this loses functionality.
None of these are true replacements for native support.
Additional context
Issue #943 appears related to pinned chats metadata (chat overview), not pinned messages, so this seems to be a separate issue.
Observed real response:
statusCode: 501
error: Not Implemented
Logs:
📌 [PIN] status=501 | ok=False
Engine:
GOWS
Tier:
PLUS

Is your feature request related to a problem? Please describe.
Yes.
Using the GOWS engine, message pinning is not implemented.
Calling:
POST /api/{session}/chats/{chatId}/messages/{messageId}/pin
returns:
501 Not Implemented
with:
"The method is not implemented by 'GOWS' engine"
This is a problem because bots using GOWS can send messages successfully, but cannot pin important messages (welcome messages, rules, onboarding messages, key offers, etc).
Describe the solution you'd like
Support message pinning in the GOWS engine for:
POST /api/{session}/chats/{chatId}/messages/{messageId}/pin
and ideally also unpin support.
If implementation is not currently planned, then please document explicitly in the engine support matrix that this endpoint is unavailable in GOWS.
Describe alternatives you've considered
Current alternatives considered:
Switch from GOWS to another engine (not ideal).
Detect engine=GOWS and disable pin logic in application code (current workaround).
Use a fallback behavior in the bot (send message without pinning), but this loses functionality.
None of these are true replacements for native support.
Additional context
Issue #943 appears related to pinned chats metadata (chat overview), not pinned messages, so this seems to be a separate issue.
Observed real response:
statusCode: 501
error: Not Implemented
Logs:
📌 [PIN] status=501 | ok=False
Engine:
GOWS
Tier:
PLUS