PATENTCLAIM: Patent Claim
The PATENTCLAIM entity represents an individual claim within a patent for claim charting and infringement analysis.
Default definition. This article describes the default
PATENTCLAIM definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches PATENTCLAIM.Entity properties
| Property | Value |
|---|---|
| Entity code | PATENTCLAIM |
| Display name | Patent Claim |
| Plural | Patent Claims |
| Level | 430 |
Use cases
Child entity of PATENT for tracking individual patent claims. Two-column layout: left has claim details (claim number, type independent/dependent, depends on, status), right has claim text. Linked to PATENT via SUB|PAT comboKey. Shown as relatedlist on PATENT Claims panel.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Created by. Read-only. | |
name | text | Yes | Claim summary. |
claimNumber | number | Yes | Claim number. |
claimType | enum | Yes | Claim type. Valid ids: independent (Independent), dependent (Dependent). |
dependsOn | number | Depends on claim. | |
status | enum | Yes | Status. Valid ids: pending (Pending), allowed (Allowed), rejected (Rejected), amended (Amended), cancelled (Cancelled). |
claimText | text (multi-line) | Full claim text. |
Relationships
- No declared relationships in the default definition.
Creating a Patent Claim via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PATENTCLAIM",
"level": 430,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"claimNumber": 100,
"claimType": "independent",
"status": "pending"
}Listing PATENTCLAIM records
# All patent claims in your tenant
GET /v1/entities/PATENTCLAIM/SUB