Skip to main content

Choose your task

Start with the Connect API at https://data.grdd.net. The company account contact and the profile display are separate records. Use the method for the record you need.

Read company content

Start with the Connect profile read. Read fleets, services and service locations separately if you need those records. Each reference lists its own company and visibility rules. Keep the Core company-content read if you need the existing combined response or its access rules.

Profile content and compatibility

PUT /api/profile/contact accepts account contact fields as mainEmail and mainPhone, and public contact fields as email and phone. In the GET profile’s contact and the contact PUT’s data, mainEmail and mainPhone instead contain the public values. Do not copy those response fields into the PUT request’s account fields. A successful account contact update does not return the new account values in data.mainEmail or data.mainPhone. Every contact write also replaces your company’s Farmhouse alert email and SMS recipients with the stored account mainEmail and mainPhone, even for a website-only change. A null stored value clears the corresponding alert recipient. When the account email changes, it can also change your billing customer email to mainEmail if a billing customer exists. Keep Core company edit if your integration must preserve separate alert recipients or a separate billing email. Core company edit does not make these alert or billing email changes. PATCH /api/profile changes profile display fields. To change the website in both places, send website in the contact request and webURL in the display request. The calls use separate versions and idempotency keys. One can succeed without the other. Keep PUT /api/company/edit if you need the existing Core request or response format, or its cross-company edit mode. The Connect writes do not accept another company’s ID.