Skip to Content
Uptimeify Docs

Error codes and known API pitfalls

This page documents real integration issues that have occurred in production or testing.

Schema

Error CodeCauseSolution / Bug
404 Website not foundSome website sub-endpoints previously accepted only the legacy numeric website ID, even though the docs showed websitePublicId.Fixed. GET /api/websites/:websitePublicId/check-history and GET /api/websites/:websitePublicId/uptime-stats now accept public IDs and still keep legacy-ID compatibility.
403 Forbidden on GET /api/organizations/:organizationPublicIdThe route previously interpreted the path parameter directly as a number. A UUID therefore failed during permission checks.Fixed. Organization detail and billing routes now resolve publicId correctly.
400 Bad Request with ZodError on customer-ips or customer-domainsQuery parameters like organizationId=, page=, or perPage= were sent as empty strings. Zod coerced them to 0, which then violated min constraints.Fixed for organizationId, page, and perPage. Optional still means: omit unused parameters instead of sending empty strings.

Monitor ownership error codes

Since the managed vs. self-service model, monitor write endpoints of all types (website, DNS, ICMP, SMTP, SSH, FTP, IMAP/POP, domain, DNSBL) can return these 403 codes in data.code:

CodeMeaning
managed_by_organizationA customer-scoped caller tried to edit/delete a managed monitor without the canEditManaged exception. Open a change request instead. Also for a managed status page and what hangs off it (settings, components, groups, domain, subscribers, incidents and maintenance on the page), for customer-bound users with any role (also readonly and editor) and customer-bound tokens; ask with Create Status Page Change Request instead.
selfServiceNotAllowedA customer-scoped caller tried to create a monitor but the customer's resolved allowSelfService is false.
selfServiceQuotaReachedCreating (or flipping to) a self_service monitor would exceed the customer's maxSelfServiceUrls: the quota counts all monitor types together.
managementTypeOrgOnlyA non-org-admin tried to change a monitor's managementType. Class flips are organization-admin-only, and since 04.09.2026 that is enforced against customer-scoped API tokens too: such a token is synthesized with an admin role but restricted scope, and the flip now requires unrestricted scope.
readonlyMayNotDeleteA caller with the readonly role tried to delete a monitor. Deleting is closed to that role on every ownership class, self_service included, and an API token issued by a read-only user inherits the restriction. Editing a self_service monitor stays permitted.
tooManyOpenRequests(429) The customer already has 10 open change requests.

Monitor quota error codes

An organization has a monitor quota. Creating a monitor while that quota is exhausted either fails, or, when the organization has automatic quota upgrading switched on, moves it to the next quota tier - and that tier has a higher monthly price, with the difference billed for the rest of the current period.

CodeMeaning
monitorQuotaReached(403) The organization is at its monitor quota and does NOT upgrade automatically. Free up a monitor or raise the quota.
monitorQuotaNoHigherTier(403) The organization is at its quota, upgrades automatically, and is already on the highest predefined tier. Contact support.
paidQuotaUpgradeNotAuthorized(403) The call would have triggered a PAID upgrade and did not authorize one. This can only happen on an agent (MCP) connection: a person in the dashboard sees the tier and its price, a model does not, so a billing effect starts opted out. The message names the tier and the monthly price the call would have bought. Send allowPaidQuotaUpgrade: true once a person has agreed to the higher bill, or free up a monitor first. Every other kind of caller, including an API token, is unaffected and never sees this code.

Customer package error codes

POST /api/customers and PATCH /api/customers/:customerPublicId resolve the package a customer is on. Both reject a package the organization does not have:

CodeMeaning
invalidPackageType(400) The packageId does not belong to this organization, or the legacy packageType matched neither a configured package key nor a package display name of this organization.

PATCH previously stored an unknown packageType verbatim and left packageId empty. Such a customer was attached to no package config at all, which left its data retention unresolvable. Send packageId, or a packageType that exists on the organization.

Customer deletion and user assignment error codes

CodeMeaning
invalidUserAction(400) DELETE /api/customers/:customerPublicId (query userAction) or POST /api/customers/bulk with action: "delete" (payload.userAction): the value is neither deactivate nor delete. Users assigned only to the deleted customer are always deactivated or deleted; there is no option to keep them. Nothing is deleted when this error is returned.
customerUserDeleteAdminOnly(403) DELETE /api/customers/:customerPublicId with userAction=delete or POST /api/customers/bulk with action: "delete" and payload.userAction: "delete", sent by an editor. Since 04.11.2026 editors may delete customers, but deleting user accounts stays with organization admins. Use the default deactivate. Nothing is deleted.
cannotDeleteOwnLastCustomer(409) An editor assigned to customers would delete the last of them with DELETE /api/customers/:customerPublicId or POST /api/customers/bulk (action: "delete"). The editor would end up without a customer and deactivate their own account. Ask an organization admin. The bulk request is rejected as a whole; no customer is deleted.
customerIdsReadonlyOnly(400) POST /api/users: a non-empty customerIds was sent with a role other than readonly. Only readonly users are bound to customers. Before 06.10.2026 the list was ignored silently and the user was created with organization-wide access.

Website check-interval error codes

checkInterval is capped by the monitor's type, because the two meanings differ: for actively scheduled monitors it is the polling rate and stays at 1-1440 minutes (24 hours), while for heartbeat monitors it is the expected ping interval and accepts 1-43200 minutes (30 days), a monthly cron job is a legitimate monitor.

CodeMeaning
checkIntervalTooLow(400) POST /api/websites: checkInterval is below the minimum the customer's package allows. The statusMessage names the minimum.
checkIntervalTooHigh(400) PATCH /api/websites/:id: checkInterval exceeds the ceiling for the monitor's type. The type is taken from monitoringType when the request sends it and from the stored monitor otherwise, so raising the interval past 1440 on a non-heartbeat monitor is rejected even when the request omits monitoringType.
invalidCheckInterval(400) PATCH /api/websites/:id (partial update without customerId, name and url): checkInterval is not an integer within 1 and the type's ceiling. The package minimum applies here too and answers checkIntervalTooLow.
invalidTimeout(400) PATCH /api/websites/:id (partial update): timeoutSeconds is not an integer between 1 and 60.
invalidCheckConfig(400) PATCH /api/websites/:id (partial update): a check field is outside its range, e.g. sslNoticeDays above 365 or minPageSize below 0. The six check fields, checkDomainExpiryEnabled, the SSL and domain-expiry thresholds and the page-size bounds are applied by a partial update; the package rules apply the same way as on a full update.
checkNotInPackage(403) POST /api/websites, PATCH /api/websites/:id and PATCH /api/websites/:id/check-config: an explicit true would switch on one of the six checks that the customer's package forbids. data.check names the field. A check that is already running (or was never set) may still be sent as true; an omitted field still takes its default from the package without an error. Before 22.10.2026 the check was silently stored as false.
checkRequiresValue(400) Same endpoints: checkKeywordEnabled: true without a non-empty searchTerm (data.field: searchTerm), or checkSizeEnabled: true with neither minPageSize nor maxPageSize (data.field: minPageSize), on a check that is not running yet. data.check names the check. A PATCH uses the value from the body, otherwise the stored one. A forbidden package check answers checkNotInPackage first. Before 22.10.2026 the check was silently stored as false.
invalidUrl(400) PATCH /api/websites/:id (partial update): url points at a private, loopback, link-local or otherwise non-public address. The same check that POST /api/websites applies. heartbeatToken is ignored on this path; the token is only ever generated server-side.

POST /api/websites reports the same ceiling as a validation issue on the checkInterval path rather than a data.code, because the type is known from the request body alone.

Website connect target (Ersatzziel) error codes

connectHost, connectPort and connectTlsInsecure connect the check to a different host than the one in url, while url, the Host header and TLS SNI stay unchanged - the semantics of curl --resolve. Both POST /api/websites and PATCH /api/websites/:id (partial update included) validate them the same way.

CodeMeaning
connectHostInvalid(400) connectHost failed to parse: it carries a protocol or a path, contains whitespace, has an unbracketed IPv6 address, or its port is not a number in 1-65535.
connectHostNotPublic(400) connectHost resolves to a private, loopback, link-local, or otherwise blocked address - the same SSRF guard applied to url.
connectTlsInsecureWithoutHost(400) connectTlsInsecure was sent as true while the resulting connectHost is empty. On PATCH, this also fires when a request clears connectHost (null) but still sends connectTlsInsecure: true.

Not available for playwright scenarios or heartbeat monitors: neither runs the HTTP/SSL check pipeline connectHost plugs into, so the fields are accepted on those monitors but have no effect.

Check mode error codes (SSH/SMTP/FTP/IMAP-POP monitors)

The credentialed monitor kinds (SSH, SMTP, FTP, IMAP/POP) support a checkMode field (protocol | tcp, default protocol). In tcp mode the monitor performs a bare TCP port-reachability check and no credentials are required or stored. Create and update endpoints for these four kinds can return these 400 codes in data.code:

CodeMeaning
portRequiredForTcpIMAP/POP create or update: checkMode is (or resolves to) tcp, but no port is set on the request or already stored on the monitor. Only IMAP/POP requires an explicit port for tcp mode. SSH, SMTP, and FTP fall back to their protocol default port.
invalidCheckModeUpdate (PATCH) endpoints only: checkMode was provided but is neither protocol nor tcp.

Incident error codes

Only manual (status-page) incidents can be deleted. DELETE /api/incidents/:id returns this data.code:

CodeMeaning
notManualIncident(403) The incident is monitor-generated. Only manual incidents created by an admin can be deleted; automatic incidents are worker-owned and are never deletable via the API.

Maintenance window error codes

POST /api/maintenance-windows/preview-occurrences (docs) can return this data.code:

CodeMeaning
invalidWindow(400) endTime is not after startTime.

Creating, updating and deleting a window (POST /api/maintenance-windows, PATCH /api/maintenance-windows/{id}, DELETE /api/maintenance-windows/{id}) can return these:

CodeMeaning
endTimeBeforeStartTime(400, create and update) endTime is not after startTime. The same condition the preview endpoint answers with invalidWindow; the two codes differ, so branch on both.
missingTargetId(400, create) The request names a target kind but no id for it. A window needs at least one monitor, customer, customer IP or customer domain to cover.
maintenanceWindowNotFound(404, update and delete) No window with that id is visible to this caller. Out-of-scope and non-existent are deliberately the same answer.
customerNotFound, customerIpNotFound, customerDomainNotFound(404, create) The named target exists in no organization this caller can see.
maintenanceWindowTargetMissing(500, update and delete) The stored window has lost the row it covered, which is a data inconsistency rather than a request error. Report it instead of retrying.

A repeated create call is safe: a window whose whole request body matches one that already exists is not created a second time, the existing window is returned and its subscribers are not announced to twice.

Organization Reports error codes

Endpoints under /api/organization/reports and /api/organization/report-runs can return these data.code values:

CodeMeaning
invalidReportScheduleA weekly report is missing weekday, or a monthly report is missing dayOfMonth (1-28).
invalidReportScopeReport scope ids are not owned by the organization, or threshold mode has no threshold set.
reportRunNotFoundThe requested report run does not exist for this organization.
reportRunNoPdfThe report run has no archived PDF (it was an email-only report or was skipped).
reportPdfNotFound(404) The run record has a PDF path, but the object could not be read from object storage.

Dependency status error codes

The public endpoints under /api/public/dependencies can return these data.code values:

CodeMeaning
providerNotFound(404) No active provider with that slug. Unknown and inactive are deliberately the same answer.
invalidIncidentPage(400) incidentPage is not an integer from 1 to 100000.

Report form error codes

The public endpoints under /api/public/im/report-form/:token, which back the report form page, can return these data.code values. A submission (POST) otherwise always answers 202 {"status":"received"}, also when it was discarded or the token is unknown.

CodeMeaning
reportFormNotFound(404, GET) No report form behind this link. Unknown token, a token of another source type and a deleted organization are deliberately the same answer.
invalidRequestBody(400, POST) A field breaks the form's rules, for example a text under 10 characters or an invalid email address.
unavailable(503) The form or the queue could not be reached. Send the report again later.

Data export error codes

Endpoints under /api/organization/data-export (see Request Data Export) can return these data.code values:

CodeMeaning
invalidExportRecipient(400) recipientEmails contains an address that is not a member of this organization. The rejected addresses are listed in data.unknown.
exportAlreadyRunning(409) An export of this organization is already queued or generating. The running export is in data.export.
exportCooldown(429) An export was requested within the cooldown window (data.cooldownHours, default 6).
exportNotReady(409) Download was requested while the export is queued, generating or failed. Current state in data.status.
exportExpired(410) The 7-day download window has closed and the file has been deleted.
missingExportId(400) The route was called without an export id.

Audit log export error codes

Export Audit Log can return this data.code value in addition to invalidRequestBody and invalidDateRange:

CodeMeaning
auditExportRangeTooLarge(400) The period is longer than 366 days or holds more than 100,000 entries. Split it into several exports.

Agent-auth error codes

Agent access tokens (wsma_, see Agent authentication) are hard-gated to a GET/HEAD-only allowlist by default. A token minted with a write scope (api.write.monitors, api.write.incidents) is gated per method-and-path instead, against a fixed positive list covering only those two domains today -- everything else, including billing, credentials and any path on the shared write denylist, stays unreachable regardless of scope. Either kind of token still cannot see or reach anything outside its own read allowlist.

CodeMeaning
agentTokenReadOnly(403) Returned for any write attempt while the platform-wide write kill-switch is off, regardless of the token's scope -- and, for reads too, when the path is outside the token's own read allowlist. data.reason names the rule that refused the call: agentTokenWriteDisabled, agentTokenReadOnly, agentTokenPathForbidden or agentTokenPathAmbiguous.
agentTokenScopeForbidden(403) The kill-switch is on, but this specific method and path are not in the token's write allowlist -- including a token that holds no write scope at all. Distinct from agentTokenReadOnly on purpose: this token may write, just not this -- a different write, or a different domain, can still succeed.

API token error codes

A customer-scoped API token (wsm_ with a customerId) is confined to its customer. Organization-wide paths have no customer dimension, so the token cannot reach them at all: everything under /api/organizations/**, /api/organization/** (except GET /api/organization), /api/users/**, /api/admin/**, /api/platform-admin/**, /api/escalation-config/**, /api/custom-pricing, /api/custom-fields/**, /api/im/**, /api/notifications/send-alert, writes to /api/package-configs/**, creating or deleting customers, and /api/customers/bulk. No API token, customer-scoped or not, can create further tokens.

CodeMeaning
customerScopedTokenForbidden(403) A customer-bound caller reached an organization-wide path or resource. Since 04.09.2026 this is raised not only for customer-scoped API tokens but for every customer-bound session as well: an editor with customer assignments and a platform admin in customer context creating a customer, or changing or deleting an organization-wide maintenance window (customerId: null). Use an organization-wide token, or an unrestricted user session, for organization settings, billing, users, reports and organization-wide windows.
apiTokenCannotMintTokens(403) POST /api/customer/tokens was called with an API token. Tokens are minted by a signed-in user, never by another token.
apiTokenScopeForbidden(403) The API token was created with scopes, and none of them covers this path and method (api.read.<area> for GET/HEAD, api.write.<area> otherwise), or the path belongs to no scope at all. Tokens without scopes are not affected. See Token Scopes. data.requiredScope names the missing scope (absent when the path belongs to no scope).
apiTokenPathAmbiguous(403) The request path contains an encoded slash, dot segment or double slash. The token guards refuse to normalize such paths.
csrfOriginRejected(403) A cookie-authenticated write came from a cross-site page: Sec-Fetch-Site: cross-site, or an Origin that matches neither the request host nor a trusted origin. API tokens are never affected; browser integrations must call from the app's own origin.

Claim flow error codes

The service_auth registration and claim ceremony (see Claim flow) can return these error / data.code values, in addition to the base agent-auth codes above:

CodeMeaning
service_auth_not_enabled(400) POST /agent/identity: the service_auth identity type is not enabled on this deployment.
invalid_claim_token(400 at POST /agent/identity/claim and POST /api/agent-claim/confirm, 404 at GET /api/agent-claim/context) The claim token, claim-attempt token, or user_code is unknown/expired/wrong-type, the signed-in user is not the bound email, or the confirming user's access cannot be resolved to a single organization/customer scope.
claimed_or_in_flight(409) POST /agent/identity/claim: the registration is already claimed.
claim_expired(400) POST /agent/identity/claim: the outer 24h claim window (from registration creation) has elapsed.
authorization_pending(400) POST /oauth2/token with the claim grant: the user has not confirmed yet; keep polling.
slow_down(400) POST /oauth2/token with the claim grant: polled faster than the returned interval (5s); back off.
expired_token(400) POST /oauth2/token with the claim grant: the claim token/registration expired, was revoked, or was already redeemed.

ID-JAG error codes

identity_assertion registrations (see Identity assertion (ID-JAG)) can additionally return:

CodeMeaning
issuer_not_enabled(400) POST /agent/identity: Uptimeify trusts no identity provider on this deployment, so identity_assertion is off.
login_required(401) POST /agent/identity: the ID-JAG's auth_time is older than max_age (3600 s, returned alongside); sign in again at the identity provider.
interaction_required(401) POST /agent/identity: the verified email belongs to an Uptimeify account and the agent is not approved yet; send the user to claim.verification_uri_complete and poll with claim_token.
invalid_grant(400) POST /oauth2/token with the jwt-bearer grant for an approved ID-JAG agent: the requested scope exceeds the approval (scope_exceeds_grant), the user's customer binding changed (binding_changed), the approving user no longer exists (no_human), or nothing is left after dropping write access for a global supporter (nothing_left). The reason is named in error_description.
invalid_request (err)(400) POST /agent/event/notify: wrong Content-Type, empty body, or the Security Event Token was not accepted. Which check failed is deliberately not said.

Connected apps (OAuth connections) error codes

GET /api/oauth/connections and DELETE /api/oauth/connections/:clientId (see Connected apps) can return these data.code values, in addition to the standard 401 unauthorized:

CodeMeaning
missingClientId(400) DELETE only: the :clientId path parameter is missing.
unknownOauthConnection(404) DELETE only: the caller has no OAuth connection for that client_id (already revoked, expired, or never connected).

These codes come from the consent screen every OAuth/MCP authorization now passes through (POST, on /api/oauth/consent). Like the step-up and account-deletion routes, it is session-only and not part of the public API surface, and the method and the path are written apart here for the same reason: a METHOD /api/... route-line in these pages is what publishes an endpoint to /openapi.json. They are listed because the codes are what the screen and any support enquiry go by. The scope catalogue itself is on Connected apps.

The checks run in the order below, so the first one that fails is the code you get. The last row is the exception: it comes from Better Auth, after every check on this list has passed.

CodeStatusMeaning
unauthorized401No active session. The endpoint resolves the session itself rather than sitting behind the shared middleware.
invalidConsentDecision400accept is absent or is not a real boolean. It is deliberately not defaulted to false: a malformed request must not refuse the authorization on the user's behalf.
missingOauthQuery400oauth_query is absent. The consent screen passes on the signed authorization request it was opened with; without it there is nothing to decide. Start the authorization again from the client.
emptyConsentSelection400Accept only: read areas were on offer and none of them was selected. Refuse the authorization instead of accepting an empty one. A client that requested no MCP scope at all sees no checkboxes and never hits this.
consentScopeEscalation400Accept only: the selection names a scope the client did not request, or one that is not a granular scope at all. A selection can only ever narrow what was asked for.
consentForwardRejected4xxThe authorization server rejected the request after the checks above passed, and the status is the one it returned. It carries a reason alongside the code: typically the signed request has expired or was altered. Retrying does not help; start the authorization again from the client.

Status page subscriber error codes

List, delete, and export endpoints for status page subscribers can return these data.code values, in addition to the standard 401 unauthorized and the two-tier statusPageNotFound behavior described on each page (a malformed or unknown :id is a code-less 400/404 from public-ID resolution; only an :id that resolves but fails the organization/customer-scope check carries data.code: statusPageNotFound):

CodeMeaning
invalidSubscriberId(400, delete only) :subscriberId does not parse as a positive integer.
subscriberNotFound(404, delete only) :subscriberId does not exist, or belongs to a different status page than :id.

Public IDs in DNS and DNSBL monitor routes

The following path endpoints support public IDs in docs and client integrations:

  • GET /api/customer-domains/:customerDomainPublicId
  • PATCH /api/customer-domains/:customerDomainPublicId
  • DELETE /api/customer-domains/:customerDomainPublicId
  • GET /api/customer-ips/:customerIpPublicId
  • PATCH /api/customer-ips/:customerIpPublicId
  • DELETE /api/customer-ips/:customerIpPublicId

Legacy numeric IDs are still accepted for backward compatibility, but public IDs are the recommended integration format.

Incident Management (IM) API error codes

The public Incident Management API (POST /api/im/events, GET/POST /api/im/incidents/**, GET /api/im/teams, GET/POST /api/im/schedules/**, GET /api/im/on-call) requires an organization-wide API token and can return these data.code values:

CodeMeaning
imAccessDenied(403) The caller is not allowed into Incident Management: no session/token, a customer-scoped API token, a customer (readonly) or globalsupporter login, or an org login without an IM-eligible role (admin, editor, responder).
imNotEnabled(403) Incident Management has not been activated for this organization.
payloadTooLarge(413, Events Ingest only) The request body exceeds 256 KB.
invalidJson(422, Events Ingest only) The request body is not valid JSON, or not a JSON object or array.
payloadTooDeep(422, Events Ingest only) The parsed JSON payload nests more than 20 levels deep.
imIncidentNotFound(404) The incident does not exist, or belongs to another organization.
imIncidentInvalidStatusTransition(422, Acknowledge / Update Incident Status) The requested status is not a valid target for this endpoint (resolved and merged are not, use Resolve Incident instead), the incident's current status cannot transition through this endpoint, or status equals the incident's current status.
imIncidentAlreadyClosed(422, Resolve Incident) The incident is already resolved or merged.
imIncidentStatusConflict(409, status/resolve endpoints) The incident's status changed concurrently between the read and the write. Safe to retry.
imTeamWriteDenied(403, Create Incident, Schedules, Schedule Overrides) The caller's role is not admin and they are not a team admin (im_team_member.imRole = 'admin') of the target team.
imShiftGiveAwayDenied(403, Schedule Overrides) A plain team member (not team admin, not organization admin) sent an override other than giving away their own shift, or tried to delete an override that is not their own give-away. data.reason names the failed condition: not_self, type, scope, tier, covered_by, window, coverer_not_in_team, already_given_away, no_duty, not_own_giveaway.
imShiftGiveAwayRateLimited(429, Schedule Overrides) A plain team member gave away more than 10 shifts within an hour. data.retryAfter is the wait in seconds.
imTeamMembershipRequired(403, Resolve Incident, merge, escalate-now, snooze, status change, severity, comment, assign, add-responder, bulk actions) The caller is an IM user but not a member of the incident's team (incident.teamId), and neither an organization admin nor a platform admin. Acknowledging stays open to every IM user. Bulk endpoints refuse the whole request and list the affected ids in deniedIncidentIds.
imTeamAdminRequired(403, add-responder with notify: true) Paging another responder requires a team admin (im_team_member.imRole = 'admin') of the incident's team or an organization admin; a plain team member may add a responder without notifying.
imUserNotEligible(400, team members, team invite of an existing account, schedule overrides) The target user is inactive or has no IM-eligible role (admin, editor, responder).
imSnoozeRangeInvalid(400, snooze) snoozedUntil is not in the future or more than 7 days ahead.
imTeamNotFound(404, Schedules create) teamId does not exist, or belongs to another organization.
imScheduleNotFound(404, Schedule Overrides) :id does not exist, or belongs to another organization.
invalidTeamId(422, Create Incident) teamId does not belong to your organization.
invalidCustomerId(422, Create Incident) customerId is given but does not belong to your organization.
imRoutingInvalidPolicyId(422, Create Incident) escalationPolicyId is given but does not belong to your organization.
userNotFound(404, Schedule Overrides add) userId does not belong to your organization.
organizationIdRequired(400, Activate, setup state) No organization could be determined for the request.
forbidden(403, Activate, setup state, organization settings) The caller is not an admin of the organization.
imUserSessionRequired(403, My On-Call Status, notification log) The endpoint describes a person and needs a user session; an organization-wide API token is refused.
monitoringAccessDenied(403, IM access check) The session has no organization.
imAuditLogAccessDenied(403, Audit Log) Only organization admins may read the audit log.
imChannelWriteDenied(403, Channels) The caller may not write this channel (org-wide channels need admin, team channels admin or team admin).
imOutboundWriteDenied(403, Outbound Integrations) The caller may not write outbound integrations.
imChannelNotFound(404, Channels) The channel does not exist, or belongs to another organization.
imEscalationTierNotFound(404, Team Tiers) The tier does not exist in this team.
imNotificationRuleNotFound(404, Notification Settings) The rule does not exist or is not yours.
imOutboundNotFound(404, Outbound Integrations) The outbound integration does not exist, or belongs to another organization.
imOutboundDeliveryNotFound(404, outbound retry) The delivery does not exist for this integration.
imOverrideNotFound(404, Schedule Overrides, Team Overrides) The override does not exist on this schedule or team.
imRoutingRuleNotFound(404, Routing Rules) The routing rule does not exist, or belongs to another organization.
imSourceNotFound(404, Alert Sources) The alert source does not exist, or belongs to another organization.
imStatuspageRuleNotFound(404, Status Page Rules) The status page rule does not exist, or belongs to another organization.
imTeamMemberNotFound(404, Team Members) The member does not exist in this team.
imChannelInactive(400, organization settings) fallbackChannelId points to a deactivated channel.
imFallbackChannelDeprecated(400, organization settings) fallbackChannel is no longer writable; set fallbackChannelId to a channel from Channels instead.
imNoTestPayloadAvailable(400, source test alert / test mapping) No payload was sent, none is cached for the source, and its type has no built-in sample.
imReportRangeRequired(400, Reports, Analytics) A valid from/to range is required (NIS-2 management report: or a quarter).
imReportRangeInvalid(400, Reports, Analytics) from/to are not valid dates, or from is not before to.
imReportRangeTooLarge(400, Reports, Analytics) The range is longer than 400 days (366 for the NIS-2 management report).
imSourceHasNoIngestToken(400, rotate-token) The source type has no inbound webhook, so there is no ingest token to rotate.
invalidPhoneNumber(400, Notification Settings) phoneNumber is not in E.164 format (e.g. +491701234567).
imChannelIsOrgFallback(409, Channels) The channel is the organization fallback channel and cannot be deactivated.
imChannelReferencesExist(409, Channels) The channel is still the organization fallback channel and cannot be deleted.
imTeamChannelReferencesExist(409, Teams delete) A channel of this team is still the organization fallback channel.
imTeamRoutingReferencesExist(409, Teams delete) A routing rule still sends alerts to this team.
imTeamSourceReferencesExist(409, Teams delete) An alert source still belongs to this team.
imTeamIncidentReferencesExist(409, Teams delete) Incidents still belong to this team; a team with incident history cannot be deleted.
imIncidentAssignmentExists(409, add-responder) The user already holds this role on the incident.
imNotificationRuleExists(409, Notification Settings) The same urgency/delay/channel rule already exists.
imSourceProtected(409, Alert Sources delete) The monitoring bridge source cannot be deleted.
imSourceReferencesExist(409, Alert Sources delete) Open alerts or incidents still reference the source.
imTeamMemberExists(409, Team Members, team invite) The user is already a member of this team.
imTierOrderConflict(409, Team Tiers create) Two tiers were created at the same moment. Safe to retry.
imAuthModeNotProvisionable(422, Alert Sources) HMAC or Bearer authentication was enabled in authMode directly; use the set-hmac-secret / rotate-bearer-token endpoints, which create the secret.
imIncidentAlreadyMerged(422, Merge Incidents) The incident is already merged.
imIncidentCannotMergeIntoSelf(422, Merge Incidents) Source and target are the same incident.
imIncidentTargetAlreadyMerged(422, Merge Incidents) The target incident is itself merged.
imMergeSuggestionNotFound(404, Dismiss Merge Suggestion) The incident has no open merge suggestion for this target (never suggested, or already dismissed).
imMergeTargetClosed(422, Merge Incidents) The target incident is resolved.
imIncidentClosed(422, Snooze) A resolved or merged incident cannot be snoozed.
imIncidentNotEscalating(422, Escalate Now) Escalate-now only works while the incident is triggered (not yet acknowledged).
imNoFurtherTier(422, Escalate Now) The incident is already at the last tier.
imInviteEmailNotEligible(422, team invite) No invitable account exists for this email in your organization.
imRoutingInvalidMatchReference(422, Routing Rules) match.source_ids or match.customer_ids names an id outside your organization; field and foreignIds say which.
imTierReorderMismatch(422, Team Tiers reorder) tierIds must be exactly the team's current set of tier ids.
invalidStatusPageId(422, Status Page Rules) statusPageId does not belong to your organization.
imPhoneCountryNotAllowed(400, Notification Settings) A verification code was requested for a number outside the EU/EEA, Switzerland and the UK, or for a premium-rate number.
imPhoneNotSet(422, Notification Settings) A verification code was requested without a stored phone number.
imPhoneVerifyCodeInvalid(422, Notification Settings) The verification code is wrong.
imPhoneVerifyCodeExpired(422, Notification Settings) The verification code is older than 10 minutes.
imPhoneVerifyTooManyAttempts(422, Notification Settings) The code was tried 5 times; request a new one.
imPhoneVerifyRateLimited(429, Notification Settings) More than 3 verification codes in an hour; retryAfterSeconds says when to retry.
imTestNotificationRateLimited(429, Notification Settings, setup test page) More than 5 test notifications or test pages in an hour; retryAfterSeconds says when to retry.
generic(500, IM write endpoints) The write did not return a row; the server log has the cause.
imBulkActionNotImplemented(501, Bulk Update) Changing an incident's team in bulk is not implemented.
imPhoneVerifySendFailed(502, Notification Settings) The SMS provider rejected the verification message; error carries its reason.
unavailable(503, Events Ingest, source test alert) The alert could not be queued. Retry with backoff.

GET /api/im/incidents, Create Incident, the status/resolve endpoints, Schedules create, and Schedule Overrides add can also return the generic 400 invalidRequestBody for malformed input (e.g. an unknown status filter value, a non-integer :id, a missing/malformed rotation layer). POST /api/im/events can additionally return 429 Too Many Requests (600 requests/minute per organization, with a retryAfter field but no data.code), or 503 with data.code: unavailable if the event could not be queued, safe to retry.

NIS-2 report case error codes

NIS-2 Settings and Report Cases are session-only and can return these data.code values:

CodeMeaning
nis2AdminRequired(403) Only organization admins can change the NIS-2 settings.
nis2InvalidOfficer(400) A reporting officer is not a user of your organization with the role admin, editor or responder.
nis2NotEnabled(403) NIS-2 report cases are not switched on for your organization.
nis2OfficerRequired(403) The caller is an API token, or a user who is neither organization admin nor reporting officer.
reportCaseAlreadySubmitted(409) After a submission the case can no longer be decided not_reportable.
reportCaseAwareAtReasonRequired(400) Moving awareAt later requires a reason.
reportCaseCannotClose(409) A case closes only after the final report or when decided not_reportable.
reportCaseClosed(409) The case is closed and accepts no more changes.
reportCaseCriteriaOpen(409) Every criterion must be confirmed or rejected before the decision.
reportCaseDraftInvalid(400) text and draftToken of a submission do not belong together: other text, case or stage, or the token is older than 90 days. Fetch GET .../draft again and send exactly its text with its draftToken.
reportCaseIncidentAlreadyLinked(409) The incident is already linked to this case.
reportCaseIncidentNotLinked(404) The incident is not linked to this case.
reportCaseInvalidTransition(409) The stage does not fit the case's status, e.g. final before notification, or a second early_warning.
reportCaseNotFound(404) The report case does not exist, or belongs to another organization.
reportCaseNotReportable(409) Submissions are only possible for cases decided reportable.
reportCaseReasonRequired(400) not_reportable requires a reason.
reportCaseSubmittedInFuture(400) submittedAt lies in the future.
reportCaseTestIncident(400) Test incidents cannot be linked to a report case.

Postmortem and follow-up error codes

Postmortems and follow-up can return these data.code values:

CodeMeaning
causeArchived(409) The cause is archived and cannot be newly chosen. A cause already set on the postmortem stays valid.
causeNameTaken(409) A cause with this name (case-insensitive) already exists in your organization.
causeNotFound(404) The cause does not exist or belongs to another organization.
imServiceNotFound(404) The service does not exist or belongs to another organization.
imServiceNameTaken(409) A service with this name (case-insensitive) already exists in your organization.
imServiceMonitorNotFound(404) A monitor in monitors does not exist or belongs to another organization; data.monitors lists them.
imServiceWriteDenied(403) Only an organization admin may create, update or delete services.
postmortemActionNotFound(404) The action does not exist or belongs to another postmortem.
postmortemActionOwnerInvalid(400) ownerUserId is not a user of your organization.
postmortemCauseRequired(400) Completing needs a causeId.
postmortemCompleted(409) The postmortem is completed. Content changes need POST .../reopen first; actions stay editable.
postmortemIncidentNotResolved(409) The incident is not resolved (or was merged into another one).
postmortemIncomplete(400) Completing needs summary and rootCause.
postmortemNotFound(404) There is no postmortem for this incident yet, or it belongs to another organization.
postmortemOrphaned(409) The incident of this postmortem was deleted. The postmortem stays readable but cannot be reopened.
quarterlyReviewExists(409) This quarter is already signed off. A sign-off cannot be changed.
quarterlyReviewNotDue(409) The quarter has not ended yet in your organization's time zone.

User management error codes

PATCH /api/users/:id (docs) and DELETE /api/users/:id (docs) protect the organization against locking itself out:

CodeMeaning
userSelfChangeForbidden(400, update) You tried to change your own role or set your own account to isActive: false. Ask another organization admin.
lastAdminProtected(400, update and delete) The target is the last active organization admin; it cannot be demoted, deactivated or deleted. Promote another user first.
globalUserProtected(403, update and delete) The target carries a platform flag (isGlobalAdmin or isGlobalSupporter) and may only be changed by a platform admin.

Tag error codes

POST /api/tags records the human who created a tag in created_by, a column that is NOT NULL and carries no foreign key. A call arriving over an agent session (an MCP connection, create_tag) is therefore refused rather than given a substitute value, because writing anything else there would break the "creator may edit" branch of the permission check silently and permanently:

CodeMeaning
authorizingUserUnresolved(403, create) The human who authorized this agent session can no longer be resolved, so there is no user id to record as the tag's creator. The tag is not created. A tag always records the authorizing human, never the agent. Re-authorize the connection, or create the tag with a session that belongs to a person.

The rest of the tag surface (POST /api/tags, PATCH /api/tags/{id}, DELETE /api/tags/{id}, and attaching or detaching one with POST /api/monitor-tags and DELETE /api/monitor-tags) can return these:

CodeMeaning
invalidTagColor(400, create and update) The colour is not one of the palette values. The palette is a fixed set, not a free hex field.
tagCustomerRequired(400, create) A customer-scoped caller with more than one customer in scope did not say which of them the tag belongs to. A caller with exactly one customer in scope gets that one by default.
invalidCustomer(400, create and update) The named customer belongs to another organization.
tagNotFound(404) No tag with that id is visible to this caller.
invalidMonitorType(400, attach and detach) monitorType is not one of the supported monitor families.
monitorNotFound(404, attach and detach) No monitor of that type and id is visible to this caller.
tagMonitorOrgMismatch(400, attach) The tag and the monitor belong to different organizations.
tagLimitReached(422, attach) The monitor already carries the maximum of five tags.

Attaching a tag is idempotent: a tag already on the monitor is not attached a second time and the call still succeeds.

Change request error codes

POST /api/monitors/:type/:id/change-requests and the legacy website-only route under /api/websites/:id/change-requests record the requesting human in requested_by, a NOT NULL column with a foreign key to user. A call over an agent session is refused rather than given a substitute value:

CodeMeaning
authorizingUserUnresolved(403, create) The human who authorized this agent session can no longer be resolved. No request is created. Resolving a request (PATCH /api/change-requests/:id) is not affected: resolved_by is nullable and simply stays empty.

Notification channel error codes

CodeMeaning
configRequiredForTypeChange(400, Update Notification Channel) type changed but the request carries no config. A type change rebuilds the configuration from the request; the previous type's fields are never carried over, so send the full config for the new type.
notificationChannelRecipientExists(409, Create Notification Channel) an ACTIVE channel of the same type in the same scope already delivers to the same recipient; data.channelId names it. Repeating a create call whose response never arrived lands here instead of creating a second channel that would deliver every alert twice. Inactive channels never block, and the name is not part of the check.
invalidRequestBody(400, Create and Update Notification Channel) a target URL in config is unparseable, uses a scheme other than http/https, or points at a private, loopback or link-local address, at localhost, at a reserved private-use name (.local, .internal, .home.arpa) or at a single-label host. Every top-level config string starting with http:// or https:// is treated as a target URL; message-content fields (bodyTemplate, webhookBodyTemplate, headers) are exempt. No DNS is resolved, the delivery-time guard covers a name that only later resolves privately.
sourceChannelIdRequired(400, create) The request asks for a website-specific override but names no sourceChannelId. An override always derives from an existing organization-level channel.
invalidSourceChannelId(400, create) sourceChannelId is not a usable id for a website override.
sourceChannelNotFound(404, create) The named source channel is visible to no organization this caller can see.
websiteChannelOverrideExists(409, create) This website already has an override for that source channel. Update the existing override instead of creating a second one.
channelIdRequired, invalidChannelId(400, update and delete) The path carries no channel id, or one that is not a usable id.
channelNotFound(404, update and delete) No channel with that id is visible to this caller.

A Matrix channel is a special case worth knowing about: its homeserverUrl is checked for shape when the channel is saved and resolved again at delivery time. A homeserver that only resolves to a private or reserved address is refused at delivery, and the refusal is recorded against that alert rather than raised as an error on this endpoint.

Custom domain error codes

The verify and activate endpoints of white-label domains and status page domains claim a hostname for your organization. Since 04.09.2026 a hostname is unique only among claimed entries (verified/active); a pending entry never blocks anyone and expires after 7 days.

CodeMeaning
domainAlreadyClaimed(409) Another organization has already verified or activated this hostname. The response never names that organization.
hostnameReserved(400, add domain) The hostname is one of the platform's own hosts, a subdomain of them, or anything under uptimeify.io.

Deprecated fields (renames, 20.10.2026)

A field that breaks the naming rules gets a successor next to it. Both are delivered until the removal date; the old field is marked deprecated in the OpenAPI spec and names its successor in x-replaced-by. Request bodies accept both spellings until then. A path that nests too deep gets a flat successor the same way; the old operation is marked deprecated with x-replaced-by and keeps working until the removal date. Switch to the successor now.

Old fieldSuccessorWhereRemoved on
duration (text, e.g. 1h 5m 3s)durationMs (integer, milliseconds)incident rows of every monitor's incident-history and details2027-01-18
started_atstartedAtrows of the incident list, with and without includeTotal2027-01-18
total (SMS sum of the month)smsTotalCurrentMonthGET /api/customers/sms-usage; with ?envelope=items, total is the number of customers2027-01-18
path POST /api/im/teams/:id/tiers/:tierId/schedulespath POST /api/im/tiers/:tierId/schedulessame body and response; the team comes from the tier2027-01-18
path POST /api/organizations/:id/package-configs/:packageType/apply-report-defaultpath POST /api/package-configs/:packageType/apply-report-defaultsame response; the organization comes from the session2027-01-18
resolved_atresolvedAtrows of the incident list, with and without includeTotal2027-01-18
last_notified_atlastNotifiedAtrows of the incident list, with and without includeTotal2027-01-18
error_messageerrorMessagerows of the incident list, with and without includeTotal2027-01-18
status_codestatusCoderows of the incident list, with and without includeTotal2027-01-18
response_time_msresponseTimeMsrows of the incident list, with and without includeTotal2027-01-18
errorerrorMessageorganization data export entries (list, single export, new request)2027-01-18
recurrencePattern.intervalrecurrencePattern.intervalCount (repeat every N units of frequency)maintenance windows: every response and the create, update and occurrence preview bodies. Sending both with different values answers 400 invalidRequestBody2027-01-18
match.source_idsmatch.sourceIdsincident management routing rules (responses and request bodies)2027-01-18
match.customer_idsmatch.customerIdsincident management routing rules (responses and request bodies)2027-01-18
match.monitor_idsmatch.monitorIdsincident management routing rules (responses and request bodies)2027-01-18
match.field_matchesmatch.fieldMatchesincident management routing rules (responses and request bodies)2027-01-18
filters.event_kindsfilters.eventKindsincident management outbound integrations (responses and request bodies)2027-01-18
authMode.url_tokenauthMode.urlTokenincident management alert sources (responses and request bodies)2027-01-18
errorerrorMessageincident management notification log entries, test notification results and the mapping test of an alert source2027-01-18
themeNeutralthemeSecondary (the name the response already uses)request body of PATCH /api/organization/whitelabel/branding; when both are sent, themeSecondary wins2027-02-01

404 for out-of-scope resources

Since 04.09.2026 every resource endpoint answers 404 with its usual not-found code (websiteNotFound, monitorNotFound, customerNotFound, customerDomainNotFound, customerIpNotFound, statusPageNotFound) both when the resource does not exist and when it exists but is not within your organization or customer scope. A 403 is reserved for role-based denials (wrong role, customer-scoped token on an organization path). Tests that asserted 403 for "belongs to another customer" need updating.

Since 20.10.2026 the remaining customer paths follow the same rule: GET, PATCH and DELETE /api/customers/:id, GET /api/customers/:id/users, POST /api/customers/:id/ips, GET and PATCH /api/customer-ips/:id and GET and PATCH /api/customer-domains/:id. Each of them answered 403 forbidden for a customer outside your scope until then, and now answers 404 with its usual not-found code (customerNotFound, ipNotFound, domainNotFound). Global supporters can now read GET /api/customer-ips/:id, like every other monitor detail.

Rate limit and size error codes

CodeMeaning
imIngestRateLimited(429, on an alert source's webhook URL) More than 300 requests per minute for one alert source. data.retryAfter carries the seconds to wait.
imIngestByteBudgetExceeded(429, on an alert source's webhook URL) The organization sent more than 50 MiB of ingest bodies within one hour. data.retryAfter carries the seconds to wait.
imOutboundRetryRateLimited(429, POST /api/im/outbound/:id/retry) More than 10 manual retries per minute for one integration.
invalidDateRange(400, every check-history, alert-history and incident-history endpoint, and the audit log export) from or to is not a parseable date, or from is after to. Previously such values were silently ignored.
invalidRequestBody(400, every check-history, alert-history and incident-history endpoint) A query parameter is invalid: page/limit not a positive integer, format not json/csv, download not 0/1, an unknown status/type, or minMs/maxMs not a non-negative number. Previously such values were silently replaced (page 1, JSON, no filter).
noLocationsConfigured(400, POST /api/websites/:id/trigger-check) The website has no monitoring location it could run on.
invalidScreenshotId(400, screenshot download) The screenshot id is not a UUID.
invalidHostname(400, TCP/SSH/FTP monitor create and update) The hostname is not a public target. This used to surface as a 500.

POST /api/organizations/:id/vat-id/validate is limited to 10 checks per hour and organization (429 with data.retryAfter). POST /api/im/sources/:id/test-alert now applies the same body limits as the ingest URL (payloadTooLarge, invalidJson, payloadTooDeep).

Webhook and SMTP target error codes

CodeMeaning
webhookHostHeaderForbidden(400, escalation config and IM channel config) A custom Host header is not accepted for webhooks; the header is always set from the URL.
smtpHostNotPublic(400, PATCH /api/organization/smtp) The SMTP host resolves to a private, loopback, link-local, CGNAT or otherwise non-public address. The same check runs again at send time; a host that stops being public falls back to the platform mail provider.

Sender domain error codes

All on /api/organization/sender-domain and /api/organization/sender-domain/verify (Sender Domain).

CodeMeaning
senderDomainNotEnabled(403) Sender domains are an Enterprise feature and not enabled for this organization.
senderDomainNotConfigured(404, GET, verify, DELETE) No sender domain is set.
senderDomainReserved(400, PUT) An Uptimeify domain or one of its subdomains cannot be a sender domain.
senderDomainTaken(409, PUT) Another organization uses the domain, or it is already registered with the mail provider.
senderDomainProviderError(502) The mail provider did not accept the request. Nothing was changed; try again later.
senderDomainUnavailable(503) Sender domains are temporarily unavailable.

Organization suspended or deleted

A gate ahead of the account-state gate below locks every /api/* call, a user session, a wsm_ API token, or a wsma_ agent access token alike, to the caller's organization status. Platform admins and supporters are exempt, the same way they are everywhere else.

A suspended organization gets 423 Organization suspended with no data.code, except for a narrow allowlist that stays reachable so it can pay its way back: reading the organization, updating its quota tier, the data export endpoints above, the tenant lookup, and the Mollie mandate return/reconcile and billing-discount routes. Every other route is blocked.

A deleted organization does not get that allowlist, and it also loses two routes the suspended case keeps: signing out (POST to /api/auth/sign-out) and both session bootstrap calls (GET on /api/auth/get-session and /api/_internal/auth/get-session) answer 423 Organization deleted with data.code organizationSuspended as well, deliberately, because signing out deletes the session row from Redis and that row is evidence for the deletion audit. Before 15.09.2026 a deleted organization's session, API token and agent token reached every route unchanged, the same gap this closes. "Deleted" here means status = 'deleted' OR the permanent deletion_completed_at marker is set. What decides this is whether the deletion has actually completed, not what status the organization currently displays. Two more surfaces follow the same rule: /mcp refuses a deleted organization's API tokens and OAuth connections with 423 before it builds a server, and no password reset e-mail is sent, the endpoint answers exactly as it does for an unknown address. A cancelled organization inside its grace period passes this gate unaffected only as long as its deletion has not actually completed. This gate takes effect within a few seconds rather than instantly, because the account state behind it is cached briefly.

Account state on the auth endpoints

Better Auth's own routes (/api/auth/**, e.g. change-password, update-user, two-factor/*, mcp/token refresh) refuse a deactivated account or a suspended organization the same way the API does. Sign-in, sign-out, password reset, e-mail verification and get-session stay reachable. A deleted organization is narrower still: only sign-in, sign-up, password reset and e-mail verification stay reachable, sign-out and get-session answer 423 as described above, and a fresh sign-in fails anyway once credentials are checked, because session creation itself refuses.

CodeMeaning
accountDeactivated(403) The signed-in user is deactivated.
organizationSuspended(423) The user's organization is suspended or deleted. A cancelled organization inside its grace period is not affected, unless its deletion has already completed.

MFA error codes

These error codes are specific to two-step verification (MFA) and can be returned by otherwise unrelated endpoints once the underlying gate applies:

CodeStatusMeaning
mfa_enrollment_required403Returned by any gated /api/* call when the caller (a platform admin/supporter when MFA_ENFORCE_PLATFORM_ADMINS is on, or a member of an organization whose matching per-role switch requireMfaAdmins, requireMfaEditors or requireMfaReadonly is on) has not enabled two-step verification yet. Set up two-step verification, then retry the request.
mfa_step_up_required403Returned only by API token mutations (POST, PATCH and DELETE on /api/organization/tokens, and POST and DELETE on /api/customer/tokens; customer-scoped tokens cannot be updated) when the caller has not confirmed in the last 5 minutes: with a code from the authenticator app (data.method: "totp"), or, for an account without two-step verification, with the current password (data.method: "password", since 17.11.2026). Confirm in the dashboard dialog, then retry within the 5-minute window. Accounts that sign in through SSO only and have no password never see this code. Other session-only actions answer the same way, see the 17.11.2026 section at the end of this page.
mfa_step_up_locked429Returned by the internal, session-only step-up endpoint (POST, /api/account/mfa/step-up, not part of the public API surface) after 5 wrong codes from the same account. Locked for 15 minutes (data.retryAfterSeconds); wait and re-verify with your authenticator once it elapses.
nonUserSessionForbidden403Returned by POST /api/users/:id/mfa/reset for any API token or agent access token caller, by POST /api/users with role: "admin" and PATCH /api/users/:id changing role to admin for those callers (since 17.11.2026), and by PATCH /api/organization(s) when the request body includes requireMfaAdmins, requireMfaEditors, requireMfaReadonly, requireMfaCustomers or quotaAutoUpgradeEnabled and the caller is an API token or agent access token (switching on automatic upgrades consents to future paid upgrades). Both MFA-administration actions require a real, logged-in user session, an organization-scoped API token with admin-level access is not enough.

These codes are data.code values on the JSON error body, alongside the listed HTTP status.

Plan change error codes

CodeStatusMeaning
quotaChangeImmediateNotSupported400Returned by PATCH /api/organization(s) when a reduction is sent with quotaChangeEffective: "immediately" for an organization with yearly billing. Yearly plans are paid in advance; send the reduction without the field (or with "period_end") to schedule it for the end of the paid term.
quotaChangePeriodEndNotYetAvailable400Returned by PATCH /api/organization(s) when a reduction is sent with quotaChangeEffective: "period_end" for an organization with monthly billing before 1 January 2027. Until then (terms version 1.0) a reduction takes effect immediately with a pro-rata credit; send it without the field (or with "immediately"). Scheduling for the end of the month is available from 1 January 2027.

Account deletion error codes

These codes come from the in-app account deletion (GET, POST and DELETE, on /api/account/deletion-request). Like the step-up endpoint above, those routes are session-only and not part of the public API surface, and the method and the path are written apart here for the same reason: a METHOD /api/... route-line in these pages is what publishes an endpoint to /openapi.json, they are listed here because the codes are what the app and any support enquiry go by.

A deletion is requested, not performed on the spot: the request sets a deadline 30 days out and can be withdrawn until then. The organization's administrators are notified when it is requested and when it is withdrawn, because they are the people who can backfill an on-call rotation the departure would leave open.

CodeStatusMeaning
accountDeletionSoleOwner409The caller is the last active administrator (role = 'admin') of their organization. Deleting that user would leave an organization with no way in, with monitors and billing still running, so this case leads to the organization cancellation instead. data.organizationId names the organization. Appoint a second administrator and the same request succeeds.
accountDeletionNotRequested404The DELETE on /api/account/deletion-request found no standing request to withdraw. Either it was never made, or it has already been carried out.
accountDeletionUserNotFound404The account does not exist in the caller's organization.
accountDeletionNotRecorded409The request could not be recorded because it was withdrawn concurrently in another session while it was being written. Safe to retry.

VAT ID validation error codes

POST /api/organizations/:organizationPublicId/vat-id/validate (see Validate VAT ID) can return these data.code values, in addition to the standard 401 unauthorized, 403 forbidden and 404 organizationNotFound:

CodeStatusMeaning
vatIdMissing422The organization has no vatId stored. Set one first with Update Organization.
vatIdChangedDuringValidation409vatId or countryCode was edited concurrently while the EU VIES lookup was in flight. The in-flight verdict is discarded rather than written to data nobody actually checked. Safe to retry.

Update Billing Details: required body

Endpoint:

  • PATCH /api/organizations/:organizationPublicId/billing

Currently supported request body:

{
  "billingEmail": "billing@deinkunde.com"
}

This endpoint currently accepts only billingEmail.

More error codes

These data.code values come from endpoints a customer can reach. Endpoints are named as plain text (method and path, :id stands for the public ID or numeric ID). Branch on data.code, never on the message text.

Billing and organization

CodeMeaning
billingAlreadyActive(400, POST /api/organizations/:id/mollie/subscription) The organization already has active billing. Cancel the existing billing first or wait for the next billing cycle.
billingAlreadyEnabled(400, POST /api/organizations/:id/mollie/trial) Billing is already enabled for this organization; no trial is started.
concurrentWrite(409, POST /api/organizations/:id/mollie/subscription) A concurrent billing change was detected. Retry the request.
mandateRequired(400, POST /api/organizations/:id/mollie/subscription) No SEPA mandate exists yet. Set up the payment mandate first, then create the subscription.
paymentMethodNotRequired(400, POST /api/organizations/:id/mollie/trial and POST /api/organizations/:id/mollie/mandate) All packages are priced at 0.00 through custom pricing, so no payment method is needed.
noActiveSubscription(403 when creating or activating a monitor of any type: POST or PATCH on /api/websites, /api/dns-monitors, /api/icmp-monitors, /api/tcp-monitors, /api/smtp-monitors, /api/ssh-monitors, /api/ftp-monitors, /api/imap-pop-monitors, /api/customer-domains, /api/customer-ips and POST /api/customers/:id/domains and /ips. Organizations on invoice billing are not affected; 400 on DELETE /api/organizations/:id/mollie/subscription and POST /api/organizations/:id/mollie/cancel) The organization has no active subscription. Reactivate billing before creating or activating monitors. This also applies after monitoring ended (trial expired or cancelled) while the free status pages keep running, until a payment method is stored again. The same 403 applies to organizations that use status pages only (status pages module active, no monitoring package booked): book monitoring first. Organizations on invoice billing are not affected.
subscriptionNotRequired(400, POST /api/organizations/:id/mollie/cancel) This organization does not need a paid subscription, so there is nothing to cancel.
noActiveTrial(400, POST /api/organizations/:id/mollie/trial/skip and POST /api/organizations/:id/mollie/trial/cancel) No active trial was found for this organization.
noMollieCustomer(400, POST /api/organizations/:id/mollie/trial/reconcile) No Mollie customer is configured for this organization, so there is nothing to reconcile.
trialAlreadyActive(400, POST /api/organizations/:id/mollie/trial) A trial is already running.
trialForfeited(403, POST /api/organizations/:id/mollie/trial) The organization was cancelled and has forfeited its trial, or its monitoring has ended (trial expired, cancelled, unpaid invoice) and it runs on as a status-pages-only organization; no new trial checkout is created. Monitoring then comes back only as a paid plan through a payment method.
trialNotAvailableForQuota(400, POST /api/organizations/:id/mollie/trial) The trial is only available for the 25 websites quota.
trialSkipNotSupported(400, POST /api/organizations/:id/mollie/trial/skip) Skipping the trial is only supported for monthly billing.
invalidPricingData(500, POST /api/websites, PATCH /api/websites/:id, GET /api/organizations/:id/trial-status, POST /api/organizations/:id/mollie/cancel) The monthly total could not be calculated. Server side problem; report it to support.
discountAlreadyApplied(409, POST /api/organizations/:id/billing/discount) A discount code is already applied to this organization.
invalidDiscountCode(422, POST /api/organizations/:id/billing/discount) The discount code is invalid or expired.
tooManyDiscountAttempts(429, POST /api/organizations/:id/billing/discount) Too many discount code attempts. Wait before trying again.
discountRateLimitUnavailable(503, POST /api/organizations/:id/billing/discount) Discount code validation is temporarily unavailable. Retry shortly.
discountNotFound(404, DELETE /api/organizations/:id/billing/discount) No discount code is applied.
missingInvoiceId(400, GET /api/organizations/:id/invoices/:invoiceId/pdf) The invoice ID is missing.
invoiceNotFound(404, GET /api/organizations/:id/invoices/:invoiceId/pdf) The invoice does not exist for this organization.
invoiceProviderFailed(502, GET /api/organizations/:id/invoices/:invoiceId/pdf) The accounting provider could not deliver the invoice PDF (provider error or unreachable). This is not a problem with your session or permissions; retry later.
invalidQuotaSelection(400, PATCH /api/organization/quota) The quota selection in the body is invalid; data.issues lists the validation problems.
mfaRequiredForActor(400, PATCH /api/organizations/:id) Changing the organization's two step verification policy requires two step verification on your own account first.
smsCapRaiseForbidden(403, PATCH /api/organization, PATCH /api/organizations/:id) An organization admin sets smsOverageSafetyCapCentsMonthly freely from 0 up to smsOverageSafetyCapMaxCentsMonthly, the upper bound a platform admin sets per organization (raise and lower). Without an upper bound, the admin may only lower the cap (any value while none is set). Removing it (null) always stays with platform admins. data.maxCents is the effective upper bound: the upper bound if set, otherwise the stored cap (null when neither is set).

Customers, packages and customer IPs

CodeMeaning
customerCreationFailed(500, POST /api/customers) The customer could not be created.
domainCreationFailed(500, POST /api/customers/:id/domains) The customer domain could not be created.
ipCreationFailed(500, POST /api/customers/:id/ips) The customer IP could not be created.
invalidIpAddress(400, POST /api/customers/:id/ips) The address is not a valid IPv4 or IPv6 address, or (since 11.11.2026) it lies in a private, loopback, link-local or documentation range (for example 10.0.0.0/8, 192.168.0.0/16, 127.0.0.0/8, 203.0.113.0/24), which no blocklist ever lists.
ipNotFound(404, GET and PATCH /api/customer-ips/:id, GET /api/customer-ips/:id/check-history) The customer IP does not exist or is out of scope.
customerIpActivationInProgress(429, PATCH /api/customer-ips/:id) Another customer IP activation is already running. Retry.
lockUnavailable(503, PATCH /api/customer-ips/:id) The activation lock could not be acquired. Retry shortly.
packageNotFound(404, DELETE /api/organizations/:id/package-configs, DELETE /api/organizations/:id/package-configs/:packageType, GET /api/organizations/:id/package-configs/:packageType/stats) The package does not exist.
packageInUse(409, DELETE /api/organizations/:id/package-configs and DELETE /api/organizations/:id/package-configs/:packageType) The package is still assigned to customers. Move those customers first.
packageConfigConflict(409, DELETE /api/organizations/:id/package-configs/:packageType) The package configuration changed concurrently. Retry.

Monitors

CodeMeaning
checkCooldown(429, the trigger check endpoints of all monitor families: websites, dns-monitors, icmp-monitors, smtp-monitors, ssh-monitors, tcp-monitors, ftp-monitors, imap-pop-monitors) A check for this monitor was triggered moments ago. data.retryAfterMs says how long to wait, data.cooldownMs is the full cooldown.
noLocationsAvailable(503, trigger check of all monitor families) No monitoring location is active right now. Retry later.
noEligibleLocations(400, trigger check of all monitor families) No monitoring location matches the monitor's allowed countries. Widen the allowed countries.
noEligibleLocationSelected(503, trigger check of all monitor families except DNS) No eligible location could be selected at this moment. Retry later.
heartbeatChecksNotSupported(400, POST /api/websites/:id/trigger-check) Heartbeat monitors are pinged by you, they cannot be checked manually.
urlRequired(400, POST /api/websites) url is missing; for DNS monitors the hostname is missing. Only heartbeat monitors may omit it.
heartbeatMonitorRequired(400, POST /api/websites/:id/heartbeat-token/rotate) Only heartbeat monitors have a token to rotate.
heartbeatTokenAlreadyExists(409, POST /api/websites) The heartbeat token is already used by another monitor. Choose another token or omit it.
expectedStateNotSupported(400, POST /api/websites and PATCH /api/websites/:id, partial and full update) expectedState: "down" was sent for a monitor that is not a heartbeat monitor. Only heartbeat monitors can be inverted; every other website type accepts only up. TCP monitors have their own expectedState and never answer this code.
websiteCreationInProgress(429, POST /api/websites) Another website creation for this organization is running. Retry. The Retry-After header and data.retryAfter give the seconds the lock is still held (at most 15).
monitorActivationInProgress(429, creating or activating monitors of all families, customer domains and customer IPs) Another monitor activation is running and holds the quota lock. Retry. The Retry-After header and data.retryAfter give the seconds the lock is still held (at most 15).
playwrightScriptRequired(400, PATCH /api/websites/:id) playwrightScript is required when monitoringType is playwright.
customerWrongOrganization(400, PATCH on websites and on DNS, ICMP, SMTP, SSH, TCP, FTP and IMAP/POP monitors) The target customer belongs to a different organization than the monitor.
invalidManagementType(400, PATCH on all monitor families) managementType is neither managed nor self_service.
ftpConfigRequired(400, POST /api/ftp-monitors and PATCH /api/ftp-monitors/:id) ftpConfig.user and ftpConfig.password are required.
imapPopConfigRequired(400, POST /api/imap-pop-monitors and PATCH /api/imap-pop-monitors/:id) imapPopConfig.user and imapPopConfig.password are required.
smtpConfigRequired(400, POST /api/smtp-monitors and PATCH /api/smtp-monitors/:id) smtpConfig.auth.user and smtpConfig.auth.pass are required.
sshConfigRequired(400, POST /api/ssh-monitors and PATCH /api/ssh-monitors/:id) sshConfig.username and either sshConfig.password or sshConfig.privateKey are required.
invalidIcmpConfig(400, PATCH /api/icmp-monitors/:id) icmpConfig is invalid; statusMessage names the first problem.
invalidStatusFilter(400, list endpoints GET /api/websites, the list endpoints of all protocol monitor families, GET /api/customer-ips, GET /api/customer-domains) The status filter has an unknown value.
invalidSortBy(400, GET /api/websites and the list endpoints of all protocol monitor families) sortBy names an unknown column.
invalidMonitoringType(400, GET /api/websites) monitoringType or excludeMonitoringType has an unknown value.
invalidHttpMethod(400, GET /api/websites) The httpMethod filter has an unknown value.
invalidOrganizationId(400, list endpoints of DNS, ICMP, SMTP, SSH, TCP, FTP and IMAP/POP monitors, GET /api/dashboard-data, GET /api/onboarding-status, GET /api/onboarding-details, GET /api/onboarding/wizard) The organizationId parameter is not a valid organization ID.
invalidCheckType(400, GET /api/websites/:id/check-history) checkType has an unknown value.
locationIdRequired(400, GET /api/websites/:id/location-series) locationId is missing or not a positive integer.
badRequest(400, GET /api/monitor-tags) monitorType is unknown or monitorId is not an integer.
websiteIdsRequired(400, POST /api/websites/summary and POST /api/maintenance-windows/check/batch) The body needs a websiteIds array.
invalidWebsiteIds(400, POST /api/websites/summary and POST /api/maintenance-windows/check/batch) At least one entry of websiteIds is not a valid identifier.
tooManyWebsiteIds(400, POST /api/websites/summary) Too many websiteIds in one request; split the request.
batchSizeExceeded(400, POST /api/maintenance-windows/check/batch) The batch exceeds the maximum size; split the request.
updateFailed(500, PATCH /api/websites/:id, PATCH /api/websites/:id/check-config, PATCH /api/status-pages/:id) The update could not be saved.
delete_failed(500, DELETE /api/websites/:id) The website could not be deleted. Legacy snake case code.
invalidPeriod(400, GET /api/websites/:id/report.pdf) period must be last-week, last-month or last-quarter.
missingScreenshotId(400, GET /api/screenshots/:id) The screenshot ID is missing.
checkNotFound(404, GET /api/screenshots/:id) The check the screenshot belongs to does not exist or is out of scope.
screenshotNotFound(404, GET /api/screenshots/:id) The screenshot does not exist or has expired.

Maintenance windows

CodeMeaning
mixedCustomers(400, POST /api/maintenance-windows and PATCH /api/maintenance-windows/:id) All selected targets must belong to the same customer.
mixedTagOrganizations(400, POST /api/maintenance-windows and PATCH /api/maintenance-windows/:id) All selected tags must belong to one organization.

Incidents and change requests

CodeMeaning
idRequired(400, the incident endpoints under /api/incidents/:id) The incident ID is missing in the path.
incidentNotFound(404, GET /api/incidents/:id and the other incident endpoints, also the IM incident actions) The incident does not exist or is out of scope, including an incident of another organization (GET /api/incidents/:id answered 403 for that until 20.10.2026).
incidentNoCustomer(400, incident write endpoints and IM incident actions) The incident is not linked to a customer, so the access check cannot resolve it.
incidentTargetRequired(400, POST /api/incidents, PATCH /api/incidents/:id) A manual incident needs a customer or at least one status page: customerId and statusPageIds are both missing, or the last status page of an incident without a customer would be removed.
invalidWebsite(400, POST /api/incidents) The website does not belong to this customer.
invalidStartedAt(400, POST /api/incidents) startedAt is not a valid date.
backfillInFuture(400, POST /api/incidents/backfill) startedAt, resolvedAt or an update time is in the future. A backfilled incident is over.
backfillTooOld(400, POST /api/incidents/backfill) startedAt is more than 90 days before the oldest named status page was created; no uptime bar reaches back that far.
invalidDateRange(400, POST /api/incidents/backfill, besides the history endpoints) startedAt is not before resolvedAt, or an update time lies outside them.
postmortemIncidentNotResolved(409, POST /api/incidents/:id/postmortem/publish, besides IM) The incident is not resolved on its status pages yet; publish the postmortem after resolving it.
postmortemNotFound(404, POST and DELETE /api/incidents/:id/postmortem/publish, besides IM) Publish: no text was saved and none was sent. Unpublish: the postmortem is not published.
createFailed(500, POST /api/incidents) The incident could not be created.
sreAttributionNotFound(404, POST /api/incidents/:id/sre-attribution-feedback) The incident has no attribution to give feedback on.
alreadyResolved(409, PATCH /api/change-requests/:id) The change request was already resolved.

Users, sign up and sign in

CodeMeaning
emailNotVerified(403, every authenticated API route except the auth, bootstrap and public status page routes, while the account's email address is unverified; also POST /api/organization/mail-templates/test-send) Verify the email address first.
onboardingStatusUnavailable(503, API routes that require completed onboarding) The onboarding status could not be read. Retry.
missingFields(400, POST /api/auth/register) Company name, email or password is missing.
registrationFailed(422 or 500, POST /api/auth/register) Registration could not be completed. The reason is deliberately not disclosed.
legalVersionMissing(500, POST /api/auth/register) Registration is temporarily unavailable because no legal document version is in force.
organizationCreationFailed(500, POST /api/auth/register) The organization could not be created.
emailRequired(400, POST /api/auth/forget-password) email is missing.
invalidRedirectTo(400, POST /api/auth/forget-password) redirectTo is not allowed: protocol relative, unparseable, on a foreign origin, or not the reset password page.
newPasswordRequired(400, POST /api/auth/set-password) newPassword is missing.
setupSessionMissing(401, POST /api/auth/set-password) No active setup session: the setup link was already used, opened in another browser or by a mail scanner. Use "Forgot password" instead.
passwordAlreadySet(400, POST /api/auth/set-password) The account already has a password.
mfa_invalid_code(401, POST /api/account/mfa/step-up) The verification code is wrong. Legacy snake case code.
emailAndRoleRequired(400, POST /api/users) email and role are required.
emailAlreadyExists(400, POST /api/users) A user with this email address already exists.
emailAlreadyExists(400, POST /api/users/:id/email-change and POST /api/account/email-change) Another member of your organization already signs in with this address. An address held by an account outside your organization is not named: the request answers like a free one and no link is sent.
emailUnchanged(400, POST /api/users/:id/email-change and POST /api/account/email-change) The new address is the current one.
emailChangeLinkInvalid(400, POST /api/auth/email-change/confirm) The confirmation link is unknown, expired (24 hours), already used, replaced by a newer request, or the account's address changed in the meantime. Request the change again.
invalidPassword(400, POST /api/account/email-change) The current password is wrong.
emailSendFailed(502, POST /api/users/:id/email-change and POST /api/account/email-change) The confirmation link could not be sent. The address is unchanged; try again.
customerIdsMultipleOrgs(400, POST /api/users) All customerIds must belong to a single organization.
userCreationFailed(500, POST /api/users) The user could not be created.
invalidRole(400, PATCH /api/users/:id) role is not one of the allowed roles; the message lists them.
selfDeletionNotAllowed(400, DELETE /api/users/:id) You cannot delete your own account through this endpoint.
userDeletionFailed(500, DELETE /api/users/:id) The user could not be deleted.
missingUserId(400, POST /api/users/:id/mfa/reset and GET /api/assets/avatar/:userId) The user ID is missing.
avatarNotFound(404, GET /api/assets/avatar/:userId) The user does not exist, belongs to another organization, or has no avatar.
contentTypeMismatch(400, POST /api/user/avatar and POST /api/users/:id/avatar) The uploaded bytes do not match the declared image type.

Single sign on and OAuth

CodeMeaning
ssoAdminOnly(403, all /api/organization/sso endpoints) Only organization admins may manage SSO.
ssoNoOrganization(400, all /api/organization/sso endpoints) The session is not linked to an organization.
ssoInvalidInput(400, PUT /api/organization/sso, POST /api/organization/sso/test) A required or invalid SSO field; data.field names it (e.g. clientSecret, idpMetadataXml).
ssoDiscoveryFailed(400, PUT /api/organization/sso) The OIDC discovery document of the issuer could not be loaded, names a different issuer than the one entered, or lacks an HTTPS endpoint (authorization_endpoint, token_endpoint, jwks_uri; userinfo_endpoint if present).
ssoSamlMetadataInvalid(400, PUT /api/organization/sso) The SAML IdP metadata is invalid, or its sign in URL is not HTTPS.
ssoDomainTaken(409, PUT /api/organization/sso) The domain is already used by another organization's SSO.
ssoEnforceNotAllowed(409, PUT /api/organization/sso) "SSO only" can only be switched on after the domain is verified and one SSO login succeeded.
ssoNotConfigured(404, POST /api/organization/sso/verify-domain, POST /api/organization/sso/test without issuer; 400, POST /api/status-pages and PATCH /api/status-pages/:id with visibility: sso_members_only) SSO is not configured yet; for a status page: the organization has no verified SSO.
unknownOauthClient(404, GET /api/oauth/consent-context) The OAuth client is unknown.
consentForwardFailed(502, POST /api/oauth/consent) The consent was recorded, but no redirect URI came back to forward the client to.

API tokens and push tokens

CodeMeaning
customerIdRequired(400, POST /api/customer/tokens) customerId is required.
invalidTokenId(400, DELETE and PATCH /api/organization/tokens/:id, DELETE /api/customer/tokens/:id) The token ID is not valid.
tokenNotFound(404, DELETE and PATCH /api/organization/tokens/:id, DELETE /api/customer/tokens/:id) The token does not exist or is out of scope.
tokenCreationFailed(500, POST /api/organization/tokens) The API token could not be created.
tokenDeletionFailed(500, DELETE /api/organization/tokens/:id) The API token could not be deleted.
imPushTokenNotFound(404, DELETE /api/im/push-tokens/:token) The push token is not registered for this user.

Status pages and custom domains

CodeMeaning
invalidSlug(400, POST /api/status-pages and PATCH /api/status-pages/:id) The slug has an invalid format.
domainVerificationFailed(400, POST /api/status-pages/domains/verify, POST /api/organization/whitelabel/domains/verify) The TXT record with the verification token was not found. data.recordName is the name we queried, data.expected the value we expect, data.observed the TXT values we actually saw (at most 10), and data.lookup what the lookup returned: records (values found, none matches), noRecords (the name exists without TXT), nxdomain (the name does not exist), timeout or error. data.nameservers names the delegated zone and its authoritative nameservers, data.authoritative what one of them answered directly, data.propagation reads both (propagating, not_published, unknown). The failure stays on the domain as lastVerificationError / lastVerificationErrorAt until the next successful verification; GET /api/status-pages/domains/{id}/diagnostics and GET /api/organization/whitelabel/domains/{id}/diagnostics check DNS and certificate live.
brandingAssetNotFound(404, DELETE /api/organization/whitelabel/branding/:kind) Nothing is uploaded for this kind of logo or favicon, also on a second DELETE.
invalidBrandingAssetKind(400, DELETE /api/organization/whitelabel/branding/:kind) kind is not one of logo, logoLight, logoDark, favicon, faviconLight, faviconDark.
slugOrHostnameAlreadyExists(409, POST /api/status-pages) The slug or hostname is already taken.
statusPageHasNoCustomer(400, POST /api/status-pages/:id/change-requests) The status page has no customer (customerId: null), so there is no customer who could ask: such a page takes no change requests. Change it directly with an organization-wide role.
statusPageLimitReached(409, POST /api/status-pages, POST /api/status-pages/:id/components, POST /api/status-pages/:id/groups, POST /api/status-pages/public/:slug/subscribe, POST /api/status-pages/templates) The customer's package allows no more status pages (maxStatusPages, also when a page is moved to that customer), the organization already has 200 templates, or the page already has 500 components, 500 groups or 50 webhook, Slack and Teams subscriptions; data.max carries the limit. An organization has no limit on status pages.
statusPageMaintenanceNotFound(404, GET, PATCH and DELETE /api/status-pages/maintenances/:id and its actions) The scheduled maintenance does not exist, belongs to another organization or is on a status page outside your customer scope.
statusPageMaintenanceClosed(409, PATCH /api/status-pages/maintenances/:id, POST .../cancel, .../complete, .../updates) The maintenance is cancelled, or the action does not fit its state: only an upcoming maintenance can be cancelled, only a running one completed.
customCssInvalid(400, PATCH /api/status-pages/:id/design, PATCH /api/status-pages/:id with designConfig) The custom CSS was rejected; data.reason names why: syntax, atRuleNotAllowed, functionNotAllowed, urlNotAllowed, propertyNotAllowed, escapeNotAllowed, htmlNotAllowed or controlCharacter.
customCssTooLarge(400, same routes) The custom CSS is larger than 20000 bytes; data.max carries the limit.
statusPageComponentNotFound(404, PATCH and DELETE /api/status-pages/:id/components/:componentId, PUT /api/status-pages/:id/components/order, POST /api/status-pages/public/:slug/subscribe; 400, PATCH /api/status-pages/:id with audienceGroups) The component does not exist on this status page.
subscriptionPhoneInvalid(400, POST /api/status-pages/public/:slug/subscribe) phone is not a mobile number in international format (+ or 00, country code, 8 to 15 digits).
subscriptionPushInvalid(400, POST /api/status-pages/public/:slug/subscribe) pushSubscription.keys are not a P-256 public key (p256dh, 65 bytes) and a 16-byte auth secret, base64url.
subscriptionTargetUrlInvalid(400, POST /api/status-pages/public/:slug/subscribe) targetUrl is not a valid https URL, or it carries credentials.
subscriptionTargetUrlRejected(400, POST /api/status-pages/public/:slug/subscribe) targetUrl resolves to a loopback, private, link-local or otherwise non-public address; status page messages are only sent to public hosts.
statusPageComponentNotOnPage(400, POST /api/incidents, PATCH /api/incidents/:id, POST and PATCH /api/im/statuspage-rules) The component belongs to a status page that is not named in the request (statusPageIds, or the rule's statusPageId).
statusPageCustomerMismatch(400, POST /api/incidents, PATCH /api/incidents/:id) The status page belongs to another customer than the incident; a customer's incident may only go on pages without a customer or of that customer.
statusPageIdsRequired(400, POST /api/incidents, PATCH /api/incidents/:id) componentIds was sent without statusPageIds.
statusPageComponentDependencyConflict(409, POST /api/status-pages/:id/components) The provider already is a component of this status page; a provider appears at most once per page.
statusPageComponentGroupNotFound(404, PATCH and DELETE /api/status-pages/:id/groups/:groupId, and every component endpoint that takes a groupId) The group does not exist on this status page.
statusPageComponentMonitorConflict(409, POST /api/status-pages/:id/components, PATCH /api/status-pages/:id/components/:componentId) The monitor already is a component of this status page; a monitor appears at most once per page.
statusPageComponentMonitorCustomerMismatch(400, POST /api/status-pages/:id/components and PATCH /api/status-pages/:id) The monitor belongs to another customer than the status page, or the page is moved to a customer that does not own all of its monitor components.
statusPageComponentNotManual(400, PATCH /api/status-pages/:id/components/:componentId) manualStatus was sent for a component that is not (or does not become) manual; only manual components carry a manual state.
statusPageComponentSourceInvalid(400, PATCH /api/status-pages/:id/components/:componentId) The source change is not possible: sourceKind: "monitor" without monitorType/monitorId for a manual component, a monitor together with sourceKind: "manual", or a dependency component (it keeps its provider).
statusPageSmsUnavailable(403, POST /api/status-pages/public/:slug/subscribe) An sms signup for a page that takes subscriptions but does not offer SMS right now (switched off, no SMS sending on the platform, or no SMS quota in the organization). Same state as smsSubscriptionsEnabled: false on the public page.
statusPageTemplateNotFound(404, GET, PATCH and DELETE /api/status-pages/templates/:id) The template does not exist or belongs to another organization.
statusPagesModuleDisabled(403, every non-public endpoint under /api/status-pages except GET /api/status-pages/module and POST /api/status-pages/module/activate; POST /api/incidents and PATCH /api/incidents/:id with a non-empty statusPageIds) The status pages module has not been activated for this organization. Incidents without status pages keep working.
domainVerificationTokenFailed(500, POST /api/status-pages) The domain verification token could not be created.
passwordRequired(400, POST /api/status-pages and PATCH /api/status-pages/:id: password protection switched on without a password; 400, POST /api/status-pages/public/:slug/verify-password: empty password; 401, GET /api/status-pages/public/:slug and GET /api/status-pages/public/by-id/:id: the page is password protected, verify the password first)
invalidPassword(401, POST /api/status-pages/public/:slug/verify-password) The status page password is wrong.
statusPageNotPublic(403, GET /api/status-pages/public/:slug and GET /api/status-pages/public/by-id/:id) The status page is not publicly accessible.
statusPageIpNotAllowed(403, GET /api/status-pages/public/:slug, GET /api/status-pages/public/by-id/:id and POST /api/status-pages/public/:slug/verify-password) The page has an IP allowlist and the request comes from another network. The password is not checked then.
ssoRequired(401, GET /api/status-pages/public/:slug and GET /api/status-pages/public/by-id/:id) The page has visibility: sso_members_only, and the visitor is not signed in, or signed in without the organization's single sign-on.
slugRequired(400, GET /api/status-pages/public/:slug and POST /api/status-pages/public/:slug/verify-password) The slug is missing.
missingSlug(400, POST /api/status-pages/public/:slug/subscribe and POST /api/status-pages/public/:slug/confirm) The slug or public ID is missing.
missingToken(400, POST /api/status-pages/public/unsubscribe and GET /api/download-center/verify) The token is missing.
invalidId(400, GET /api/status-pages/public/by-id/:id, DELETE /api/organization/whitelabel/domains/:id, the roadmap endpoints) The ID in the path is not valid.
subscriberUnsubscribedNotDeletable(409, DELETE /api/status-pages/:id/subscribers/:subscriberId) An unsubscribed subscriber cannot be deleted.
domainCreateFailed(500, POST /api/status-pages/domains) The domain record could not be created.
domainNotBoundToStatusPage(400, POST /api/status-pages/domains/verify and POST /api/status-pages/domains/activate) The domain is not bound to a status page.
domainNoVerificationToken(400, POST /api/status-pages/domains/verify and POST /api/organization/whitelabel/domains/verify) The domain has no verification token.
wildcardDomainNotSupported(400, POST /api/organization/whitelabel/domains) Wildcard domains are not supported.

Branding, SMTP and mail templates

CodeMeaning
insufficientRole(403, POST /api/organization/branding/presign and POST /api/organization/branding/confirm) Only organization admins may upload branding assets.
unsupportedFileType(400, POST /api/organization/branding/presign) The content type is not allowed for this asset type.
objectKeyEmpty(400, POST /api/organization/branding/confirm) The objectKey does not belong to your organization's upload area.
smtpFieldsRequired(400, PATCH /api/organization/smtp) Required SMTP fields cannot be cleared. Disable your own SMTP instead.
smsQuotaRequired(403, POST /api/status-pages, PATCH /api/status-pages/:id) smsSubscriptionsEnabled is switched on while your organization cannot send an SMS: no included SMS left, overage off, or the SMS safety cap reached. Book SMS or enable overage; a page that already has SMS subscriptions on keeps them.
smsCountryNotAllowed(400, POST /api/notification-channels, PATCH /api/notification-channels/:id, POST /api/customers, PATCH /api/customers/:id, PATCH /api/escalation-config/:id) An SMS alert target (config.to / config.phoneNumbers / config.phoneNumber of an sms channel, notificationPhoneNumber, defaultPhoneNumber) is not in international format or its country calling code is outside the EU/EEA, Switzerland and the UK. Alert SMS only go to these countries.
smtpConfigIncomplete(400, PATCH /api/organization/smtp and POST /api/organization/smtp/test) The SMTP configuration is incomplete: host, port, username, password and sender address are required.
smtpPasswordMissing(400, POST /api/organization/smtp/test) A username is set but no password.
smtpPasswordRequiredForNewHost(400, POST /api/organization/smtp/test) The host changed, so the password must be entered again.
missingRecipientEmail(400, POST /api/organization/smtp/test) toEmail is missing.
smtpSendFailed(502, POST /api/organization/smtp/test) Your SMTP server did not accept the test mail; the message carries the server's answer.
mailTemplateNotEditable(400, the mail template and snippet endpoints under /api/organization) This mail is not editable.
mailTemplateInvalid(400, PUT /api/organization/mail-templates/template and POST /api/organization/mail-templates/test-send) The template is invalid; data.issues lists the problems, such as unknown snippets.
mailTemplateConflict(409, PUT /api/organization/mail-templates/template and PUT /api/organization/mail-snippets/snippet) Someone else saved at the same time. Reload and apply your change again.
mailTemplateVersionNotFound(404, POST /api/organization/mail-templates/restore) The version to restore does not exist.
mailTemplateTestSendMailOnly(400, POST /api/organization/mail-templates/test-send) Test sends are only available for mails.
mailTemplateTestSendLimit(429, POST /api/organization/mail-templates/test-send) Too many test sends. Wait before trying again.
mailTemplatePaidPlanRequired(403, PUT /api/organization/mail-templates/template, POST /api/organization/mail-templates/restore and PUT /api/organization/mail-snippets/snippet) Saving custom mail templates and snippets needs a paid plan. Templates that are already saved stay in use, and reading, preview and reset stay open.
emailProviderRejected(502, POST /api/organization/mail-templates/test-send) The email provider rejected the test mail.
mailSnippetInvalid(400, PUT /api/organization/mail-snippets/snippet) The snippet is invalid; data.issues lists the problems.
mailSnippetInUse(409, DELETE /api/organization/mail-snippets/snippet) The snippet is still used; data.usedIn lists where.
mailAssetNotFound(404, DELETE /api/organization/mail-assets/:id; 400 with data.assetIds, PUT /api/organization/mail-templates/template and PUT /api/organization/mail-snippets/snippet) The image does not exist in your media library.
mailAssetInUse(409, DELETE /api/organization/mail-assets/:id) The image is still used; data.usedIn says how often.
mailAssetLimit(409, POST /api/organization/mail-assets) The media library is full; data.limit is the maximum.
mailAssetTooLarge(413, POST /api/organization/mail-assets) The image is too large.
mailAssetType(415, POST /api/organization/mail-assets: only PNG, JPEG, GIF or WebP; 400: exactly one file is expected)

Onboarding wizard

CodeMeaning
customerCreateFailed(500, POST /api/onboarding/wizard/customer) The customer could not be created.
invalidTarget(400, POST /api/onboarding/wizard/check) The target is not a valid URL or host.
monitorAlreadyExists(409, POST /api/onboarding/wizard/target) The organization already has a monitor. (409, POST /api/websites and POST /api/{dns,ftp,icmp,imap-pop,smtp,ssh,tcp}-monitors) This customer already has a monitor of this type for the same target; data.existingId and data.existingPublicId name it. Send allowDuplicate: true to create it anyway.
targetHostMonitorLimitReached(403, POST /api/websites and POST of the protocol monitors dns, ftp, icmp, imap-pop, smtp, ssh, tcp) The organization already has 100 monitors for this target host, counted across all monitor types (exact hostname; for websites with connectHost the connect target counts, heartbeat does not count); data.host names the normalized host, data.limit the limit. The same code comes on PATCH when the change moves the monitor to another host (hostname, url or connectHost); a PATCH that keeps the host always succeeds. allowDuplicate: true does not lift the limit. It protects against the check fleet being misused as a load generator; contact support for a higher limit.
targetHostPlatformLimitReached(403, same endpoints and same PATCH rule as targetHostMonitorLimitReached) The target host already has 300 monitors across all Uptimeify customers, counted the same way. data.host names the normalized host, data.limit the limit; the message does not reveal how many monitors other organizations have. Existing monitors stay in place. Contact support if you need to monitor this host.
monitorCreateFailed(500, POST /api/onboarding/wizard/target) The monitor could not be created.
channelCreateFailed(500, POST /api/onboarding/wizard/channel) The notification channel could not be created.
verificationSendFailed(502, POST /api/onboarding/wizard/channel) The verification message could not be delivered.
noAlertAddress(409, POST /api/onboarding/wizard/test-alert) No alert address is configured yet.
noMonitor(409, POST /api/onboarding/wizard/test-alert) There is no monitor to send a test alert about yet.
testAlertSendFailed(502, POST /api/onboarding/wizard/test-alert) The test alert could not be delivered.
testSendRateLimited(429, POST /api/notification-channels/test, /api/escalation-config/:id/test, /api/organization/smtp/test, /api/organization/sso/test, /api/onboarding/wizard/test-alert, /api/im/sources/:id/test-alert) More than 10 test sends per minute for your organization, shared across these endpoints; a syntax check (dryRun) does not count. retryAfter gives the seconds until the next window.

Roadmap and bug reports

CodeMeaning
featureNotFound(404, the roadmap endpoints under /api/roadmap) The feature request does not exist.
featureRequestCreationFailed(500, POST /api/roadmap) The feature request could not be created.
commentCreationFailed(500, POST /api/roadmap/:id/comments) The comment could not be created.
invalidCommentId(400, PATCH /api/roadmap/comments/:id) The comment ID is not valid.
commentNotFound(404, PATCH /api/roadmap/comments/:id) The comment does not exist.
invalidCursor(400, GET /api/roadmap/:id/comments) The pagination cursor is not valid.
roadmapChallengeMissing(400, POST /api/roadmap, POST /api/roadmap/vote, POST /api/roadmap/:id/comments) The anti bot proof is missing. Fetch a challenge from GET /api/roadmap/challenge first.
roadmapChallengeInvalid(400, same endpoints) The challenge token, signature, payload, action, visitor or proof of work does not match. Fetch a new challenge.
roadmapChallengeExpired(400, same endpoints) The challenge has expired. Fetch a new one.
roadmapChallengeUsed(400, same endpoints) The challenge was already used. Fetch a new one.
roadmapChallengeUnavailable(503, same endpoints) Challenge verification is temporarily unavailable. Retry shortly.
roadmapChallengeNotConfigured(500, same endpoints and GET /api/roadmap/challenge) The challenge secret is not configured on the server.
adminNotesPlatformAdminOnly(403, PATCH /api/bugs/:id) adminNotes can only be set by the platform team. Omit the field.

Public endpoints and free tools

CodeMeaning
disposableEmail(422, POST /api/contact and POST /api/waitlist/incident-management) Use an email address that is not disposable.
emailSendFailed(500, POST /api/contact) The contact mail could not be sent.
downloadRequestInProgress(429, POST /api/resource-downloads/sla-template) Another download request for this email address is running. Retry.
downloadRateLimited(429, POST /api/resource-downloads/sla-template) Too many download requests for this email address. Try again later.
invalidOrExpiredToken(404, GET /api/download-center/verify) The download link is invalid or expired.
invalid_plz(400, GET /api/geo/de-city) The German postal code is not valid. Legacy snake case code.
objectionLinksUnavailable(503, GET /api/legal/objection/:token) Objection links are not configured on the server.
objectionNotAvailable(409, POST /api/legal/objection/:token) This notice carries no right of objection.
objectionDeadlinePassed(409, POST /api/legal/objection/:token) The objection deadline has passed.
unsubscribeLinksUnavailable(503, POST /api/public/alert-unsubscribe) Unsubscribe links from alert emails are not configured on the server. The link itself is not broken.
invalidBody(400, POST /api/public/dependencies/:slug/report) The report body is invalid; statusMessage names the first problem.
toolResultEmptyBody(400, POST /api/tools/result) The body is empty.
toolResultInvalidJson(400, POST /api/tools/result) The body is not valid JSON.
toolResultTooLarge(413, POST /api/tools/result) The result is too large; data.maxBytes is the limit.
toolResultNotFound(404, GET /api/tools/result/:id) The shared result does not exist or has expired.
serverMisconfigured(500, sometimes 503, e.g. on website and SMTP secrets, status page password checks, report download links) A required server secret is missing. Not a client error; report it to support.

Platform and admin endpoints

These codes come only from internal endpoints of the Uptimeify platform team (platform admin, billing administration, sandbox checkout) and from internal helpers. They are not part of the public API, and neither an API token nor a regular organization login can reach them. They are listed here so that every data.code is named.

CodeMeaning
billingDisabledFreeOrg(400, platform admin: retry billing for a payment) The organization pays 0.00 for its base price and its SMS overage, so billing is disabled and there is nothing to retry.
billingModeConflict(409, platform admin: quota price, quota migration and manual billing of an organization) A quota price above 0 and manual billing exclude each other. Switch the organization off the other billing mode first.
cancellationEnqueueFailed(503, platform admin: delete an organization now) The deletion job could not be queued. data.reverted says whether the organization was restored; if it is false, the organization is marked cancelled without a job and needs manual follow up.
confirmNameMismatch(400, platform admin: delete an organization now) confirmName does not match the organization name. Send the exact name.
deadlineInThePast(400, platform admin: send or retry a legal notice) The objection deadline has already passed. Set a new deadline before sending.
discountCodeAlreadyExists(409, platform admin: create a discount code) A discount code with this code already exists.
emailOverrideNotSupported(400, platform admin: generate a report) The body contains email, but the recipient always comes from the customer. Remove the field.
emptyUpdate(400, platform admin: update a dependency) The body contains no field to update.
enqueueFailed(502, platform admin: send, retry or test send a legal notice) The send job could not be queued. Retry; on a test send data.queued says how many languages were already queued.
enqueueFailedSendStarted(502, platform admin: send a legal notice) Queueing failed after the send had already started. Resume it with the retry action instead of sending again.
fileNotFound(404, platform admin: update a download center file) The file does not exist.
indexNowSyncFailed(502, platform admin: IndexNow sync) The IndexNow submission failed. Retry later.
indexNowSyncInProgress(409, platform admin: IndexNow sync) Another IndexNow sync is already running. Wait for it to finish.
invalidDateFormat(400, platform admin: trigger the monthly billing run) month (1 to 12 or YYYY-MM) or year is not valid.
invalidLexwareId(400, internal invoice client) An invoice or file ID for the accounting provider (Lexware) is not a UUID. The invoice PDF download currently passes this on as generic.
invalidNoticeState(400, platform admin: update or send a legal notice) The notice combines fields that do not fit together, for example a deadline that does not match the change kind or lies after the effective date, or a terms or DPA notice without a version.
invalidObjectKey(400, platform admin: download center upload) The object key must start with a publicly deliverable prefix (branding/, download-center/ or downloads/).
invalidPrice(400, platform admin: set custom pricing for an organization) The price must be a whole number of cents, 0 or more.
invalidProxyTarget(400, first party proxy for the real user monitoring script) The requested path would leave the collector origin, so the request is refused.
mollieCustomerOverrideForbidden(400, platform admin: trigger the monthly billing run) mollieCustomerIdOverride is only accepted in test mode, or in live mode when it equals the target organization's own Mollie customer ID.
noRecipients(400, platform admin: generate a report, send a legal notice) There is no recipient: the customer has neither a notification address nor an account email address, or the legal notice matches nobody.
noticeNotEditable(409, platform admin: update or delete a legal notice) The notice has already been sent and can no longer be changed.
noticeNotFound(404, platform admin: legal notices) The legal notice does not exist.
organizationAlreadyDeleted(409, platform admin: delete an organization now, cancel a deletion) The deletion is already complete. The data is gone and the organization cannot be restored.
paymentNotFound(404, sandbox checkout, not available in production) The test payment is unknown.
platformAdminDisabledInCustomerContext(403, every platform admin endpoint) A platform admin is working in customer context. Platform admin endpoints stay blocked until the customer context is cleared.
platformMaintenanceNotFound(404, platform admin: update or delete a platform maintenance) The platform maintenance does not exist.
publishedAtNotSettable(400, platform admin: create or update a dependency) publishedAt cannot be set here, publishing is a separate step. Remove the field.
reportNotFound(404, platform admin: update a dependency status report) The report does not exist.
sandboxCheckoutFailed(400, sandbox checkout, not available in production) The test checkout could not be completed; statusMessage names the reason.
searchQueryRequired(400, platform admin: organization search) The query parameter q is missing.
sitemapUnavailable(502, platform admin: IndexNow status) The sitemap could not be read.
versionExists(409, platform admin: create a legal document version or a legal notice with a new version) This version of the document already exists.
websiteIdRequired(400, platform admin: generate a report) websiteId is missing.

Incident Management: SMS and voice before phone verification (28.10.2026)

EndpointChange
POST /api/im/notification-settings/rules, PUT /api/im/notification-settings/channelssms and voice steps are accepted without a verified phone number (200 instead of 422 imPhoneNotVerified; the code is retired). They are stored and wait: every page until the number is verified is logged as skipped with reason unverified.
GET /api/im/notification-settingsNew fields lastAdminChangeAt and lastAdminChangeBy: when and by whom an organization admin last set these settings.
GET, PUT /api/im/users/:userId/notification-settings, GET, PUT /api/im/notification-templateNew: organization admins set a person's notification chain and the default chain for new users.

Every error carries a code (20.10.2026)

Every error response now carries data.code; texts and status codes are unchanged. Errors without a specific reason use the fixed codes unauthorized (401), forbidden (403), <resource>NotFound or notFound (404), invalidRequestBody (400), rateLimited (429) and internalError (500). New specific codes:

CodeMeaning
gone(410) The URL was removed permanently.
methodNotAllowed(405) Wrong HTTP method for this path, e.g. GET /mcp.
wrongTenant(403) The session belongs to another tenant than the domain it was sent to.
registrationDisabledOnDomain(403) Sign-up is closed on status page and customer domains.
monitorQuotaBelowActiveCount(400) The new monitor quota is below the number of active monitors.
ambiguousPackage(400) The package name matches more than one package of the organization.
invalidDomainName(400) Not a valid domain name.
domainTldNotSupported(400) No expiry lookup (RDAP) is available for this top-level domain.
invalidHeartbeatToken(400) The heartbeat token in the ping URL is malformed.
heartbeatTokenNotFound(404) No heartbeat monitor has this token.
agentAuthUnavailable(503) Agent authentication is not enabled.
serviceAuthNotEnabled(400) Service identities are not enabled.
claimedOrInFlight(409) The agent is already claimed, or a claim is in progress.
claimExpired(400) The claim token has expired.
authMetadataUnavailable(502) The upstream OAuth metadata could not be fetched.
invalidToolInput(400) Free tools (/api/tools): the input is invalid; statusMessage names the reason.
toolTargetRejected(422) Free tools: the target is private or reserved, or a redirect is invalid.
toolTimeout(504) Free tools: the target did not answer in time.
toolTooManyRedirects(508) Free tools: too many redirects.
toolHostNotResolved(404/502) Free tools: the host does not resolve to a public address.
toolTargetUnreachable(502) Free tools: the target is unreachable or the TLS handshake failed.
toolDataUnavailable(503) Free tools: lookup data (ASN) is not loaded yet; retry later.

Protocol monitor fixes (19.10.2026)

EndpointChange
POST /api/tcp-monitors/:id/trigger-checkAnswered 500 for every TCP monitor (its check queue was not allowed). Now 200. The immediate check after creating or reactivating a TCP monitor was skipped for the same reason and runs again.
GET /api/smtp-monitors/:idReturned an empty config/smtpConfig. Now returns the stored settings, with auth.pass as null.
PATCH on every protocol monitor400 instead of silently storing "[object Object]" as name, dropping a non-array allowedCheckCountryCodes, ignoring a non-object config, or (FTP, IMAP/POP) answering 500 for a non-numeric timeoutSeconds.
GET monitor lists400 invalidRequestBody for a non-integer page/perPage, an unknown sortOrder or malformed tags, instead of silently using defaults.
POST /api/dns-monitors/status/batch400 invalidRequestBody if monitorIds is not an array of positive integers or organizationId is not a positive integer; previously ignored.
POST /api/websites/summaryAnswered 500 for every request (the query read the non-existent columns error and updated_at). Now returns per website latestCheck (with errorMessage, ISO checkedAt), uptime, openIncidents, inMaintenance, alertsLast24h.
GET /api/websites/:id/report.pdfAnswered 500 for every website since 15.08.2026 (it read the location threshold from the website instead of the customer). Now returns the PDF (application/pdf).
POST /api/websites, GET /api/websites/:id/detailsNo longer return playwrightEnvEncrypted, the encrypted script variables. GET /api/websites/:id lists the variable names with redacted values.
PATCH /api/websites/:id (partial update)400 invalidRequestBody for a wrong type or an unknown status, instead of storing "[object Object]" as name, reading checkExpectedResponseEnabled: "false" as true or writing NaN. Each data.issues entry carries path (dot-joined) and message, as on every other endpoint; it was the raw validator issue.
PATCH /api/websites/:id/check-configA rejected body answers 400 with data.code invalidCheckConfig and data.issues; it carried the bare issue list. minPageSize and maxPageSize must be integers of at least 0.
GET /api/websites400 invalidRequestBody for a non-integer page/perPage, an unknown sortOrder (now case-sensitive), malformed tags or a skipMetrics other than 1, true, 0, false.
GET /api/websites/:id/details, GET /api/websites/:id/monitoring-data400 invalidRequestBody for an unknown range, an invalid date/tz/maxPoints, a lone startDate or endDate, or a granularity other than minute. monitoring-data returns responseTimeData[].timestamp as an ISO instant; it was the raw database text.
GET /api/customer-domains with statusesAnswered 500 for every status filter (the count query missed the join to the expiry status). Now filters; an unknown status next to a valid one is 400 invalidStatusFilter instead of being dropped.
POST /api/customers, PATCH /api/customers/:id, POST /api/customers/:id/domains, POST /api/customers/:id/ips, PATCH /api/customer-domains/:id, PATCH /api/customer-ips/:id, POST /api/customer/tokensA rejected body answers 400 with data.code invalidRequestBody and data.issues (path, message); it was data.name ZodError without a code. A wrong type is rejected instead of coerced: monthlyReportsEnabled: "false" was stored as true, any status string was stored, expiryWarningDays: "30" was accepted.
GET /api/customers400 invalidRequestBody for a non-integer page/perPage/organizationId, an unknown status, fields, sortBy or sortOrder; they were replaced by defaults. In the paged shape createdAt, cancelledAt and cancellationDate are ISO instants; they were the raw database text.
GET /api/customer-ipsEach item has customerName and customerPublicId, as the domain list does. The embedded customer row is deprecated.
POST /api/status-pages, PATCH /api/status-pages/:id, PATCH /api/status-pages/:id/design, POST /api/status-pages/domains, POST /api/status-pages/domains/verify, POST /api/status-pages/domains/activateA rejected body answers 400 with data.code invalidRequestBody and data.issues (path, message); it was data.name ZodError without a code. The design numbers (historyDays, incidentLimit, incidentDays, maintenanceLimit, maintenanceDays) must be integers; a string such as "14" was accepted.
GET /api/status-pages/:id/designReturns every design field, as PATCH does: historyDays, showIncidents, incidentLimit, incidentDays, showMaintenance, maintenanceLimit, maintenanceDays and seoTitle were missing. A page without a saved design reports layout statusboard, the layout its public page shows; it reported classic.
DELETE /api/status-pages/:idAlso deletes the page's custom domain. The domain row stayed behind, so adding the same hostname again answered 409 hostnameAlreadyInUse.
GET /api/status-pages/domains/:id, DELETE /api/status-pages/domains/:id, POST /api/status-pages/domains, POST /api/status-pages/domains/verify, POST /api/status-pages/domains/activateApply the caller's customer scope, as the status page endpoints do: a role restricted to some customers gets 403 or 404 for a domain of another customer's page.
PATCH /api/organization, PATCH /api/organizations, PATCH /api/organizations/:id, PATCH /api/organization/billing, PATCH /api/organizations/billing, PATCH /api/organizations/:id/billingA rejected body answers 400 with data.code invalidRequestBody and data.issues (path, message); data was the bare issue list without a code. 401 and 403 now carry data.code (unauthorized, forbidden).
PATCH /api/package-configs, PATCH /api/package-configs/:packageType, PATCH /api/organizations/package-configs/:packageType, PATCH /api/organizations/:id/package-configs/:packageTypeA wrong type is rejected with 400 invalidRequestBody instead of coerced: enableSmsAlerts: "false" was stored as true, maxUrls: "5" was accepted. Numbers must be JSON numbers, switches JSON booleans. allowedCheckCountryCodes must be an array (lower case is still accepted and upper-cased); notes is limited to 4096 characters and alertLocationThreshold to 32 on every variant.
PATCH /api/organization, PATCH /api/organizations, PATCH /api/organizations/:id with protected fieldsrequireMfaAdmins, requireMfaEditors, requireMfaReadonly, requireMfaCustomers, smsOverageSafetyCapCentsMonthly, quotaIpsLimit and quotaAutoUpgradeEnabled only count when the value differs from the stored one. Sending the current value (as Terraform does with the full state) answered 403 (API token, or not a global admin) or 400 mfaRequiredForActor (account without its own second factor); it now succeeds and leaves the field untouched. A real change still needs the same rights as before.
GET /api/package-configs, GET /api/organizations/:id/package-configssummary accepts 0 or 1; any other value answers 400 invalidRequestBody instead of being read as 0.
Every endpoint that takes a resource id or public idAn identifier of the wrong form answers 400 with data.code invalidIdentifier; an unknown public id 404 with data.code <resource>NotFound (e.g. organizationNotFound, tcpMonitorNotFound). Both came without data.code.
POST /api/organization/tokens, PATCH /api/organization/smtp, POST /api/organization/smtp/test, PATCH /api/organization/whitelabel/branding, POST /api/organization/whitelabel/branding/upload, POST /api/organization/whitelabel/domains, POST /api/organization/whitelabel/domains/verify, POST /api/organization/whitelabel/domains/activate, POST /api/organization/data-export, POST /api/organization/reports, PATCH /api/organization/reports/:idA rejected body answers 400 with data.code invalidRequestBody and data.issues (path, message); it was data.name ZodError without a code. port must be a JSON number ("587" was accepted); an empty string still clears it.
POST /api/organization/smtp/testA private SMTP host answers 400 smtpHostNotPublic like PATCH /api/organization/smtp, a failed send 502 smtpSendFailed; both were generic.
POST /api/organization/whitelabel/branding/uploadEvery error carries data.code: invalidDataUrl, unsupportedContentType, invalidBase64, emptyUpload, fileTooLarge (413), storageNotConfigured, storageUnavailable (503), uploadFailed (502).
GET /api/organization/report-runslimit (1-200) and offset must be non-negative integers; any other value answers 400 invalidRequestBody instead of falling back to 50 and 0. A limit above 200 is no longer silently capped.
POST /api/organization/whitelabel/domains/verifyFor an already active domain, domain now carries createdAt and updatedAt like every other answer.
POST /api/users, PATCH /api/users/:idA rejected body answers 400 with data.code invalidRequestBody and data.issues; it was data.name ZodError. PATCH now also returns the changed login as user (same shape as GET /api/users/:id) next to success. Unknown customerIds answer invalidCustomerIds as in POST; it was generic.
GET /api/users/:id, DELETE /api/users/:id, POST /api/usersError answers carry their text in statusMessage; it read Server Error (e.g. a 404 userNotFound).
POST /api/incidents/:id/false-alarmA rejected body answers 400 with data.code invalidRequestBody and data.issues; it was data.name ZodError.
POST /api/websites, POST /api/dns-monitors, POST /api/ftp-monitors, POST /api/icmp-monitors, POST /api/imap-pop-monitors, POST /api/smtp-monitors, POST /api/ssh-monitors, POST /api/tcp-monitorsA rejected body answers 400 with data.code invalidRequestBody and data.issues (path, message); it was data.name ZodError without a code. With this, every endpoint that validates its JSON body answers in this one form.
GET /api/customer-domains, GET /api/customer-ips, GET /api/organization/audit, GET /api/organization/smtp/logsAn invalid query parameter answers 400 with data.code invalidRequestBody and data.issues (path, message); it was data.name ZodError without a code.
PATCH on every protocol monitor (DNS, FTP, ICMP, IMAP/POP, SMTP, SSH, TCP)A rejected checkInterval answers 400 with data.code invalidCheckInterval (not a number), checkIntervalTooLow (below the package minimum) or checkIntervalTooHigh; it carried no code. The text is unchanged.
PATCH /api/escalation-config/:id with defaultEmail or defaultPhoneNumberUpdates only the organization's own email or SMS channel. It could overwrite a customer-bound channel of the same type instead.
GET /api/websites/:id/details, GET /api/websites/:id/monitoring-data and every protocol monitor details without date"Today" is the caller's local calendar day from tz. It was the UTC day, so in the first hours after local midnight (east of UTC) the response showed the previous day without the latest checks.
GET /api/escalation-config/:idRequires the same rights as PATCH: an organization admin with unrestricted scope. Read access was enough, so a read-only or customer-bound login could read the webhook URL, headers and body template. Now 403 forbidden or 403 customerScopedTokenForbidden.
PATCH /api/customers/:idChanging the package (packageId or packageType) or the permission fields (canEditManaged, allowSelfService, maxSelfServiceUrls, SMS/notification rights) needs an organization admin with unrestricted scope. A customer-bound token passed before. A package change answers 403 packageOrgOnly; sending the unchanged package (full state, as Terraform does) still works; permission fields are ignored as for other non-admins.
POST /api/customers/bulk with action: packageLike PATCH /api/customers/:id: only an organization admin with unrestricted scope changes the package. Other callers get a per-customer failed entry with reason: packageOrgOnly.
PATCH /api/organization/tokens/:idPartial update: an omitted customerId or expiresInDays leaves the customer binding and expiry unchanged. Only an explicit null clears them. Previously a body with only name made the token organization-wide and non-expiring.
POST /api/maintenance-windows, PATCH /api/maintenance-windows/:id, DELETE /api/maintenance-windows/:idA customer-restricted caller (read-only or editor login with assigned customers, customer-bound token) creates, changes or deletes windows only on self_service monitors. Windows for the whole customer, with tags or on managed monitors need the customer's canEditManaged exception, otherwise 403 managed_by_organization.
Customer-bound API tokensA trailing slash (/api/customers/bulk/) no longer bypasses the restrictions on customer-bound tokens: same response as without it.
GET /api/organization/data-export/:id/download, PATCH and DELETE /api/organization/tokens/:id, GET and DELETE /api/organization/whitelabel/domains/:idOrganization-wide, so a caller restricted to customers gets 403 customerScopedTokenForbidden, as the export status already did. Customer-bound tokens were stopped before; a global admin in platform-admin customer context got through (until 20.10.2026).
PATCH /api/change-requests/:idOnly an organization-wide caller decides a change request; a customer-bound token or login gets 403 customerScopedTokenForbidden. With an organization API token it answered 500; it now succeeds and records the token's issuer as the decider.
POST /api/users/:id/mfa/resetResetting the second factor of a platform account (global admin or supporter) needs a global admin, as PATCH and DELETE do: 403 globalUserProtected. A user of another organization answers 404 userNotFound like a missing one (since 20.10.2026; it answered 403 insufficientPermissions before and so confirmed the id).
GET /api/organization/reports, GET /api/organization/reports/:id, PATCH /api/organization/reports/:id, DELETE /api/organization/reports/:id, POST /api/organization/reports/:id/send-nowA customer-restricted caller (a read-only or editor login with assigned customers) only sees reports that cover exclusively customers in their scope (scopeMode customers). Other reports are missing from the list and answer 404 notFound. Reports over all customers or over tags were visible to them.
POST /api/organization/reports and PATCH /api/organization/reports/:idA customer-restricted caller can only create a report, or switch one, for customers within their scope: 403 forbidden. Sending the unchanged scope still works.
GET /api/organization/report-runs and GET /api/organization/report-runs/:id/pdfRuns follow the visibility of their report: a customer-restricted caller no longer lists or downloads runs of reports over other customers (404 reportRunNotFound).
GET /api/organizations/:id/notification-stats, GET /api/organizations/:id/dashboard-stats, GET /api/organizations/:id/package-stats and GET /api/organizations/:id/package-configs/:packageType/statsOrganization-wide figures: a customer-restricted caller gets 403 customerScopedTokenForbidden.
DELETE /api/organization/tokens/:id and PATCH /api/organization/tokens/:idThe admin check reads the role from the current user record. A demoted admin kept the right as long as their session lived.
GET /api/invoices/:invoiceId/pdfA customer-bound token gets 403 customerScopedTokenForbidden; it could download the organization's invoices through this short route.
POST /api/incidents/:id/sre-attribution-feedbackNeeds write access to the incident (admin or editor within the incident's customer scope), as every other incident change does. A read-only login gets 403 forbidden.
GET /api/organization/data-export, GET /api/organization/data-export/:idLike the download: an organization admin with unrestricted scope. Others get 403 forbidden or 403 customerScopedTokenForbidden.
GET /api/status-pages/:id/designChecks the customer scope of the page, as PATCH does: a page of another customer answers 403 forbidden.
PATCH /api/status-pages/:id/design, PATCH /api/status-pages/:id with designConfig, showRecentIncidents or showRecentMaintenance, POST /api/status-pages with showRecentIncidents or showRecentMaintenanceChanging a status page's design needs the role admin or editor. readonly users, also customer-bound ones on their self_service pages, and tokens they issued get 403 forbidden; reading with GET stays open to them.
GET /api/status-pages/domains/:id and DELETE /api/status-pages/domains/:idA domain not bound to a status page exists only for callers with unrestricted scope; a customer-restricted caller gets 404 domainNotFound.
POST /api/users/:id/avatar and DELETE /api/users/:id/avatarChanging the avatar of a platform account (global admin or supporter) needs a global admin, as PATCH and DELETE of the user do: 403 globalUserProtected.
GET /api/incidentsInvalid limit, offset, includeTotal or source answer 400 invalidRequestBody. They fell back silently: ?source=manuel listed every source, ?limit=abc returned 100 rows. limit above 500 is still capped.
GET /api/change-requestsAn unknown status answers 400 invalidRequestBody; it listed the open requests. 401 and 403 now carry data.code (unauthorized, forbidden).
PATCH /api/change-requests/:id, POST /api/monitors/:type/:id/change-requestsA rejected body answers 400 with data.code invalidRequestBody and data.issues; it was data.name ZodError. Every error carries data.code: unauthorized, forbidden, changeRequestNotFound, invalidChangeRequestId, invalidMonitorId.
GET /api/agent-claim/context, POST /api/agent-claim/confirmErrors carry data.code (unauthorized, claimAttemptRequired, invalidClaimToken) and a statusMessage; data.error stays for existing readers. POST checks its body: a user_code that is not text, or write_scopes that is not a list of texts, answers 400 invalidRequestBody. Both were dropped silently.
GET /api/oauth/connectionsThe 401 carries its text in statusMessage; it read Unauthorized only in message.
GET /api/domainsInvalid page, perPage, organizationId or customerId answer 400 invalidRequestBody. They fell back silently (?page=abc was page 1, ?customerId=12abc was customer 12). perPage above 200 is still capped.
Details endpoints of FTP, ICMP, IMAP/POP, SMTP, SSH and TCP monitorsmonitoringData.responseTimeData[].timestamp is an ISO instant; it was the raw database text (2026-10-19 13:36:00+00). Invalid range, date, tz, startDate/endDate, granularity (and ICMP includeIncidentHistory/includeAlertHistory) now answer 400 instead of falling back silently. The website details endpoint emits ISO instants too.
POST /api/custom-fields, PATCH /api/custom-fields/:id, POST /api/tags, PATCH /api/tags/:id, POST /api/monitor-tags, DELETE /api/monitor-tags, POST /api/maintenance-windows, PATCH /api/maintenance-windows/:id, POST /api/maintenance-windows/preview-count, POST /api/maintenance-windows/preview-occurrences, POST /api/notification-channels, PATCH /api/notification-channels/:idA rejected body answers 400 with data.code invalidRequestBody and data.issues; it carried no data.code.
POST /api/maintenance-windows, PATCH /api/maintenance-windows/:id, POST /api/maintenance-windows/preview-occurrencesstartTime and endTime take an ISO string or epoch milliseconds. null or true answers 400 invalidRequestBody instead of being stored as 01.01.1970.
GET /api/maintenance-windows400 invalidRequestBody for a filter id that is not a positive integer (for example a public id in websiteId), an activeOnly other than true/false, a format other than json/csv or a download other than 0/1. A bad filter id was dropped and the unfiltered list of the whole organization came back.
GET /api/maintenance-windows, GET /api/maintenance-windows/:idThe embedded website of a window on a single website no longer carries the encrypted columns (authorizationHeaderEncrypted, basicAuthPasswordEncrypted, customHeadersEncrypted, requestBodyEncrypted, mtlsClientCertEncrypted, mtlsClientKeyEncrypted, playwrightEnvEncrypted); they shipped as ciphertext.
POST /api/notification-channels/testThe body is validated: a missing body, an unknown type or a wrong type answers 400 invalidRequestBody; a missing body answered 500.
GET /api/notification-channels, POST /api/notification-channels, POST /api/notification-channels/testScope errors carry data.code: customerNotFound (404), forbidden (403), notificationChannelScopeMismatch (400, organizationId or customerId does not match websiteId/customerId), invalidRequestBody (400, invalid organizationId). organizationId: null counts as absent; it answered 400.
PATCH /api/escalation-config/:idNumbers must be integers and isActive a boolean; "10" and "true" answer 400 invalidRequestBody (they were converted). Every validation error was data.code generic, now invalidRequestBody. defaultEmail must be an email address, defaultPhoneNumber a string; both were stored in the organization channel unchecked.
PATCH /api/escalation-config/:id without isActiveNo longer switches the organization webhook channel off. Before 19.10.2026 any update without isActive and without webhookUrl (for example only webhookTimeout) deactivated it.
PATCH /api/escalation-config/:id with only webhookUrlThe organization webhook channel keeps the saved method, headers, template and timeouts; they were removed from its configuration.
POST /api/escalation-config/:id/testErrors carry their own data.code: invalidRequestBody (bad body, missing PagerDuty or Pushover keys, template not valid JSON), webhookUrlNotConfigured, webhookTestFailed (400, the receiver failed or answered an unexpected status); 401 and 403 keep unauthorized/forbidden. Every error was generic.
GET /api/escalation-config/:id, PATCH /api/escalation-config/:id, POST /api/escalation-config/:id/testAn organization id with trailing characters (2abc) answers 400 organizationIdRequired instead of being read as 2; an invalid id was generic.
PATCH /api/custom-fields/:id, DELETE /api/custom-fields/:idA non-integer id such as 1.5 answers 400 fieldIdRequired, as GET does.
POST /api/organization/reports/:id/send-nowSends the report and records a run even when the report is switched off. The enabled switch only governs the schedule; before 19.10.2026 a manual send of a disabled report was skipped silently.
POST /api/custom-fieldsCreating a field with the key of a deleted (deactivated) field reactivates it with the values from the body and answers like a new field. It answered 409 customFieldAlreadyExists. An active field with that key still answers 409. Values stored on customers under the key stay as they are.
GET /api/maintenance-windows, GET /api/maintenance-windows/:idNew field websiteSummary (id, publicId, name, url, or null) for the legacy target website. website (the full website row) is unchanged but deprecated in favour of websiteSummary.
GET /api/escalation-config/:idNo longer creates a configuration. Without a saved one it returns the inactive defaults, with id, createdAt and updatedAt set to null; readers without write access get them too instead of 403. The first PATCH /api/escalation-config/:id stores the configuration with the same defaults.
PATCH /api/escalation-config/:id with isActive: falseDeactivates only the organization webhook channel (no websiteId, no customer). Customer webhook channels stay active; before 19.10.2026 they were switched off as well.
POST /api/escalation-config/:id/testHeaders in webhookHeaders go through the same block list as on PATCH /api/escalation-config/:id: Host answers 400 webhookHostHeaderForbidden, Authorization, Cookie, X-Forwarded-* and Proxy-* answer 400 invalidRequestBody. They were sent as given.
DELETE /api/incidents/:idAnswers { "success": true, "ok": true }. ok stays for existing readers but is deprecated; read success.

Confirmation without two-step verification, admin role by API token (17.11.2026)

EndpointChange
Session requests that answer 403 mfa_step_up_required (creating, updating and deleting API tokens, creating users, changing a role or the active flag, resetting a second factor, the organization's MFA requirement, SSO setup, OAuth consent, account deletion, an admin changing a member's email)An account without two-step verification now gets this answer too and confirms with its current password in the dashboard dialog. data.method says which proof is asked for: totp or password. The confirmation holds for 5 minutes per session. Accounts that sign in through SSO only and have no password are not asked. API tokens are not affected.
POST /api/users with role: "admin", PATCH /api/users/:id changing role to adminWith an API token or agent access token: 403 nonUserSessionForbidden. Invite or promote admins in the dashboard. Other roles work as before, and sending an unchanged role: "admin" (full state, as Terraform does) still succeeds.
POST /api/organization/tokens, POST /api/customer/tokensThe user who created the token and every active admin of the organization receive an e-mail with the token name and the creator.

On this page

SchemaMonitor ownership error codesMonitor quota error codesCustomer package error codesCustomer deletion and user assignment error codesWebsite check-interval error codesWebsite connect target (Ersatzziel) error codesCheck mode error codes (SSH/SMTP/FTP/IMAP-POP monitors)Incident error codesMaintenance window error codesOrganization Reports error codesDependency status error codesReport form error codesData export error codesAudit log export error codesAgent-auth error codesAPI token error codesClaim flow error codesID-JAG error codesConnected apps (OAuth connections) error codesOAuth consent error codesStatus page subscriber error codesPublic IDs in DNS and DNSBL monitor routesIncident Management (IM) API error codesNIS-2 report case error codesPostmortem and follow-up error codesUser management error codesTag error codesChange request error codesNotification channel error codesCustom domain error codesDeprecated fields (renames, 20.10.2026)404 for out-of-scope resourcesRate limit and size error codesWebhook and SMTP target error codesSender domain error codesOrganization suspended or deletedAccount state on the auth endpointsMFA error codesPlan change error codesAccount deletion error codesVAT ID validation error codesUpdate Billing Details: required bodyMore error codesBilling and organizationCustomers, packages and customer IPsMonitorsMaintenance windowsIncidents and change requestsUsers, sign up and sign inSingle sign on and OAuthAPI tokens and push tokensStatus pages and custom domainsBranding, SMTP and mail templatesOnboarding wizardRoadmap and bug reportsPublic endpoints and free toolsPlatform and admin endpointsIncident Management: SMS and voice before phone verification (28.10.2026)Every error carries a code (20.10.2026)Protocol monitor fixes (19.10.2026)Confirmation without two-step verification, admin role by API token (17.11.2026)