Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Nectr-AI/nectr-ai-pr-review-agent/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Disconnects a repository from Nectr AI by removing the GitHub webhook and marking the installation as inactive. After disconnection, PR events from this repository will no longer trigger AI reviews.
Authentication
Requires a valid JWT token in the Authorization header.
Authorization: Bearer <token>
Path Parameters
Repository owner (user or organization)
Request
curl -X DELETE "https://api.nectr.ai/api/v1/repos/acme/my-backend/install" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"
Response
Always returns "disconnected" on success
Full repository name in owner/repo format
Example Response
{
"status": "disconnected",
"repo": "acme/my-backend"
}
What Happens During Disconnection
1. Webhook Removal
If the installation has a webhook_id, the endpoint attempts to delete the webhook from GitHub using:
DELETE https://api.github.com/repos/{owner}/{repo}/hooks/{webhook_id}
2. Installation Deactivation
The Installation record is marked as inactive:
installation.is_active = False
3. Data Retention
Preserved:
- Installation record (marked
is_active = False)
- Neo4j code graph (Repository, File, PullRequest, Developer nodes)
- Historical PR review data
Effect:
- No new webhook events will be processed
- Repository will show as disconnected in
/api/v1/repos
- User can reconnect later without data loss
Error Responses
JWT token is invalid, expired, or missing{
"detail": "Unauthorized"
}
GitHub OAuth token cannot be decrypted (SECRET_KEY changed){
"detail": "Session expired — please log out and sign in again."
}
No active installation found for this repository and user{
"detail": "Installation not found"
}
- The repository was never connected
- The repository is already disconnected
- The repository belongs to a different user
Webhook Removal Failure Scenarios
The endpoint handles webhook deletion gracefully:
| Scenario | Behavior |
|---|
| Webhook deleted manually on GitHub | Warning logged, disconnection succeeds |
| User lost admin permissions | Warning logged, disconnection succeeds |
| GitHub API unavailable | Warning logged, disconnection succeeds |
| Network timeout | Warning logged, disconnection succeeds |
Permissions Required
GitHub OAuth Scopes
repo - Required to delete webhooks
Repository Access
The authenticated user must have admin permissions on the repository to remove webhooks. If permissions are lost, webhook removal will fail gracefully.
Reconnection
After disconnection, you can reconnect the same repository using the Connect Repository endpoint. The previous installation record will remain inactive, and a new active installation will be created.