ConnectedApplicationsByBearerToken: Loket.nl REST itgen_loketnl_connectedapplicationsbybearertoken_plural
read only REST
- Catalog:
LoketNlRest - Schema:
ConnectedApplications - Label: itgen_loketnl_connectedapplicationsbybearertoken_plural
List of all the connected applications for the logon user Activity name: GetConnectedApplicationsByBearerToken
List of all the connected applications for the logon user.
The difference between integrations and connected applications is as follows
- integrations = from lokets point of view an incomming connection where a different application connects with the loket API
- connected applications = from lokets point of view an outgoing connection where a loket connects with the API of a different application
Can only retrieve data.
API Source
- Endpoint:
/users/connectedApplications - Operation:
get /users/connectedApplications
Table Columns
The columns of the table ConnectedApplicationsByBearerToken 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 |
|---|---|---|---|---|---|
application |
varchar2 |
itgen_loketnl_applicationprovider_description | |||
application |
guid |
itgen_loketnl_applicationprovider_id | The unique identifier of an object (GUID/UUID) | ||
created |
datetime |
Created on | The time the integration was succesfully initiated | ||
description |
varchar2 |
Description | Descrition of the connection | ||
id |
guid |
ID | The unique identifier of an object (GUID/UUID) | ||
key |
int32 |
Key | because users tend te use the same description for multiple connected applications we added this field as an extra unique identifier | ||
last |
datetime |
itgen_loketnl_lastusedon | The time the integration was last active |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver: