Skip to content

Upgrading from Connect2Capital

This guide outlines the key changes between Connect2Capital’s Matchmaking API and C2C Connect’s Matchmaking API.

API Flow Changes

The main flow changes are that instead of directly getting products from a submission payload, you now:

  1. Create a submission

    Previously, matchmaking was done synchronously, and then repeated for each call. Now the submission is created, and the unique identifier is returned immediately once the submission is validated. The matchmaking process is kicked off in the background and the results are cached with the submission.

  2. Get the submission’s matches

    With the submission’s results now cached, you can retrieve the matches indefinitely from this endpoint.

  3. Create a match with a specific product

    Once the user has selected a product, a lead can be created by invoking this endpoint, which expects a submission and a (matching) product.

Full Guide

Question/Field Renames

Several question IDs have been renamed:

  • OwnerDemographics → OwnershipDemographics
  • PriorBankruptcies → PriorBankruptcy
  • AmountRequested → RequestedAmount
  • ContactMethod → PreferredContactMethod
  • ContactTime → PreferredContactTime
  • BusinessServiceOfferType → BusinessService

In address objects:

  • BusinessAddress.zip → BusinessAddress.PostalCode

Response Model Changes

  1. Question model changes:

    • required → isRequired
    • labelAlwaysOn → isLabelAlwaysOn

  2. Product model changes:

    • Partner properties moved to separate partner object
    • productName → name in product details
    • Range models now use min/max instead of low/high

  3. Form Handoff changes:

    • Simplified to only include endpoint
    • Removed UI customization properties

Additional Features

New features in C2C Connect:

  • Matchmaking results are cached with the submission
  • Additional resources may be returned alongside product matches

Breaking Changes Checklist

  • Update API endpoint URLs
  • Update question field names in payloads
  • Restructure to use submission-first flow
  • Update response parsing for new model structures
  • Update form handoff implementation if used