This API adds flexible profile information to existing contacts in your CRM system. The profile_payload structure is designed for AI indexing and context building, allowing you to store any key-value data that helps Zyntro's AI understand and work with your contacts more effectively.

💡 Pro Tip

Structure your profile_payload with a 'summary' field for quick AI indexing and descriptive key-value pairs. This helps Zyntro's AI build better context and provide more intelligent responses about your contacts.

Request Endpoint: https://app.zyntrohq.com/apis/public/addProfileToContact.php

Request Method: POST

Request Payload:

{
  "api_key": "your_zyntro_api_key",
  "org_id": "your_organization_id",
  "member_id": "your_member_id",
  "contact_id": "contact_id_to_add_profile_to",
  "profile_source": "Google",
  "profile_payload": {
    "summary": "A summary of the profile data for quick AI indexing",
    "data_key_1": "Descriptive text, that can help Zyntro build context based on this field",
    "data_key_2": "Another descriptive field with relevant information"
  }
}

Response (JSON):

{
  "status": "success",
  "data": {
    "profile_id": 123,
    "profile_payload": {
      "summary": "A summary of the profile data for quick AI indexing",
      "data_key_1": "Descriptive text, that can help Zyntro build context based on this field",
      "data_key_2": "Another descriptive field with relevant information"
    },
    "profile_source": "Google"
  }
}

Response Fields:

  • status: Indicates success or error status
  • data: Object containing profile details
  • profile_id: Unique identifier for the created profile
  • profile_payload: The profile data that was stored
  • profile_source: Source of the profile data

Required Fields:

  • api_key: Zyntro API authentication key
  • org_id: Organization identifier (UUID format)
  • member_id: Member identifier (UUID format) - must be the owner of the contact
  • contact_id: Contact identifier (UUID format) - the contact to add profile to
  • profile_payload: Object containing profile data (must be a valid array/object)
  • profile_source: Source of the profile data (free-form string)

Profile Payload Examples:

Example 1: Basic Profile with Summary

{
  "profile_source": "LinkedIn",
  "profile_payload": {
    "summary": "Senior Marketing Manager at TechCorp with 8 years experience in digital marketing and lead generation",
    "job_title": "Senior Marketing Manager",
    "company": "TechCorp",
    "experience_years": "8",
    "specialties": "Digital Marketing, Lead Generation, Content Strategy",
    "education": "MBA in Marketing from State University",
    "location": "San Francisco, CA",
    "industry": "Technology"
  }
}

Example 2: Social Media Profile

{
  "profile_source": "Twitter",
  "profile_payload": {
    "summary": "Tech entrepreneur and startup advisor with 50K+ followers, active in AI and blockchain discussions",
    "username": "@techguru",
    "followers_count": "50000",
    "bio": "Tech entrepreneur | Startup advisor | AI enthusiast | Blockchain advocate",
    "interests": "Artificial Intelligence, Blockchain, Startups, Technology",
    "recent_tweets": "Active in AI and blockchain discussions, shares startup advice",
    "engagement_level": "High",
    "verified": true
  }
}

Example 3: Company Research Profile

{
  "profile_source": "Company Website",
  "profile_payload": {
    "summary": "CEO of Acme Solutions, a B2B SaaS company with 100+ employees and $10M ARR",
    "company_name": "Acme Solutions",
    "company_size": "100+ employees",
    "annual_revenue": "$10M ARR",
    "industry": "B2B SaaS",
    "founded_year": "2018",
    "headquarters": "Austin, TX",
    "key_products": "CRM Software, Marketing Automation, Sales Tools",
    "funding_rounds": "Series A - $5M",
    "key_metrics": "10,000+ customers, 95% retention rate"
  }
}

Profile Payload Best Practices:

  • Always include a 'summary' field: This helps Zyntro's AI quickly understand the contact
  • Use descriptive field names: Choose clear, meaningful keys for your data
  • Include relevant context: Add information that helps understand the contact's role, interests, or background
  • Keep data structured: Use consistent data types and formats where possible
  • Include quantitative data: Numbers, counts, and metrics are valuable for AI processing
  • Add qualitative insights: Descriptions, interests, and characteristics help build context

Notes:

  • This is a public API and requires an API Key. You can get your API Key from inside your Zyntro Account under Me > API Keys
  • Ensure that the api_key, org_id, member_id, and contact_id are valid and correspond to your Zyntro account credentials
  • The org_id should correspond to an existing organization within your account
  • The member_id should correspond to an existing member within the organization
  • The contact_id should correspond to an existing contact within the organization
  • Organization must be active for API calls to be processed successfully
  • Only the member who owns the contact can add profiles to it
  • Contact must belong to the same organization as the member
  • Profile payload must be a valid array/object - strings will be rejected
  • Profile data is automatically escaped and stored as JSON
  • Profile source is a free-form field to help track where the data came from
  • Use this API to enrich contact data with external information and build comprehensive profiles
  • Profile data is used by Zyntro's AI for better context and more intelligent responses