Skip to main content
POST
/
api
/
application-management
Create a new application management configuration
curl --request POST \
  --url https://your-instance.example.com/api/application-management \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "configurationName": "Mortgage CRM Webhook",
  "name": "mortgage-crm",
  "description": "Maps applications from Encompass CRM",
  "source": "Encompass",
  "defaultStatus": "new",
  "allowRecontact": false,
  "status": "active"
}
'
{
  "success": true,
  "message": "Configuration created",
  "data": {
    "_id": "66c0a0b0c0d0e0f0a0b0c0d0",
    "configurationName": "Mortgage CRM Webhook",
    "source": "Encompass",
    "defaultStatus": "new",
    "status": "active",
    "organizationId": "65a0e0e0e0e0e0e0e0e0e0e0"
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
configurationName
string
required

Internal identifier shown in the Applications management list (unique per org).

​
defaultStatus
string
required

Initial status applied to new Applications created with this config.

​
name
string

Display name surfaced on the Application record.

​
description
string

Free-text note explaining what this configuration is used for.

​
source
string
default:Any

Origin label (e.g. Zillow, Encompass) used to attribute leads.

​
allowRecontact
boolean
default:false

When true, the same contact can produce additional Applications even if a prior one exists.

​
status
enum<string>
default:active

Lifecycle state of the config itself: active makes it selectable, inactive retires it.

Available options:
active,
inactive

Response

Configuration created

​
success
boolean
​
message
string
​
data
object