Merjax API
Merjax API as documented publicly: 72 operations. Contract generated from the documentation by API Evangelist (2026-11-10); not the provider's own document.
Operations 72
GET
/api/v2/admin/estate/ratings
Every repository of every account with its letter, score, trend against the previous recorded day and the next item to A (site admin)
#
DELETE
/api/v2/repos/{owner}/{repo}
Delete repository (owner only: the personal owner, or an org owner)
#
GET
/api/v2/repos/{owner}/{repo}/actions/jobs/{jobId}/logs
One job's log as plain text, masked as stored.
#
GET
/api/v2/repos/{owner}/{repo}/actions/runs/{runId}/jobs
A run's jobs: status, conclusion, steps and exit code, no log text
#
GET
/api/v2/repos/{owner}/{repo}/actions/runs/{runId}/logs
Logs: a ZIP by default; format=text or Accept: text/plain for plain text, format=json for steps, failedSteps and testFailures.
#
POST
/api/v2/repos/{owner}/{repo}/actions/runs/{runId}/rerun-failed
Re-run a failed or cancelled run at the same commit (every job is re-run)
#
GET
/api/v2/repos/{owner}/{repo}/branches/{branch}/protection
The rule that applies (404 when the branch is not protected)
#
GET
/api/v2/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks
Required checks, GitHub shape {contexts, checks, strict}
#
POST
/api/v2/repos/{owner}/{repo}/deploy-tokens
Create a deploy token; the secret is in this response only
#
POST
/api/v2/repos/{owner}/{repo}/issues/{number}/labels
Add labels to an issue: {labels, createMissing?}. Idempotent; 422 names a missing label unless createMissing
#
DELETE
/api/v2/repos/{owner}/{repo}/issues/{number}/labels/{name}
Remove a label from an issue (idempotent)
#
PATCH
/api/v2/repos/{owner}/{repo}/pulls/{number}
Edit title, body or base — the author or write access; draft under the Ready / Draft buttons' rule
#
DELETE
/api/v2/repos/{owner}/{repo}/pulls/{number}/auto-merge
Disarm auto-merge — the merge train then leaves the PR alone; an explicit merge still works
#
GET
/api/v2/repos/{owner}/{repo}/pulls/{number}/auto-merge
Armed? last_attempt.reason says what it waits for
#
PUT
/api/v2/repos/{owner}/{repo}/pulls/{number}/auto-merge
Arm auto-merge: merges through the gated chain once CI and every required check pass and no reviewer requests changes
#
GET
/api/v2/repos/{owner}/{repo}/pulls/{number}/checks
Every check at the head (workflow runs, gates, commit statuses) with conclusion, required flag, log_url (a run's logs as plain text) and archive_url (the same logs as a ZIP)
#
GET
/api/v2/repos/{owner}/{repo}/pulls/{number}/conflicts
What stands between the PR and a clean merge, as the merge gate sees it: status, each unresolved file with its kind in plain words, files the merge rules settle, saved drafts
#
POST
/api/v2/repos/{owner}/{repo}/pulls/{number}/conflicts/commit
Commit the drafts (or an explicit resolutions list) on the PR head as a two-parent merge commit through the push gates
#
PUT
/api/v2/repos/{owner}/{repo}/pulls/{number}/conflicts/file
Save a resolution draft for one conflicted file at the exact (base_sha, head_sha) pair
#
POST
/api/v2/repos/{owner}/{repo}/pulls/{number}/conflicts/propose
Ask AI to propose a resolution for each conflict block
#
POST
/api/v2/repos/{owner}/{repo}/pulls/{number}/merge
Merge through the gated chain; a refusal names each required check that is not passing (missingChecks)
#
POST
/api/v2/repos/{owner}/{repo}/pulls/{number}/update-branch
Merge the base into the head (never a force-push); 409 lists conflictFiles
#
GET
/api/v2/repos/{owner}/{repo}/rating
The repository's letter rating A+/A/B/C/D/F — the health report's grade (A is 85+) — with the score, the six categories, `to_a`...
#
GET
/api/v2/repos/{owner}/{repo}/webhooks
List webhooks (secret never returned: masked, plus hasSecret)
#
GET
/api/v2/user/ready-to-merge
Every PR that is green and clean and not armed in a repository you can merge in, plus the PRs waiting on your review
#
Specifications
Schemas & Data
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-put-api-v2-repos-owner-repo-branches-branch-protection-request-schema.json
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-put-api-v2-repos-owner-repo-pulls-number-conflicts-file-request-schema.json
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-post-api-v2-repos-owner-repo-pulls-number-conflicts-commit-request-schema.json
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-post-api-v2-repos-owner-repo-pulls-request-schema.json
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-post-api-v2-repos-owner-repo-pulls-number-conflicts-propose-request-schema.json
JSONSchema
https://artifacts.apis.io/gluecron-com/json-schema/gluecron-com-post-api-v2-orgs-org-repos-request-schema.json