---
title: "Delete a build certificate"
method: DELETE
path: "/apps/{app-slug}/build-certificates/{build-certificate-slug}"
tags: ["build-certificate"]
---

# Delete a build certificate

`DELETE /apps/{app-slug}/build-certificates/{build-certificate-slug}`

## Request

- Base URL: `https://api.bitrise.io/v0.1`
- URL: `https://api.bitrise.io/v0.1/apps/{app-slug}/build-certificates/{build-certificate-slug}`
- Auth: API key in header `Authorization`

Delete an app's build certificate. You can fetch the build certificate slug for this endpoint if you first call the [GET /apps/{app-slug}/build-certificates](https://api-docs.bitrise.io/#/build-certificate/build-certificate-list) endpoint to list all available build certificates of an app. Read more in our [Deleting an iOS code signing file](https://devcenter.bitrise.io/api/managing-ios-code-signing-files/#deleting-an-ios-code-signing-file) guide.

## Path parameters

- `app-slug` string, required
- `build-certificate-slug` string, required

## Response `200`

OK

- V0BuildCertificateResponseModel
  - `data` V0BuildCertificateResponseItemModel
    - `certificate_password` string
    - `certificates` V0BuildCertificateContentModel[]: Read-only. The signing certificates contained in the .p12 file. A single .p12 can bundle several independent certificates (for example a development and a distribution one), so this is always an array. The entries keep the order the .p12 itself stores them in (its ASN.1 sequence order) and are not re-sorted. Computed server-side once the file is processed; never null, but empty until then or when the extraction failed.
      - `expiry_date` string, date-time: Read-only. This certificate's notAfter date in RFC 3339 / ISO 8601 (UTC). Computed server-side once the file is processed; null when it could not be extracted from the certificate.
      - `serial` string: Read-only. X.509 serial number of this certificate, rendered as uppercase hexadecimal. Computed server-side once the file is processed; null when it could not be extracted from the certificate.
    - `file_sha256` string: Read-only. SHA-256 hash of the uploaded file bytes, rendered as lowercase hexadecimal. Computed server-side once the file is processed; null until then.
    - `is_expose` boolean
    - `is_protected` boolean
    - `processed` boolean
    - `slug` string
    - `upload_file_name` string
    - `upload_file_size` integer

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/bitrise/apis/bitrise-api.md) - [All operations](https://skmtc.dev/bitrise/apis/bitrise-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bitrise/apis/bitrise-api/revisions/859a161f2622?raw)