For the complete documentation index, see llms.txt. This page is also available as Markdown.

Agreement

The Agreement object represents an instance of a relationship between the seller, buyer, and licensee. It may refer to one-time purchases or a set of subscriptions.

This object contains the following attributes:

Field
Type
Description

id

string

(Read-only) The primary identifier for the account.

status

string

The key status of the object. May only be specified on creation and cannot be updated with PUT.

name

string

The agreement name. The value is assigned automatically when the agreement is created, as {product.name} for {licensee.name}. The value can be changed later.

vendor

object

(Read-only) Represents the vendor account object filled in upon creation, according to the product.

client

object

Represents the client account object.

buyer

object

(Read-only) Represents the buyer object.

seller

object

(Read-only) Represents the seller object.

licensee

object

Represents the licensee object.

product

object

Represents the product object.

Example:

listing

listing

Represents the listing that allows this agreement.

Example:

authorization

object

(Read-only) Represents the authorization object used for the agreement.

price

object

(Read-only) Represents the agreement’s pricing details. Monthly and yearly prices exclude one‑time charges. Visibility of specific price fields varies by actor, as defined within the price object.

Example:

template

object

Represents the template object.

Example:

error

object

Represents the error object,containing a markup‑formatted text string that explains the reason for provisioning failure.

Example:

lines

object

Represents the line object, containing a list of items in the agreement.

Example:

subscriptions

object

Represents the subscription within the agreement.

parameters.fulfillment

object

(Optional) Represents the orderParameter object containing a concise definition of a parameter, its value, and any associated errors.

Example:

parameters.ordering

object

(Optional) Represents the orderParameter object containing a concise definition of a parameter, its value, and any associated errors.

Example:

audit

object

(Read-only) Represents the audit object.

externalIds

object

(Optional) Represents a set of externalIds.

termsAndConditions

object

(Read‑only) Represents the terms and conditions of the product that were accepted as part of the order. These values are then copied from the order into the agreement when the order is completed.

Examples

Last updated

Was this helpful?