Failure modes you can see
All errors are application/problem+json; branch on code. Some codes add fields to the problem body
(listed in the last column).
code | HTTP | Meaning | What to do / extra fields |
|---|---|---|---|
auth_failed | 401 | Bad key, signature or stale timestamp | Check clock skew and the signing string |
credentials_revoked | 401 | The request was signed correctly, but Melee has revoked your apiSecret and callbackSecret. Every request is refused and no callback is sent | Contact Melee, then claim and confirm new credentials. See Credential revocation and reclaim |
claim_not_pending | 409 | POST /resolvers/credentials/claim: no claim is open (credentials not revoked, not reissued yet, window cancelled, or claimed credentials already confirmed) | Contact Melee |
claim_expired | 410 | POST /resolvers/credentials/claim: the claim window closed; nothing was issued | Ask Melee to reissue your credentials |
temporarily_unavailable | 503 | Melee could not check or complete the request (a dependency on our side is down); nothing was changed | Retry the same request (same Idempotency-Key) after Retry-After |
resolver_suspended | 403 | Melee suspended your resolver (bad faith); only reads are allowed | Contact Melee |
invalid_config | 422 | Registration or update failed validation; nothing was created or changed | errors: [{ field, reason, message }], one entry per invalid field, each with a stable reason, for example required, too_long, invalid_value, contains_link, not_approved or name_taken. On PATCH /resolvers/me also unknown_field (not a field of the endpoint, usually a typo), read_only (set by Melee: resolverId, state, verified, network) and not_patchable (a field PATCH can’t change: one changed on another endpoint, one set at registration, or a key change that is coming soon; message says which) |
smoke_check_failed | 422 | Activation probes failed | checks: [...]; fix and retry activate |
market_not_bound | 404 | You are not this market’s resolver | — |
market_not_active | 409 | Market not live or already terminal, or the outcome you propose is already the standing proposal | detail names the state |
not_yet_open | 409 | Too early: propose, resolve or void before the market’s earliestProposalTs; nothing was issued | opensAt (Unix seconds); retry from then. See Contract versions for void |
definition_mismatch | 409 | Your definitionHash is not the current version | currentVersion, currentHash; re-read the definition |
proposal_required | 409 | Disputable resolver called resolve without a standing proposal | Call propose |
proposal_mismatch | 409 | Requested outcome differs from the standing proposal (or a void proposal stands) | Call propose with the new outcome, or void |
change_window_closed | 409 | The change is not allowed in the market’s current phase | See Changes to a market |
change_not_found | 404 | The market has no change with this changeId | Check the id in GET /markets/{market}/changes |
change_already_decided | 409 | The rules request was already answered differently, or by a rules update | status when known; a request takes one answer |
change_rejected | 409 | The counter-party rejected the change | reason |
invalid_change | 422 | A rules update changed a field other than rules, or the hash did not match, or its changeId does not name an unanswered rules request; or a decision names a change that is not a rules request | errors[].field names the field; rebuild from the current version |
outcome_not_found / outcome_ambiguous | 422 | Outcome reference did not match exactly one outcome | Use outcomeIndex |
transaction_expired | 410 | Signed transaction submitted after expiresAt, or its blockhash has expired | Request a new transaction |
transaction_failed | 409 | Chain rejected the transaction | error: { code, message, programError? } |
transaction_altered | 400 | The submitted transaction’s message differs from the one issued | Re-sign the original bytes |
transaction_unsigned | 400 | A required signature is missing or invalid in the submitted transaction | Sign with every key in the envelope’s signers and submit again |
transaction_not_found | 404 | No transaction with this id was issued to you | Use the transactionId from the envelope |
proposal_not_found | 404 | GET /proposals/{id} for a proposal that was not sent to you | — |
feature_unavailable | 501 | The action does not exist on this market’s program, for example claim-fees and fee-recipient while markets have no resolution fees | See Contract versions |
resolution_blocked | 409 | Resolution to this outcome is temporarily blocked by a platform safety check | Contact Melee; void remains available |
rate_limited | 429 | Too many requests | Honour Retry-After |
idempotency_conflict | 409 | Same Idempotency-Key with a different body, or the first request with that key is still in progress | Different body: use a new key. Still in progress: retry the same request with the same key to receive its response |
rotation_in_progress | 409 | POST /resolvers/me/secrets/rotate while the previous secret is still in its overlap window | detail says until when the previous secret is valid; rotate again after that |
resolver_state_forbidden | 403 | The operation is not available in your resolver’s current state (for example market actions before activation, or reinstate while Active), or not for your kind of resolver (propose and reject are for disputable resolvers) | detail names the allowed states and your current one; see what each state may do |
internal_error | 500 | Unexpected error on our side; nothing you sent was wrong | traceId. Retry with the same Idempotency-Key, unless detail says retrying will not help; quote traceId when contacting Melee |
Creators, not you, see evaluation_failed, below_confidence_threshold and handshake_timeout when your
evaluate or accept did not succeed. Those never create a market.
Refused rules guidelines
invalid_config on POST /resolvers or PATCH /resolvers/me with an errors entry for rulesGuidelines
means the guidelines, not your keys or fees, caused the failure. Registration is all-or-nothing, so no
resolver was created and no credentials were issued; a patch leaves your record unchanged. Fix the text and
submit again.
{
"type": "https://docs.melee.markets/resolver-api/errors#invalid_config",
"title": "Registration failed validation",
"status": 422,
"code": "invalid_config",
"detail": "rulesGuidelines was rejected. Nothing was registered; fix the field and submit again.",
"errors": [
{
"field": "rulesGuidelines",
"reason": "contains_link",
"message": "Links are not allowed in rules guidelines. Remove \"https://stats.example.com/results\" and name the source in words instead."
}
]
}The rules that produce each reason are defined on the
registration page.
Partially confirmed resolve
A partially confirmed non-disputable resolve (proposal landed, resolve failed) leaves a standing proposal.
Calling resolve again with the same outcome completes it; void remains available; reject is available
to clear it.