Messages

Handle Custom Channel Message

post

https://api.dmchamp.com/v1https://us-central1-whatzaidev.cloudfunctions.net/api/v1

/incoming-custom-channel-message

Handles incoming messages from custom channels. Campaign Assignment Priority - 1. Explicit campaignId (highest priority) 2. Keyword matching (existing logic) 3. Default campaign (fallback). Backwards Compatibility - All new fields are optional. Existing integrations continue to work unchanged.

Authorizations

ApiKeyAuthUserIdAuth

apiKeystringRequired

Your DM Champ API key. Obtain from Settings → API Keys.

Query parameters

apiKeystringOptional

API key for authentication. At least one of apiKey or userId is required for protected endpoints.

Example: your_api_key

Body

application/json

messageTypestringRequired

Type of message (e.g., text, reaction)

Default: text

Responses

200

Message processed successfully

application/json

successbooleanOptionalExample: true

messageIdstringOptionalExample: 1234567890

400

Invalid request

application/json

401

Unauthorized

application/json

500

Server error

application/json

post

/incoming-custom-channel-message

HTTPcURLJavaScriptPython

POST /v1/incoming-custom-channel-message HTTP/1.1
Host: api.dmchamp.com
Content-Type: application/json
Accept: */*
Content-Length: 173

{
  "customData": {
    "messageSid": "msg123",
    "fromId": "user123",
    "toId": "business456",
    "body": "Hello from custom channel",
    "status": "received",
    "channel": "custom"
  },
  "messageType": "text"
}

Simple text messageMessage with explicit campaign assignmentMessage with media

{
  "success": true,
  "messageId": "1234567890"
}

Handle Custom Channel Message (Alternative)

post

https://api.dmchamp.com/v1https://us-central1-whatzaidev.cloudfunctions.net/api/v1

/incoming_custom_channel_message

Alternative endpoint for handling incoming messages from custom channels. Same functionality as /incoming-custom-channel-message. Campaign Assignment Priority - 1. Explicit campaignId (highest priority) 2. Keyword matching (existing logic) 3. Default campaign (fallback). Backwards Compatibility - All new fields are optional. Existing integrations continue to work unchanged.

Authorizations

ApiKeyAuthUserIdAuth

apiKeystringRequired

Your DM Champ API key. Obtain from Settings → API Keys.

Query parameters

apiKeystringOptional

API key for authentication. At least one of apiKey or userId is required for protected endpoints.

Example: your_api_key

Body

application/json

messageTypestringRequired

Type of message (e.g., text, reaction)

Default: text

Responses

200

Message processed successfully

application/json

successbooleanOptionalExample: true

messageIdstringOptionalExample: 1234567890

400

Invalid request

application/json

401

Unauthorized

application/json

500

Server error

application/json

post

/incoming_custom_channel_message

HTTPcURLJavaScriptPython

POST /v1/incoming_custom_channel_message HTTP/1.1
Host: api.dmchamp.com
Content-Type: application/json
Accept: */*
Content-Length: 173

{
  "customData": {
    "messageSid": "msg123",
    "fromId": "user123",
    "toId": "business456",
    "body": "Hello from custom channel",
    "status": "received",
    "channel": "custom"
  },
  "messageType": "text"
}

{
  "success": true,
  "messageId": "1234567890"
}

Send Custom Channel Message

post

https://api.dmchamp.com/v1https://us-central1-whatzaidev.cloudfunctions.net/api/v1

/send-custom-channel-message

Send an outbound message to a custom channel contact. Creates contact if it doesn't exist.

Authorizations

ApiKeyAuthUserIdAuth

apiKeystringRequired

Your DM Champ API key. Obtain from Settings → API Keys.

Query parameters

apiKeystringOptional

API key for authentication. At least one of apiKey or userId is required for protected endpoints.

Example: your_api_key

Body

application/json

Responses

200

Message sent successfully

application/json

successbooleanOptionalExample: true

messageIdstringOptional

ID of the created message

contactIdstringOptional

ID of the contact

messagestringOptionalExample: Message sent successfully

400

Bad request

application/json

401

Unauthorized

application/json

500

Server error

application/json

post

/send-custom-channel-message

HTTPcURLJavaScriptPython

POST /v1/send-custom-channel-message HTTP/1.1
Host: api.dmchamp.com
Content-Type: application/json
Accept: */*
Content-Length: 105

{
  "customData": {
    "fromId": "user_123",
    "customChannel": "telegram",
    "body": "Hello! How can I help you today?"
  }
}

Simple outbound messageOutbound message with campaign assignment

{
  "success": true,
  "messageId": "text",
  "contactId": "text",
  "message": "Message sent successfully"
}

Send Custom Channel Message (Alternative)

post

https://api.dmchamp.com/v1https://us-central1-whatzaidev.cloudfunctions.net/api/v1

/send_custom_channel_message

Alternative endpoint for sending outbound messages to custom channel contacts. Same functionality as /send-custom-channel-message. Creates contact if it doesn't exist.

Authorizations

ApiKeyAuthUserIdAuth

apiKeystringRequired

Your DM Champ API key. Obtain from Settings → API Keys.

Query parameters

apiKeystringOptional

API key for authentication. At least one of apiKey or userId is required for protected endpoints.

Example: your_api_key

Body

application/json

Responses

200

Message sent successfully

application/json

successbooleanOptionalExample: true

messageIdstringOptional

ID of the created message

contactIdstringOptional

ID of the contact

messagestringOptionalExample: Message sent successfully

400

Bad request

application/json

401

Unauthorized

application/json

500

Server error

application/json

post

/send_custom_channel_message

HTTPcURLJavaScriptPython

POST /v1/send_custom_channel_message HTTP/1.1
Host: api.dmchamp.com
Content-Type: application/json
Accept: */*
Content-Length: 105

{
  "customData": {
    "fromId": "user_123",
    "customChannel": "telegram",
    "body": "Hello! How can I help you today?"
  }
}

{
  "success": true,
  "messageId": "text",
  "contactId": "text",
  "message": "Message sent successfully"
}