ContractUsageSpecificByContractId: Visma.net Financials Contract Usage by Contract ID
read only REST
- Catalog:
VismaNet - Schema:
ContractUsage - Label: Contract Usage by Contract ID
Get a specific Contract Usage Data for the Contract Usage The response headers include an ETag after a successful GET operation.
Can only retrieve data.
Summary
Data for the Contract Usage
The response headers include an ETag after a successful GET operation.
API Source
- Endpoint:
/v1/contractUsage/{contractId} - Operation:
get /v1/contractUsage/{contractId}
Performance Characteristics
| Characteristic | Value |
|---|---|
| Average access latency (ms) | 155 |
| Full scan rows per minute | 29,100 |
| Point query rows per minute | 387 |
The result can be cached on the client.
Parameters
| Name | Data Type | Required | Default | Documentation |
|---|---|---|---|---|
contract |
`` | Identify the Contract Usage |
Table Columns
The columns of the table ContractUsageSpecificByContractId are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.
| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|---|---|---|
COMPANY_ |
varchar2 |
Company Code | writable | Partition code, segmenting the data. | |
COMPANY_ |
varchar2 |
Company Name | writable | Name of the partition. | |
contract |
varchar2 |
Contract | filters on the platform, writable, contract |
||
last |
datetime |
Last Modified | filters on the platform, writable, last |
||
time |
blob |
Timestamp | filters on the platform, writable, time |
Identifier that represents a specific version of the resource. It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers) |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver: