Skip to main content
Use https://data.grdd.net with Authorization: Bearer <ACCESS_TOKEN>. Get a Core-issued access token for your company. Your token selects the company for owner reads and writes. You cannot select another company for a write.

Read a profile

Both reads accept only the locale query parameter: en, es, de or fr. The default is en. Send no body.
A successful read returns 200 and a profile object directly, without a data wrapper. On the owner read, the ETag header gives the profile version as "vN". If the body includes a contact record, contact.version is a separate version number. In that record, contact.mainEmail and contact.mainPhone are the public email and phone, not the account contact fields accepted by the contact PUT. Use GET /api/profiles/{griddid} when a visible profile is enough. Replace {griddid} with the company GNET ID and encode it as a URL path segment. This read still requires a Bearer token. The response includes griddid, name, locale and resolvedLocale. Other fields depend on what the caller may see. If the API supplies an English fallback, resolvedLocale can differ from locale. A missing or inaccessible profile can return 404 not_found. Use the Core member lookup if you need the existing Core member fields or response. Use the Core company content read if you need the combined profile, fleet, services and locations in one response. The Connect profile is neither of those records.

Update account contact details

Send PUT /api/profile/contact with a flat JSON object. All fields below are optional strings and accept null. Send no company selector or locale. Use mainEmail and mainPhone for the account contact, not email and phone. The response uses different names: contact.mainEmail and contact.mainPhone in the GET profile response, and data.mainEmail and data.mainPhone in the contact PUT response, contain the public values written with email and phone. Do not copy the GET contact fields into the PUT request’s mainEmail or mainPhone. That would overwrite the account contact with the public contact and trigger the effects below. A successful account contact update does not make the PUT response’s data.mainEmail or data.mainPhone show the new account values. To update the website field from Core company edit, send website, not webURL, in this request. Set If-Match from contact.version in your latest own profile response. For example, send "v3" for contact.version: 3. If there is no contact record, send "v1". Do not use the profile’s ETag for this write.
Every contact write also replaces your company’s Farmhouse alert email and SMS recipients with the stored account mainEmail and mainPhone. A null stored value clears the corresponding alert recipient. This includes the website-only example below. When the account email changes, the write 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.
This write updates the contact record and applies the account contact and address fields to the company account. If the response is 202, follow the recovery steps before you rely on the account update. This write does not return the Core company edit response. Keep Core for integrations that need that contract or the existing cross-company edit mode.

Update profile display fields

Send PATCH /api/profile with a flat JSON object. Set If-Match to the profile ETag from your latest own profile read for the intended locale. If you also updated the contact record, read your profile again after that write completes. Set locale in the request body to the language from your read. It defaults to en.
This PATCH changes the profile display fields only. It does not update the company account contact. If the website must change in both records, use website in the contact PUT and webURL in the profile PATCH. The two calls have separate versions and keys. One can succeed without the other.

Write results and recovery

For both writes, send Content-Type: application/json, If-Match in the form "vN" with a positive integer, and an Idempotency-Key of 8 to 128 printable ASCII characters without spaces. Use a new key for each new change. Reuse a key only for an exact retry of that request. For a 202, use the operation ID instead of starting the write again. Send a Bearer token for the same company and no body:
The response has operationId, status and effects. Each effect has name, status, retryable and, when available, problemCode. The request returns 200 when complete, 202 when still pending, or 404 if the operation is missing or does not belong to your company. See Connect API errors for the problem response fields.