Creates new profile associations with the specified organization unit
POST/organization-units/:organizationUnitId/profiles
Creates new profile associations with the specified organization unit
Request
Path Parameters
Id of the specified organization unit
- application/json
Body
required
Specifies the profiles to associate with the organization unit
The ids of the profiles to associate with the organization unit
Responses
- 201
- 401
- 403
- 404
- 422
- 429
- 500
Created
- application/json
- Schema
- Example (from schema)
Schema
The id of the profile
The reference of the profile
The name of the profile
The image uri of the profile
Possible values: [person, product, event, place]
The kind of the profile
The id of the category of the profile
The date and time when the profile was created
The date and time when the profile was updated
The date and time when the profile was deleted
{
  "id": "string",
  "reference": "string",
  "name": "string",
  "imageUri": "string",
  "kind": "person",
  "category_id": "string",
  "created_at": "2024-07-29T15:51:28.071Z",
  "updated_at": "2024-07-29T15:51:28.071Z",
  "deleted_at": "2024-07-29T15:51:28.071Z"
}
Unauthenticated
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}
Unauthorized
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}
Not found
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}
Unprocessable Entity
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}
Too Many Requests
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}
Unknown error
- application/problem+json
- Schema
- Example (from schema)
Schema
A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable
Possible values: >= 100 and < 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}