Customers | B2C

Add consents for many customers in one call. For each customer, a consent of a new type is added and a consent of an existing type is updated (the previous value is kept in consent history). Changed customers are indexed in bulk. Only existing customers are processed - unknown customers are skipped and returned in NotFoundIds. Max size in batch is 1000.

post/api/PrivateCustomers/Consents/AddMany

Request

Base URL: https://api.omnium.no (the document declares no server; this is the origin it was published from)
URL: https://api.omnium.no/api/PrivateCustomers/Consents/AddMany
Auth: API key in header Authorization

exportCustomersboolean nullable

If true - Omnium will trigger configured connectors to export updated customers

customerIdstring nullable

Id of the customer the consents should be added to.

Returns a summary of how many customers were updated, unchanged, and not found.

isModifiedboolean

True if at least one property on the customer was changed by the patch operation.

totalCountinteger

Total number of customers processed by the operation.

updatedCountinteger

Number of customers that were modified and persisted.

unchangedCountinteger

Number of customers that were processed but had no changes to apply.

notFoundCountinteger

Number of customers that could not be found and were therefore skipped.

notFoundIdsstring[] nullable

Ids of customers that could not be found and were therefore skipped. Null for single-customer operations.

errorCountinteger

Number of customers where the update failed due to an error.

errorMessagestring nullable

Concatenated error messages for any customers that failed to update. Each entry includes the customer id and the underlying error.

No recorded changes to this operation across all 1 revision of this API.