Add Custom Channel Event endpoints documentation#260
Conversation
dsinghvi
left a comment
dsinghvi
left a comment
There was a problem hiding this comment.
Intercom-OpenAPI/fern/openapi-overrides.yml
Lines 4 to 6 in 7afd4f1
x-fern-sdk-group-name and x-fern-sdk-method-name for each of the endpoints so they show up properly in the SDK?
auroralimin
force-pushed
the
aurora.wang/fin-over-api-channel
branch
2 times, most recently
from
49447c7 to
380b41a
Compare
|
@dsinghvi I've added |
fern/openapi-overrides.yml
Outdated
| post: | ||
| x-fern-sdk-group-name: | ||
| - customChannelEvents | ||
| x-fern-sdk-method-name: createNewConversation |
There was a problem hiding this comment.
should we change this to just createConversation? suggestion from Matt @auroralimin
There was a problem hiding this comment.
@Eclairemoy These are events and not REST actions, so it is a "new conversation" event. I can rename everything in the API to have event at the end of it, I didn't so far because the events was in the name of the group of endpoints, so it felt repetitive.
There was a problem hiding this comment.
How about "notify", like "NotifyNewConversation", "NotifyMessage", etc?
There was a problem hiding this comment.
ah that makes sense! these look good to me
Add documentation for the new API endpoints for Custom Channel Event, that are used on a closed beta to achieve "Fin over API" integrations.
auroralimin
force-pushed
the
aurora.wang/fin-over-api-channel
branch
from
380b41a to
ca8bb06
Compare
3 participants
Add documentation for the new API endpoints for Custom Channel Events, that are used on a closed beta to allow "Fin over API" types of integration.
The changes were tested using a Swagger editor:
Swagger.Editor.-.19.May.2025.mp4