Hanzo
OpenapiGit

Delete a repository over the ZAP transport

Deletes the repository named by `name` and answers with the deleted name.

POST /v1/git/zap/deleteRepo

Addresshttps://api.hanzo.ai/v1/git/zap/deleteRepo
MethodPOST
Operationpost_git_zap_deleterepo
AuthAuthorization: Bearer $HANZO_API_KEY

Deletes the repository named by name and answers with the deleted name. A repository outside the caller's org and project scope is a 404 envelope, so a delete can never reach another tenant's repository.

A ZAP PROCEDURE, not a REST resource. It answers the bridge's {status, msg, data} envelope rather than the raw view the /v1 route returns — which is a wire shape a typed op cannot produce, and the reason this stays a raw handler — and it calls the SAME core function the REST route calls, so the two transports cannot diverge in behaviour. Org and project scope come from the request identity and NEVER from the body: the body cannot widen the caller's scope. Without a validated org the answer is a 403 envelope.

Request

3 fields, body application/json.

FieldInTypeRequiredDescription
descriptionbodystring
namebodystring
projectbodystring

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo git zap deleteRepo

Git API · All Hanzo APIs · Interactive reference

How is this guide?

On this page