Associated Contact Types

Relationship types between customers and associated contacts (TipoContactoAsociado).

📄️ Get associated contact type by ID

Returns a single associated contact type by its primary key.

📄️ Update associated contact type

Full replacement of an existing associated contact type. Send the `If-Match` header for optimistic concurrency (accepted but ignored ÔÇö not versioned).

📄️ Delete associated contact type

Deletes an associated contact type. Send the `If-Match` header with the current ETag (accepted but ignored ÔÇö not versioned).

📄️ Merge-patch associated contact type

RFC 7396 merge-patch over `application/merge-patch+json`. Send only the fields you want to change; include a field with value `null` to remove it. Use the `If-Match` header for optimistic concurrency control.

📄️ List associated contact types

Returns a paginated list of associated contact types with envelope `{data, totalCount, skip, limit, hasMore}`. Supports optional RSQL `filter`, `sort` (default `name:asc`), `skip`/`limit` pagination and `modifiedAfter`/`modifiedBefore` bookends.

📄️ Create associated contact type

Creates a new associated contact type. Business logic runs in the legacy WAR.

📄️ Bulk delete associated contact types

Removes every id in `ids` as a single all-or-nothing transaction.

📄️ Bulk patch associated contact types

Applies the same `patch` to every id in `ids` as a single all-or-nothing transaction. Editable fields: `enabled`, `linkApp`.

📄️ Prototype associated contact type for a creation form

Returns a non-persisted associated contact type pre-populated with backend defaults (`enabled=true`, `linkApp=true`, current company, empty `name`). Optional JSON hints: `companyId`, `copyFromId`. Call `POST /api/v2/associated-contact-types` afterwards to persist.