Frequent SES errors and how to fix them
What each type of SES rejection means and the exact steps to fix it.
Wrong username, password, or Código Arrendador
This is the most common rejection, and it means SES itself refused the login — not that Keyio failed to send anything. It covers messages like "usuario incorrecto", "contraseña incorrecta", HTTP 401/403 responses, and a Código Arrendador that doesn't exist in SES's system.
Each property has its own SES username, password, and Código Arrendador, stored in that property's Edit → SES tab — not a single account shared across your whole portfolio. If you manage several properties, double-check you're editing the one that's actually failing, and watch for a trailing space left over from copy-pasting the password from an email or document.
- 1Open the affected property → Edit → SES tab.
- 2Re-type (rather than paste) the username and password.
- 3Click "Verificar credenciales" to test them directly against SES.
- 4If it still fails, log into hospedajes.ses.mir.es yourself (with Cl@ve or your digital certificate — not these credentials) and re-check the web-service username and password under your web-service configuration, since they're a separate credential pair from your personal portal login.
The username and password configured here are for the SES web service (SOAP API) — a separate credential pair from your own personal login to the hospedajes.ses.mir.es portal, which uses Cl@ve or a digital certificate, not a username/password you can test by logging in directly.
SES says the web service isn't enabled
This shows up as SES error -1 or 10120, often with a raw SOAP fault reading "the user does not have permission to execute web services". It means your SES account's login works, but the Ministerio del Interior hasn't (yet) granted it permission to receive automated submissions — this is a state on SES's own system, not something wrong in Keyio.
Enabling "Acceso a Servicios Web" on hospedajes.ses.mir.es can take hours to actually take effect on their backend, even though their portal shows it as active immediately. If you manage more than one establishment, this permission is granted per Código de Establecimiento — activating it for one property doesn't activate it for another.
Use "Verificar credenciales" in the property's SES tab a few hours after activating. If it still fails with this same error, log into hospedajes.ses.mir.es directly and check your profile's web-service status.
A guest's data doesn't meet SES's format
These errors (codes like 10118, 10121, 10130, 10131) mean SES accepted the login and understood the submission, but rejected one or more guest records because a field doesn't meet its requirements — a missing document support number, an invalid municipality, a value that's too long, or a character SES doesn't accept. Keyio checks guest data against SES's requirements before you can submit, so this should be uncommon — it usually means an edge case slipped past that pre-check rather than something you did wrong.
The detail line shown under the error names the exact field and guest — fix that guest's record (from the rental's guest list) rather than anything in the property's SES settings, then resend.
Everything else: internal or connection errors
A smaller set of errors (codes in the 101xx-1018x range, code 10999, and generic connection failures) come from SES's own infrastructure rather than anything about your credentials or guest data — a malformed request, a temporary outage, or an unexpected response.
There's usually nothing to fix on your end. Try resending in a few minutes; if it keeps failing, contact Keyio support with the rental link and the exact error text so we can investigate.