Skip to main content
Use https://data.grdd.net for Connect profile and contact changes. Registration, public duplicate checks and general token operations remain on Core because their matching Connect operations do not exist. A website profile or company-user list is not a registration or duplicate-check replacement.

Choose your task

Keep account authority separate from content

Core issues the credentials used by the documented Connect APIs. Company registration, account checks and client-token issuance remain on their existing Core contracts. A website profile or team-member content record does not replace an account record. Company user management does not replace the public duplicate check. Use the exact workflow reference for your task. Ask GRiDD support for a setup or password-recovery workflow not covered here. Do not copy a private recovery link into an integration.

Before you use a token

Check the endpoint’s caller and company-scope rules. The client token described on the existing client-token reference has client MANAGER authority. It is not a read-only credential. Keep it private and use it only for the documented workflow.