Partner API integrations can now write custom fields whose names contain a number, such as relationship_1_email or deal_2_status, using the same key the API returns when you read the record (customRelationship1Email, customDeal2Status). Before this fix, those values were ignored even though the request reported success. This applies to people, companies and contracts. Keys that already worked are unaffected.
Person responses now also include call in communicationsConsent, alongside email, text, massEmail, postalMail and visit.