> ## Documentation Index > Fetch the complete documentation index at: https://docs.support.onclarity.com/llms.txt > Use this file to discover all available pages before exploring further. # Delete an outbound SIP trunk > Deletes the trunk. A trunk still listed in a phone number's `outbound_trunk_ids` cannot be deleted: remove it from those numbers first (409, with their ids in `referenced_by`). Needs the publish permission, which organization API keys carry. ## OpenAPI ````yaml api-reference/voice-openapi.json DELETE /v1/projects/{projectId}/telephony/outbound-trunks/{id} openapi: 3.0.3 info: title: Clarity Voice API version: '1.0' description: >- Voice agents and their tools, outbound calls, conversations, campaigns, telephony, and evals. servers: - url: https://voice-api.onclarity.com security: - organizationApiKey: [] tags: - name: Projects description: >- The projects your organization owns. Every other resource lives in a project. - name: Agents description: Create, configure, version and publish voice agents. - name: Outbound calls description: Have a published agent phone a number now. - name: Conversations description: >- One record per call session, with its calls, recordings, transcripts and artifacts. - name: Calls description: The calls of a project, with their status, direction, timing and outcome. - name: Campaigns description: Outbound calling campaigns that phone a list of numbers on a schedule. - name: Eval suites description: >- Reusable sets of eval scenarios and test cases to measure an agent against. - name: Eval judges description: The LLM judges that score eval calls against your test cases. - name: Eval scenarios description: The simulated-caller scenarios of your eval suites. - name: Eval test cases description: The checks a judge applies to each eval call. - name: Eval submissions description: Run an eval suite against an agent and read the verdicts. - name: Phone numbers description: >- The phone numbers of a project, where their calls come from, and how agents call out from them. - name: Inbound SIP trunks description: Bring calls from your own SIP infrastructure to Clarity agents. - name: Outbound SIP trunks description: >- The SIP endpoints Clarity dials through for outbound calls from your numbers. - name: Tools description: The tools agents call during a conversation, and which agents use them. paths: /v1/projects/{projectId}/telephony/outbound-trunks/{id}: parameters: - $ref: '#/components/parameters/ProjectIdPath' - name: id in: path required: true schema: type: string description: Outbound SIP trunk id delete: tags: - Outbound SIP trunks summary: Delete an outbound SIP trunk description: >- Deletes the trunk. A trunk still listed in a phone number's `outbound_trunk_ids` cannot be deleted: remove it from those numbers first (409, with their ids in `referenced_by`). Needs the publish permission, which organization API keys carry. operationId: deleteTelephonyOutboundTrunk responses: '204': description: The trunk was deleted. '401': $ref: '#/components/responses/Unauthorized' '403': description: 'Your credential cannot delete (`code: PUBLISH_CAPABILITY_REQUIRED`).' content: application/json: schema: $ref: '#/components/schemas/Error' example: error: publish_capability_required code: PUBLISH_CAPABILITY_REQUIRED '404': description: The project or the trunk does not exist. content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: Phone numbers still use the trunk; `referenced_by` lists their ids. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - type: object properties: referenced_by: type: array items: type: string description: >- Ids of the phone numbers whose `outbound_trunk_ids` include this trunk. example: error: >- Outbound trunk is referenced by one or more phone numbers; detach it first referenced_by: - 7b0e2c4a-1f3d-4e8a-9c21-5d6f7a8b9c01 components: parameters: ProjectIdPath: name: projectId in: path required: true schema: type: string description: Project id responses: Unauthorized: description: >- No credential was sent, or the API key is invalid or revoked. A key that could not be checked at all answers 503 `AUTH_UPSTREAM_UNAVAILABLE` instead (see Errors). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid or revoked token schemas: Error: type: object required: - error additionalProperties: true properties: error: type: string description: Error message code: type: string description: >- A stable machine-readable reason, present on the refusals a client may branch on. Among them: `PUBLISH_CAPABILITY_REQUIRED` (403, the credential may not change what is live), `AGENT_NOT_PUBLISHED` (409, the agent has no published version yet), `AGENT_TYPE_NOT_DISPATCHABLE` (422, a Voice Assist agent named where an agent must place a call or answer one itself — a campaign, an outbound caller ID, a dispatched call, an eval; a number's inbound dispatch rule accepts one; the body carries `agent_type` and `agent_id`), `ASSIST_FLEET_NOT_CONFIGURED` (422 on a dispatch rule naming a Voice Assist agent in a project whose LiveKit has no Voice Assist listener), `NOT_APPLICABLE_TO_AGENT_TYPE` (422, a voice-only setting written on a Voice Assist agent), `AGENT_TYPE_BOUNDARY` (409), `AGENT_TYPE_NOT_SUPPORTED` (400), `INVALID_CUSTOMER_TIMEZONE` (400, `customer_timezone` is not a time zone name; the body carries the value), `VOICE_ASSISTANT_REQUIRED` (403, the organization is not licensed for Voice Assist), `ORGANIZATION_UNAVAILABLE` (503), `REGION_PROFILE_CONFLICT` (503), `LLM_SERVICE_TIER_UNAVAILABLE` (422, an agent's processing speed is not offered by its model or not enabled for the organization; `reason` says which) and `AUTH_UPSTREAM_UNAVAILABLE` (503 on any endpoint, with `Retry-After`: the credential could not be checked right now; it was not rejected and the request was not carried out). securitySchemes: organizationApiKey: type: http scheme: bearer description: >- Your organization API key (it starts with `anek_org_`). The same key works on the Voice API and the Support API. See [Authentication](/authentication). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.