LoginSign Up
← Back to all sparks
P

Productboard

PM
Velocity6.3

Product management platform for prioritization and roadmapping

www.productboard.com ↗

Productboard v2 adds exact-match text filters as the data model keeps widening.

product-managementapi-extensibilitydata-modelsearch-filtersintegrations
◆Current state
Productboard's v2 API spent the summer closing v1 parity gaps, then in September made entity types an open, workspace-specific string. Since then the data model has kept widening: rich text accepts tables and checklists, relationships hold their own field values, and as of October 15 entity search supports exact-match filtering on text fields.
◆Where it's heading
With parity mostly done, v2 is extending the data model and making it queryable. Workspace-defined entity types and relationship fields push schema decisions into each workspace's configuration, and filter operators like eq let integrations match records precisely instead of scanning with contains.
◆Prediction
Expect filtering and search to reach relationship fields next, following the pattern of new data shapes gaining query operators a few weeks later. Whether the beta customer score endpoint leaves beta isn't signalled by the entries.

◆Recent moves

  1. 13d ago

    v2 - 2026-10-15 - Exact-match text field filter

    Entity search gains an eq operator for text fields, matching whole values up to 2,000 characters, case-sensitive except on email and domain fields. It is a practical addition for sync integrations that dedupe on external IDs, and it follows the summer's pattern of new query operators filling out v2.

    View source ↗
  2. 20d ago

    v2 - 2026-10-08 - Relationship field values and Documents API references

    Relationships now carry field values: list and entity reads return a fields object, create accepts one, and entity configuration lists which fields each relationship supports. It extends the September move to workspace-defined entity types, letting teams store context such as weight or status on the link itself instead of on either entity.

    View source ↗
  3. 1mo ago

    EntityType moves from fixed enum to workspace-specific open string

    ⚡ SPARK

    EntityType is now an open string sourced from workspace configuration rather than a fixed enum — a breaking API change that makes the entity model extensible per workspace, requiring clients to query List entity configurations before filtering rather than hardcoding type values.

    View source ↗
  4. 1mo ago

    v2 - 2026-09-21 - Tables, checklists and code languages in rich text

    Rich text fields accept tables, checklists and language-tagged code blocks, and reads now come from the live editor document. Mentions, embeds and similar nodes come back as placeholder links, so round-tripping descriptions through the API is closer to lossless but not fully.

    View source ↗
  5. 1mo ago

    v2 - 2026-09-09 - Search tag field values

    Tag field value search now supports fuzzy, accent-insensitive querying with up to 20 relevance-ranked results — closing a gap that previously required exact or prefix matching for tag lookups in large taxonomies.

    View source ↗
  6. 3mo ago

    Add beta endpoint for aggregated customer importance scores on hierarchy entities

    A new beta endpoint returns aggregated customer importance scores across a product hierarchy entity and all its descendants — a read-only analytics surface that rolls up weighted customer signals without requiring clients to compute the rollup themselves.

    View source ↗