Skip to main content

Contact Messages API

The Contact Messages API handles submissions from contact forms across the platform, tracking message source and status.

Get All Contact Messages

curl -X GET https://api.kinconecta.com/api/contact-messages \
  -H "Content-Type: application/json"

Response

id
long
required
Unique identifier for the contact message
name
string
required
Name of the person submitting the message (max 150 characters)
email
string
required
Contact email address (max 190 characters)
subject
string
required
Message subject (max 180 characters)
message
string
required
Message content (text field)
sourcePage
string
Page where the contact form was submitted (max 120 characters)
status
enum
required
Message status
createdAt
date
required
Timestamp when message was created

Get Contact Message by ID

curl -X GET https://api.kinconecta.com/api/contact-messages/{id} \
  -H "Content-Type: application/json"

Path Parameters

id
long
required
The contact message ID

Response

Returns a single contact message object or 404 if not found.

Create Contact Message

curl -X POST https://api.kinconecta.com/api/contact-messages \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Miguel Alvarez",
    "email": "[email protected]",
    "subject": "Technical Issue",
    "message": "I am experiencing issues with the mobile app crashing on startup.",
    "sourcePage": "/support/contact",
    "status": "new",
    "createdAt": "2026-03-10T12:00:00Z"
  }'

Request Body

name
string
required
Name of the person submitting the message (max 150 characters)
email
string
required
Contact email address (max 190 characters)
subject
string
required
Message subject (max 180 characters)
message
string
required
Message content (text field, no length limit)
sourcePage
string
Page URL or identifier where the form was submitted (max 120 characters)
status
enum
default:"new"
Initial message status: new, read, or archived
createdAt
date
required
Timestamp when message is created (ISO 8601 format)

Response

Returns the created contact message object with assigned ID.

Update Contact Message

curl -X PUT https://api.kinconecta.com/api/contact-messages/{id} \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Miguel Alvarez",
    "email": "[email protected]",
    "subject": "Technical Issue - RESOLVED",
    "message": "I am experiencing issues with the mobile app crashing on startup.",
    "sourcePage": "/support/contact",
    "status": "archived",
    "createdAt": "2026-03-10T12:00:00Z"
  }'

Path Parameters

id
long
required
The contact message ID to update

Request Body

All fields from the create request. Typically used to update the status field.
status
enum
Updated message status: new, read, or archived

Response

Returns the updated contact message object or 404 if not found.

Delete Contact Message

curl -X DELETE https://api.kinconecta.com/api/contact-messages/{id} \
  -H "Content-Type: application/json"

Path Parameters

id
long
required
The contact message ID to delete

Response

Returns 204 No Content on success.

Message Status Workflow

Contact messages typically follow this lifecycle:
  1. new - Message submitted and unread
  2. read - Message has been reviewed by staff
  3. archived - Message resolved and archived for records

Source Page Tracking

The sourcePage field helps track where users are contacting you from, enabling analytics on which pages generate the most inquiries. Common values include:
  • /contact - Main contact page
  • /support - Support center
  • /tours/{id} - Specific tour pages
  • /about - About page
  • /pricing - Pricing page
Use the sourcePage field to identify patterns in user inquiries and improve user experience on high-contact pages.

Build docs developers (and LLMs) love