---
title: "Create a Contact Profile"
method: POST
path: "/v2.0/profiles"
tags: ["Contact Profiles"]
---

# Create a Contact Profile

`POST /v2.0/profiles`

Creates a [Contact Profile](https://docs.cognigy.com/ai/agents/analyze/contact-profiles).

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Request body

- object
  - `profile` object
    - `prevent_data_collection` boolean
    - `accepted_gdpr` boolean
    - `privacy_policy` object
    - `tasks` string[]
    - `memories` object[] — Array of memories associated with the profile.
      - `id` string — Unique identifier for the memory
      - `timestamp` string, date-time — The timestamp of when the memory was created
      - `text` string — The text content of the memory
    - `firstname` string
    - `lastname` string
    - `email` string, email
    - `profilepic` string
  - `active` boolean
  - `contactIds` string[]
  - `projectId` string — The unique identifier for the Project.

## Response `201`

Returns Profile object.

- object — The IEntityMeta defines meta information every entity within the system has. These are dates when a resource was created and modified as well as information about the user who initially created a resource and who modified it the last time.
  - `profile` object
    - `prevent_data_collection` boolean
    - `accepted_gdpr` boolean
    - `privacy_policy` object
    - `tasks` string[]
    - `memories` object[] — Array of memories associated with the profile.
      - `id` string — Unique identifier for the memory
      - `timestamp` string, date-time — The timestamp of when the memory was created
      - `text` string — The text content of the memory
    - `firstname` string
    - `lastname` string
    - `email` string, email
    - `profilepic` string
  - `active` boolean
  - `contactIds` string[]
  - `_id` string
  - `createdAt` integer — Unix-timestamp
  - `lastChanged` integer — Unix-timestamp
  - `createdBy` string
  - `lastChangedBy` string

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/versions/85b2872bdfb7/schema)