metadata.source field on company entities is populated, replacing the v1 sourceOrigin / sourceRecordId identifiers used for CRM matching and deduplication. The temporary data consistency gap has been removed from the migration guide.isSet presence filter for custom field filters: true matches entities whose field has a non-empty value, false matches entities with no value (unset or empty). Must be used as the only key.teams[id] and teams[name] query parameters to filter entities by assigned team (mutually exclusive)teams filter to search by one or more assigned teams (multiple teams use OR semantics)type[] array parameter to filter notes by one or more note types (textNote, conversationNote, opportunityNote). Legacy aliases (simple, conversation, opportunity) are also accepted.type query parameter in favor of type[].You can find descriptions of individual objects in the Reference section of the documentation. Each object page includes an overview, use cases, key fields, relationships, and related objects to help you understand how to work with that object type in the API.
metadata[source][system] and metadata[source][recordId] query parameters to filter entities by their originating source system and record IDmetadata.source filter (previously inactive), allowing search by source system and/or record identifierhtml link in links pointing to the entity in the Productboard web UI. Returned on List entities, Retrieve entity, Create entity, Update entity, Search entities, and entity relationship responses.html link in links pointing to the note in the Productboard web UI. Returned on List notes, Retrieve note, Create note, Update note, and Search notes.html link in links pointing to the member's settings page in the Productboard web UI. Returned on List members, Retrieve member, and Search members.html link in links pointing to the team's settings page in the Productboard web UI. Returned on List teams, Retrieve team, Create team, Update team, and Search teams.html link in links pointing to the Jira integration settings page in the Productboard web UI. Returned on List Jira integrations and Retrieve Jira integration.type, types, ids, name, archived, parent, statuses, owners, fields) from the request body. Use the structured filter and return objects insteadfilter.fields. Text, number, date, single-select, and multi-select custom fields are supported with type-specific operators (contains, eq, id/name, any/all)return.fields to accept "all" or "default" as string values, in addition to an array of field namesSINGLE_SELECT, MULTI_SELECT, TAG). If color is omitted, the next available color is assigned automaticallyforce=true to unset the value from all entities, or replaceWith to reassign assignments to another value (the two parameters are mutually exclusive)ids, emails, roles, includeDisabled, includeInvitationPending, query) from the request body. Use the structured filter, search, and return objects insteadids, names, handles) from the request body. Use the structured filter and search objects insteadids, archived, processed, owners, creators, source, metadata, createdAt, updatedAt, relationships, fields) from the request body. Use the structured filter and return objects insteadsource[recordId] query parameter. Use metadata[source][recordId] insteadstate and entityId filters in the request body, useful when filtering by many entity IDs or when URL length limits applystate[] query parameter to filter connections by stateconnections link pointing to the connections list for each integration