neosourceDocs
Search docs

Remove a per-repo grant

DELETE/api/repos/{owner}/{repo}/grants/{grantee_kind}/{grantee_id}

removeRepoGrant

Required role: `repo:admin`. Idempotent: removing a non-existent grant returns 204.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X DELETE 'https://neosource.dev/api/repos/OWNER/REPO/grants/GRANTEE_KIND/GRANTEE_ID' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/grants/GRANTEE_KIND/GRANTEE_ID", {
  method: "DELETE",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
  },
});

Path parameters

ownerrequired

string

reporequired

string

grantee_kindrequired

`team` or `account`. Stays a `String` here — the route parses it with its own 400 error for unknown values.

string

grantee_idrequired

Team key (e.g. `ENG`) for `team` grants, or account handle for `account` grants.

string

Responses

204Grant removed

Standard errors

Bodies documented once for the whole API — see standard errors.

  • 400Bad Request — one of: invalid_input
  • 401Authentication required
  • 403Forbidden — one of: forbidden
  • 404Not Found — one of: not_found
  • 409Conflict — one of: already_exists, conflict, non_fast_forward
  • 423Locked — one of: busy
  • 429Rate limited — retry after the `Retry-After` header
  • 500Internal server error
  • 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
  • 504Gateway timeout — the request exceeded the server's handling budget