submitLead

Mutation

Submit a qualified lead to the CRM system for enrollment.

Use this mutation after receiving a qualified result code (1013-1017) from createLead when your partner configuration requires manual CRM submission.

Returns the CRM record ID on success.

Mutation Signature

mutation {
  submitLead(input: SubmitLeadInput!): SubmitLeadResponse!
}

Example Request

GraphQL
Apollo Studio

mutation SubmitLead($input: SubmitLeadInput!) {
  submitLead(input: $input) {
    leadId
    statusCode
    crmRecordId
    crm
    partnerLeadId
  }
}

Example Variables:

{
  "input": {
    "leadId": "lead_abc123def456"
  }
}

Example Response

{
  "data": {
    "submitLead": {
      "leadId": "lead_abc123def456",
      "statusCode": 1021,
      "crmRecordId": "3rb1h2o3gql",
      "crm": "AFS",
      "partnerLeadId": "PARTNER-LEAD-12345"
    }
  }
}

Arguments

Argument	Type	Description
`input`	`SubmitLeadInput!`	Input for submitting a qualified lead to the CRM system. Only use after receiving a qualified result code (1013-1017) from createLead.

Input Types

`SubmitLeadInput`

Input for submitting a qualified lead to the CRM system. Only use after receiving a qualified result code (1013-1017) from createLead.

Required Fields:

Field	Type	Description
`leadId`	`ID!`	Internal lead ID returned from createLead. NOTE: This is the internal MLAS ID, not the partner’s external leadId

Optional Fields:

Field	Type	Description
`trustedformCertificateID`	`String`	TrustedForm certificate ID for deferred TCPA consent verification. Used by ping-post partners (e.g., PingTree) who generate TrustedForm after createLead, during the consumer consent page. When provided, TrustedForm verification runs before CRM submission. If verification fails, the submission is rejected.
`mobilePhone`	`String`	Consumer’s mobile phone number. Used by ping-post partners to provide the verified phone number collected during the consent page. FORMAT: 10-digit number without formatting (e.g., 5551234567)

Response Type

Returns: SubmitLeadResponse!

`SubmitLeadResponse`

Response returned from the submitLead mutation. Contains CRM submission status and record identifiers.

Field	Type	Description
`leadId`	`ID!`	Internal lead ID that was submitted
`statusCode`	`Int!`	CRM submission status code. • 200: Successfully submitted to CRM • 208: Lead was already submitted (idempotent, returns existing record) • 400: Rejected — workflow requires TrustedForm on submit but none was provided (ping∕post workflows only, where TrustedForm is deferred from createLead) • 422: Rejected — deferred TrustedForm verification failed permanently (ping∕post workflow…
`crmRecordId`	`String`	CRM record ID created in the destination system. Use this ID for future reference in the CRM.
`crm`	`String`	Name of the CRM system where the lead was submitted. Possible values: SALESFORCE, SIGMA
`partnerLeadId`	`String`	Partner’s external lead ID for correlation
`note`	`String`	Provides actionable context when statusCode indicates a rejection or error. For ping∕post workflows where TrustedForm validation is deferred (not part of the initial createLead workflow), this field describes: • For TrustedForm rejections (400, 422, 503), describes the specific failure reason. • For server errors (500), contains the error message for debugging.