Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

properties get/list/batch-read appear unable to retrieve sensitive or highly-sensitive properties

Ouverte
  • Quelque chose ne va pas ?
#9 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Domaine
api, cli

Piste de recherche

Start with the implementations of properties get, properties list, and properties batch-read, then compare their requests with the documented HubSpot Properties API behavior described here. Verify how each command handles the dataSensitivity query parameter and inspect existing command tests if present. Done means sensitive and highly sensitive properties are reachable through the read paths, with the intended default and filtering behavior covered.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

HubSpot's Properties API filters by dataSensitivity tier on read: GET /crm/v3/properties/{type} and GET /crm/v3/properties/{type}/{name} return only non-sensitive properties by default, and need a ?dataSensitivity=sensitive or ?dataSensitivity=highly_sensitive query parameter to return properties at that tier. Each value looks to be an exact match rather than cumulative, it seems getting every property regardless of tier needs three separate calls (no parameter, ?dataSensitivity=sensitive, ?dataSensitivity=highly_sensitive) merged together.

As far as we could find, none of properties get, properties list, or properties batch-read expose a flag for this parameter, and we couldn't locate a generic raw-request/escape-hatch command elsewhere in the CLI either (checked the full top-level hubspot --help command surface). So it looks like a property with a dataSensitivity of sensitive or highly_sensitive may not be reachable through any of the CLI's read paths, even though it exists and is correctly configured (visible in the HubSpot UI, retrievable via the raw API with the right parameter). Happy to be pointed at something we missed if this is already supported somewhere.

Reproduction:

hubspot properties get --type contacts <a property with dataSensitivity set>
→ {"ok":false,"error":{"status":404,"message":"No property named '<name>' exists."}}

hubspot properties list --type contacts --format json | grep <name>
→ (no output, property appears absent from the list)

printf '<name>' | hubspot properties batch-read --type contacts
→ No results.

All three behave the same way for a property that HubSpot's own Settings UI shows as correctly configured.

Possible fix: our preference would be for list/batch-read to merge all three tiers by default, since a property being invisible by default based on its sensitivity seems like a surprising gotcha to hit rather than something a caller would need to opt into avoiding. A --data-sensitivity <sensitive|highly_sensitive> flag would still be useful on top of that for anyone wanting to filter to a specific tier, but shouldn't be required just to see everything.

Langage dominant
Aucune donnée de langage
Étoiles
7
Forks
2
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de HubSpot/agent-cli

Toutes les issues de HubSpot/agent-cli

Issues similaires

Plus d'issues Backend & API Design

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.