LoginSign Up
← Back to all sparks
P

Productboard

PM
Velocity5.0

Product management platform for prioritization and roadmapping

www.productboard.com ↗

Productboard's v2 documents API now keeps plain web addresses and emoji as ordinary text.

product-managementapidocumentsdata-modelintegrations
◆Current state
Productboard's v2 API spent the summer closing v1 parity gaps, then in September made entity types a workspace-specific string. October added field values on relationships, exact-match text search and 308 redirects for merged entities. On November 5 the documents content endpoints changed how they treat bare URLs, email addresses and emoji: they now stay plain text unless written with explicit link syntax.
◆Where it's heading
The v2 API is being tightened release by release so integrations can round-trip data without surprises. The documents format is the latest surface to get exact, documented rules.
◆Prediction
Expect further dated v2 entries that fill in document and entity edge cases; nothing in the entries points to a larger change soon.

◆Recent moves

  1. 9d ago

    v2 documents API keeps bare URLs and emoji as plain text

    Document reads and writes now leave bare URLs, email addresses and emoji as ordinary text, and only explicit link syntax creates a link. Integrations that rewrite documents need to keep existing links and fetch a fresh version token after rollout.

    View source ↗
  2. 19d ago

    v2 API redirects requests for merged entities

    When an entity has been merged into another, Get entity and List relationships now return a 308 redirect to the surviving entity instead of failing. Integrations that cache IDs keep working after merges, which fits v2's turn toward real-world data hygiene.

    View source ↗
  3. 1mo 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 ↗
  4. 1mo 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 ↗
  5. 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 ↗
  6. 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 ↗