MEA price lists contain standalone selling prices for items sold in multiple-element arrangements. A company that provides multiple products and/or services to customers as part of a single arrangement needs to create one or more MEA price lists. A contract that contains multiple-element arrangements can be linked to an MEA price list.
Returns up to 100 MEA price lists from the collection with a key, ID, and link for each list. This operation is mostly for use in testing; use the query service to find MEA price lists that meet specific criteria and to specify the properties that you want in the response.
Subscription | Contract Core Billing or Contract Usage Billing |
---|---|
User type | Business, Employee, Project Manager, Warehouse |
Permissions | List Contract MEA Price Lists |
OK
Bad Request
{- "ia::result": [
- {
- "key": "30",
- "id": "CONMEA_FVPriceBand_Amount_USD",
- "href": "/objects/contracts/mea-price-list/30"
}, - {
- "key": "31",
- "id": "CONMEA_FVPriceBand_Amount_EUR",
- "href": "/objects/contracts/mea-price-list/31"
}, - {
- "key": "32",
- "id": "CONMEA_FVPriceBand_Amount_GBP",
- "href": "/objects/contracts/mea-price-list/32"
}, - {
- "key": "33",
- "id": "CONMEA_FVPriceBand_Amount_INR",
- "href": "/objects/contracts/mea-price-list/33"
}
], - "ia::meta": {
- "totalCount": 4,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new MEA price list.
Subscription | Contract Core Billing or Contract Usage Billing |
---|---|
User type | Business |
Permissions | Add Contract MEA Price Lists |
MEA price list to create
id required | string Unique name or ID for the MEA price list. Example: "Subscription MEA price list" |
description | string Description of the MEA price list. Example: "Fair value for high-volume customers" |
isDefault | boolean Set to Example: false |
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
Created
Bad Request
{- "status": "active",
- "id": "CONMEA_FVPriceBand_Amount_USD_1",
- "description": "MEA NearestBoundary PriceBand Amount"
}
{- "ia::result": {
- "key": "39",
- "id": "CONMEA_FVPriceBand_Amount_USD_2",
- "href": "/objects/contracts/mea-price-list/39"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified MEA price list.
Subscription | Contract Core Billing or Contract Usage Billing |
---|---|
User type | Business, Employee, Project Manager, Warehouse |
Permissions | View Contract MEA Price Lists |
key required | string System-assigned key for the MEA price list. Example: 61 |
OK
Bad Request
{- "ia::result": {
- "key": "37",
- "audit": {
- "createdDateTime": "2023-06-08T06:06:15Z",
- "modifiedDateTime": "2023-06-08T06:06:15Z",
- "createdBy": "1",
- "modifiedBy": "1"
}, - "status": "active",
- "id": "CONMEA_FVPriceBand_Amount_USD_2",
- "description": "MEA NearestBoundary PriceBand Amount",
- "isDefault": false,
- "href": "/objects/contracts/mea-price-list/37"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Update an existing MEA price list by setting field values. Any fields not provided remain unchanged.
Subscription | Contract Core Billing or Contract Usage Billing |
---|---|
User type | Business |
Permissions | Edit Contract MEA Price Lists |
key required | string System-assigned key for the MEA price list. Example: 61 |
description | string Description of the MEA price list. Example: "Fair value for high-volume customers" |
isDefault | boolean Set to Example: false |
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
OK
Bad Request
{- "status": "active"
}
{- "ia::result": {
- "key": "38",
- "id": "CONMEA_FVPriceBand_Amount_USD",
- "href": "/objects/contracts/mea-price-list/38"
}, - "ia::meta": {
- "totalCount": 1
}
}
Deletes an MEA price list. You can delete an MEA price list if it has not been used by any contracts. Deleted price lists cannot be recovered. Alternatively, you can change the status to Inactive, which prevents it from being used but retains the price list for historical purposes.
Subscription | Contract Core Billing or Contract Usage Billing |
---|---|
User type | Business |
Permissions | Delete Contract MEA Price Lists |
key required | string System-assigned key for the MEA price list. Example: 61 |
No Content
Bad Request
{- "ia::result": {
- "ia::error": {
- "code": "invalidRequest",
- "message": "A POST request requires a payload",
- "errorId": "REST-1028",
- "additionalInfo": {
- "messageId": "IA.REQUEST_REQUIRES_A_PAYLOAD",
- "placeholders": {
- "OPERATION": "POST"
}, - "propertySet": { }
}, - "supportId": "Kxi78%7EZuyXBDEGVHD2UmO1phYXDQAAAAo"
}
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 0,
- "totalError": 1
}
}
Queries an object for filtered data.
object | string Object type to query, in the form Example: "contracts/mea-price-list" | ||||||||
fields | Array of strings List of fields to include in the response. Can be any combination of these:
Example: ["key","id","max:vendor.creditLimit"] | ||||||||
Array of equal (object) or not equal (object) or less than (object) or (less than or equal (object)) or greater than (object) or (greater than or equal (object)) or in (object) or not in (object) or between (object) or not between (object) or contains (object) or does not contain (object) or has (object) or starts with (object) or does not start with (object) or ends with (object) or does not end with (object) Filter conditions to select the objects to return based on their field values. You use operators and conditions to build your filter, such as Example: [{"$eq":{"status":"active"}},{"$gt":{"totalDue":"1000"}},{"$contains":{"name":"Acme"}}] | |||||||||
Array Any of: Field value must be equal to this specified value. For date fields, you can use these macro values that are relative to the current date or the
These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the For example,
| |||||||||
filterExpression | string Default: "and" Logical operators to apply when there are multiple filter conditions. The conditions in the Shortcuts:
Example: "(1 and 2) or 3" | ||||||||
| |||||||||
Array of objects Set the order of the results by specifying field names to sort by and whether they should be in ascending or descending order. Example: [{"totalDue":"asc"},{"lastPaymentMadeDate":"desc"}] | |||||||||
Array
| |||||||||
start | integer First record of the result set to include in the response. Example: 1 | ||||||||
size | integer Number of records to include in the result set, 4000 maximum. Example: 100 |
OK
Bad Request
{- "object": "contracts/mea-price-list",
- "filters": [
- {
- "$eq": {
- "status": "active"
}
}
], - "fields": [
- "key",
- "id",
- "description"
], - "orderBy": [
- {
- "id": "asc"
}
]
}
{- "ia::result": [
- {
- "key": "11",
- "id": "LightingMEAPL",
- "description": "MEA price list for lighting supplies"
}, - {
- "key": "12",
- "id": "PackagingMEAPL",
- "description": "MEA price list for packaging supplies and services"
}
], - "ia::meta": {
- "totalCount": 2,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}