Please enable JavaScript to view this site.

Navigation: Schema: Contact > Tables

PutContactByContactId

Edit a contact__Activity name :__ PutContactByContactId __Metadata :__ Possible options for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL.Edit the details of a contact

Catalog: LoketNlRest

Schema: Contact

This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API.

Select loket.nl (REST) API URL: /providers/employers/employees/contacts/{contactId}

Insert loket.nl (REST) API URL: /providers/employers/employees/contacts/{contactId}

Update loket.nl (REST) API URL: /providers/employers/employees/contacts/{contactId}

Delete loket.nl (REST) API URL: /providers/employers/employees/contacts/{contactId}

Field Selection Method: NotRequired

Base Path: content

Select loket.nl (REST) API Operation: put /providers/employers/employees/contacts/{contactId}

Table Function Parameters

The following parameters can be used to control the behaviour of the table function PutContactByContactId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

contactId

guid

 

The unique identifier of the employee contact detail

If-Match

string

 

Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations).

 

Table Function Columns

The columns of the table function PutContactByContactId are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

address_city

string(24)

 

City of the address

address_country_isoCode

string(2)

 

The ISO 3166-1 alpha-2 value for the country

address_country_key

int32

 

The key for the country. Posible values can be aquired via the metadata endpoint

address_country_value

string(50)

 

The name of the country

address_houseNumber

int32

 

House number of the address

address_houseNumberAddition

string(4)

 

An addition to further specify the house/door/postbox. For example used to specifty a room of floor number in addition to the house number.

address_postalCode

string(9)

 

The postal code of the address

address_street

string(24)

 

Streetname of the address

description

string(50)

 

Describes the relationship of the contact to the employee

id

guid

 

The unique identifier of an object (GUID/UUID)

name

string(70)

 

Name of the contact

particularities

string(4000)

 

Extra information about the contact

phoneNumber

string(15)

 

The phone number of the contact

 

25-05-2022 14:15 Version 22.1.46-BETA+3385