Line Attributes Overview

line attributes are admin defined, line level inputs that map one rep facing value to one salesforce field and carry it across the commercial record (pricebook entry → quote line item → order product → subscription → billing) the line attributes api lets you manage attribute definitions programmatically — create, read, update, delete, and activate them — the same objects you manage in settings → price builder → line attributes this is how a revops admin scripts attribute setup, keeps configuration in source control, or lets an ai agent define attributes the api runs on the same object as the settings ui, so an attribute created through the api behaves exactly like one created in the app for the concept, the admin ui, and how reps set values on a quote, see line attributes https //docs nue io/line attributes in the knowledge center definitions vs values this section covers managing attribute definitions to set the value of a line attribute on a specific quote or order line, set the mapped custom field on the line through the create or update quote & order methods — the value is a custom field keyed by the mapped field's salesforce api name required permission the line attribute object is gated by the system settings feature your api key's role must be permitted to manage system settings (the same capability as manage line attributes in the app) base url use your tenant's nue api host it is environment specific and is not necessarily api nue io — a sandbox tenant is served from https //api sandbox nue io confirm your host in the nue app; do not infer it from a salesforce named credential examples in this section use {baseurl} endpoints endpoint method description /api/objects/lineattribute post create guides and examples/customer lifecycle/cpq revenue lifecycle/line attributes/create line attributes mdx a line attribute definition /async/graphql post fetch guides and examples/customer lifecycle/cpq revenue lifecycle/line attributes/fetch line attributes mdx line attributes via graphql /api/objects/lineattribute/{id} patch update guides and examples/customer lifecycle/cpq revenue lifecycle/line attributes/update line attributes mdx a line attribute (including activation) /api/objects/lineattribute/{id} delete delete guides and examples/customer lifecycle/cpq revenue lifecycle/line attributes/delete line attributes mdx an inactive line attribute /api/metadata/objects/lineattribute get describe the object (fields, value sets) the object apiname is lineattribute — not the salesforce lineattribute c name, which is rejected field names are nue camelcase apinames see the line attribute data reference guides and examples/customer lifecycle/cpq revenue lifecycle/line attributes/line attribute data reference mdx for the full field list authentication include your api key in the nue api key header curl '{baseurl}/api/metadata/objects/lineattribute' \\ h 'nue api key your api key' draft vs active isactive controls the attribute's lifecycle, and activation has a side effect on the transition into active, nue provisions the mapped field across the five line objects (quote line item, order product, subscription, asset, entitlement), adds it to the fields expose to nue field sets, and runs a business objects sync create as a draft ( "isactive" false ) to register the attribute without provisioning this is the only way to create a line attribute in a not yet active state — the admin ui requires at least one surface and creates it active activate by setting "isactive" true (on create or a later update) if provisioning fails, activation fails and the record stays a draft