The Fin Custom Helpdesk API allows you to integrate your custom helpdesk with Fin through a standardized set of API endpoints and webhooks.
Fin Custom Helpdesk API (0.0.1)
Overview
Languages
Servers
Your Custom Helpdesk API (replace with your actual domain)
https://helpdesk.example.com/api/fin/
- Your Custom Helpdesk API (replace with your actual domain)https://helpdesk.example.com/api/fin/messages
- curl
- Node.js
- Ruby
- PHP
- Python
- Java
- Go
- C#
- R
curl -i -X GET \
'https://helpdesk.example.com/api/fin/messages?conversation_id=string&after_id=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Messages retrieved successfully
Message content in HTML format
Example: "<p>Thank you for reaching out! I'd be happy to explain our pricing plans.</p>"
One of:
End user having a conversation with Fin or with an agent.
URL to user's avatar/profile picture (displayed in Fin Messenger)
Example: "https://example.com/avatars/jane.jpg"
Who can see the message:
public- Visible to end-users (appears in Fin Messenger)private- Only visible to agents (internal notes)
Enum"public""private"
Example: "public"
When the message was created (ISO 8601 UTC)
Example: "2025-10-27T14:35:00.000Z"
Response
application/json
[ { "id": "msg_101", "conversation_id": "conv_456", "message_type": "comment", "body": "<p>Thank you for reaching out! I'd be happy to help.</p>", "author": { … }, "visibility": "public", "created_at": "2025-10-27T14:35:00.000Z", "attachments": [] }, { "id": "msg_102", "conversation_id": "conv_456", "message_type": "comment", "body": "<p>Great! Can you tell me about the Enterprise plan?</p>", "author": { … }, "visibility": "public", "created_at": "2025-10-27T14:37:00.000Z", "attachments": [] } ]
Bodyapplication/json
Message content in HTML format.
Supported HTML tags are:
- Paragraphs
<p> - Heading 1, Heading 2
<h1><h2>(note h3 to h6 appears as a h2) - Bold
<b> - Italic
<i> - Links
<a> - Images
<img>(can be linked) - Line breaks
<br> - Code blocks
<code> - Unordered lists
<ul> - Ordered lists
<ol>
Example: "<p>Hi! I'd like to know more about your pricing plans.</p>"
- Your Custom Helpdesk API (replace with your actual domain)https://helpdesk.example.com/api/fin/messages
- curl
- Node.js
- Ruby
- PHP
- Python
- Java
- Go
- C#
- R
curl -i -X POST \
https://helpdesk.example.com/api/fin/messages \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"conversation_id": "conv_456",
"message_type": "comment",
"body": "<p>Hi! I'\''d like to know more about your pricing plans.</p>",
"author": {
"id": "user_123456",
"user_type": "end_user"
},
"visibility": "public",
"created_at": "2025-10-27T14:30:00.000Z",
"object_id": "123456",
"attachments": [
{
"url": "https://example.com/files/pricing-guide.pdf",
"filetype": "pdf",
"filename": "Pricing Guide 2025"
}
]
}'Message created successfully
Message content in HTML format
Example: "<p>Thank you for reaching out! I'd be happy to explain our pricing plans.</p>"
One of:
End user having a conversation with Fin or with an agent.
URL to user's avatar/profile picture (displayed in Fin Messenger)
Example: "https://example.com/avatars/jane.jpg"
Who can see the message:
public- Visible to end-users (appears in Fin Messenger)private- Only visible to agents (internal notes)
Enum"public""private"
Example: "public"
When the message was created (ISO 8601 UTC)
Example: "2025-10-27T14:35:00.000Z"
Response
application/json
{ "id": "msg_001", "conversation_id": "conv_456", "message_type": "comment", "body": "<p>Thank you for reaching out! I'd be happy to explain our pricing plans.</p>", "author": { "id": "user_123456", "user_type": "end_user", "name": "Jane Doe", "email": "jane.doe@example.com", "photo_url": "https://example.com/avatars/jane.jpg", "attributes": { … } }, "visibility": "public", "created_at": "2025-10-27T14:35:00.000Z", "attachments": [ { … } ] }