---
title: "Update Detail"
method: PUT
path: "/detail/{detail_id}"
tags: ["Detail"]
---

# Update Detail

`PUT /detail/{detail_id}`

Update a Detail with the `id`, placed in the parameters. Only the provided fields in the request body will be updated, the rest will remain unchanged. If skills are provided, old skills will be deleted and new skills will be created in place.

If Detail `status` is _Sent_, it can **not** be updated. You can copy the Detail with the `/Copy` address if you wish to use an edited version of the original Detail.

Details for the body of the request:

- `type` enum value, the type of event which the credential is being issued for
- `title` the credential title
- `description` the credential description
- _Duration_ the duration of the event
  - The duration is a combination of two fields `durationNumber` and `durationType`
  - `durationNumber` indicates the integer value for the `durationType` enum value which is the unit time
- `cost` enum value, the cost of the event or course
- _Expire Date_ expire date of the credential, **not required**
  - There are **two different options for the expire date of the credential**
    1. Set an exact expire date for every credential sent with this _Detail_ (ex: 01/01/2023). This option uses `expireDate` (DateTime) field
    2. Set a time span which will be added to the credential's issue date (ex: 2 years). This option uses `expireDateNumber` (int) and `expireDateType` (DurationType enum) fields
  - If none of these options are used, the expire date will be set to _null_
- `level` enum value, level of the event or course
- `earningCriteria` the information given as earning criteria for the course or event, **not required**
  - The input can be given as HTML code, the HTML will be rendered in the credential verification page below the "Earning Criteria" title
- `skills` the skills related to the Detail, minimum one skill is required for the `status` to be _Ready_
  - The skills can be obtained from the `/SearchSkills` address
    - The `skillId` field can be retrieved from the `/SearchSkills` address, this field can be left blank to add custom skills to the Detail
  - `languageCode` has to be _en_ or _tr_
- `dontSendExpireDateEmail` field is a boolean field used for controlling if users should be notified automatically when the expire date of credential is approaching

## Path parameters

- `detail_id` string, required

## Headers

- `api-version` string, required

## Request body

- DetailRequest
  - `type` integer — Detail type enum (0=Field Event, 1=Online Event, 2=Class Course, 3=Online Course, 4=Webinar, 5=Achievement, 6=License, 7=Appreciation, 8=Promotional Course, 9=Membership, 10=Graduation, 11=Hybrid Event, 12=Hybrid Course)
  - `title` string
  - `description` string
  - `durationNumber` integer
  - `durationType` integer — Duration type enum (1=Hour, 2=Day, 3=Week, 4=Month, 5=Year, 6=Minute)
  - `cost` integer — Cost enum (0=Free, 1=Paid, 2=NA)
  - `expireDate` string, date, nullable
  - `expireDateNumber` integer, nullable
  - `expireDateType` integer, nullable — DurationType enum value
  - `level` integer — Level enum (0=Beginner, 1=Intermediate, 2=Advanced, 3=Experienced, 4=Professional, 5=NA)
  - `earningCriteria` string, nullable — Earning criteria, can be HTML
  - `dontSendExpireDateEmail` boolean
  - `skills` Skill[]
    - `skillId` string — Skill ID from /detail/searchSkills, leave blank for custom skills
    - `title` string
    - `languageCode` string — Must be 'en' or 'tr'
  - `expiryReminderDays` integer[] — List of days before expire date to send reminders (max 3)

## Response `200`

Successful response

- ApiResponse
  - `message` string, nullable
  - `hasError` boolean
  - `validationErrors` string[]
  - `data` unknown
  - `content` unknown

---

[API](https://skmtc.net/sertifier/apis/sertifier-credential-api-documentation.md) · [All operations](https://skmtc.net/sertifier/apis/sertifier-credential-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sertifier/sertifier-credential-api-documentation/revisions/98c494325aae/schema)