invantive documentation
Invantive Support ForumsLog In / Sign Up

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
contractId `` 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_CODE varchar2(30) Company Code writable Partition code, segmenting the data.
COMPANY_NAME varchar2(240) Company Name writable Name of the partition.
contract varchar2 Contract filters on the platform, writable, contract
lastModifiedDateTime datetime Last Modified filters on the platform, writable, lastModifiedDateTime
timeStamp blob Timestamp filters on the platform, writable, timeStamp 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: