API Field Mapping

Not applicable

API Field Mapping

We integrate with various third parties to accept leads by creating the service in launchpoint, providing them our fields, they push JSON data to that endpoint with the appropriate fields.

The most recent partner will not alter the data they push so that it matches our fields. They have their leads/fields that they push to all their partners and we (and the rest of their partners) have to be able to accept it. We have fields in Marketo that align with alll the data they pushing but the field names don't quite match up. Most are due to casing issues (name vs Name, phone vs Phone) but then we have naming issues like postalCode vs Zip or businessStartDate vs InceptionDate. Is there a way for us to be able to map those fields to ours?

I can't seem to find anything in documentation about it and the only reference to field mappings is in regards to SalesForce. Are the webhooks what we need to use instead and can we accept bulk lead data through that?

Level 10 - Community Moderator

Re: API Field Mapping

You can send these requests through an API gateway like AWS API GW (which I frankly recommend for all API connections no matter what).

API GW mapping templates can easily change case in JSON payloads.

Webhooks can't create leads, they can only enrich/alter/push existing leads.