"The URL must be a valid link ending in .ICS": the five-minute repair
You paste your calendar link, and the platform refuses it with this message. Five causes explain almost every case. Take them in order: the first settles more than half of all situations.
By the 1calendrier team · Updated 11/08/2026
What is happening to you
You are connecting two calendars. You paste the link, you confirm, and the platform answers: "The URL must be a valid link ending in .ICS". That is the wording Airbnb shows at the time of writing (August 2026); the phrasing varies elsewhere: "invalid link", "URL not valid", "this link does not appear to be a calendar". The meaning is the same: the platform does not recognise what you have just pasted as a calendar link.
Good news: this message can almost always be fixed in under five minutes. Five causes cover nearly every case. Take them in order, from the most frequent to the rarest, each with its own test.
What to do now: the 5 causes, in order
1. You pasted the address of the page, not the calendar link
This is cause number one, by a long way. The address of your listing page, the one shown at the top of the browser with photographs and a booking button, is not a calendar link. The calendar link is a separate address, to be fetched from the calendar settings of the listing, often under a heading such as "Export calendar". If you do not know what it looks like, our guide on what an iCal link is shows it step by step.
The test: open the pasted link in a new tab. If you see a normal web page, with images and menus, it is the wrong link. A real calendar link shows or downloads plain text beginning with the line BEGIN:VCALENDAR.
2. The link begins with webcal:// instead of https://
Some platforms, Abritel first among them, give links that begin with webcal://. Many others refuse that prefix.
The test: look at the first characters of the link. If it begins with webcal://, replace those characters with https:// without touching the rest, then paste it again.
3. A space or a stray character slipped in when pasting
A space at the beginning or the end of the link, a line break in the middle, a full stop added by an autocorrect: one character too many is enough for the link to be refused. It happens above all when the link has travelled through an email, a text message or a document.
The test: paste the link into the browser's address bar and press Enter. If it loads there but is still refused by the platform, copy it again straight from the platform of origin, using the "Copy" button where there is one, with no intermediary in between.
4. The link has expired or has been replaced by the platform
A calendar link is not eternal: according to host reports and the documentation of booking tools, a link may expire when it goes unused for a long time, or be replaced on the occasion of a change to the account or a technical migration by the platform. The old link, the one you had noted down somewhere, no longer answers.
The test: go back to the platform that supplies the link and copy it again, there and then. If that fresh link is accepted where the old one was refused, you have your answer. Remember to put the new link everywhere the old one was pasted. That scenario is set out in why your Airbnb calendar is no longer syncing.
5. The platform has not finished generating the link
A calendar link that has only just been created may take a few minutes to become active. If you create it and paste it straight away, the platform opposite may test it before it is ready.
The test: wait ten minutes or so, open the link in the browser to check that it answers, then paste it again. If the message persists beyond an hour, go back to causes 1 to 4: the problem lies elsewhere.
Why this message is so badly written
The message talks about ".ICS" as though everybody knew what that is. Yet it says something simple: "what you have given me does not look like a calendar link". The platform checks the shape of the link before even trying to read it. Hence the strength of the browser test: either you see calendar text, or you see something else, and you know which side to look on.
The repair, however, only takes you halfway. A link accepted today may be replaced tomorrow (cause 4), and this time with no message at all: the breakdown will be silent. Once the connection has been accepted on both sides, as described in the guide on syncing Airbnb and Booking, take two minutes to check that your calendars really are in sync.
How to avoid going through this again
The "invalid link" message has one merit: it warns you at once. The real danger is its absence. When a link breaks after months of service, no platform shows you that message: it keeps the last data it received and says nothing. Free calendar merging tools do the same: they accept the link on the first day, then warn nobody when it dies.
A monitoring service turns the situation round: it reads your calendar links every 30 minutes, alerts you by email as soon as a link stops responding (after several failures in a row, so as not to cry wolf), and carries on serving the last known good version of your calendar until the repair is made. And for causes 1 and 3 on this page, one detail that changes everything: you can paste a whole email, and the calendar link is picked out of it automatically, with no stray space and no bad copy and paste. The test you have just done by hand, it does again for you, day and night.
Frequently asked questions
My link does not end in .ics, is it still valid?
Often, yes. Some platforms add characters after the .ics, others do not show that ending at all. The message is about the general shape of the link, not only about its end. The real test remains opening the link in a browser.
Is "calendar in the wrong format" the same error?
No. "Invalid link" means the address is refused before it is even read. "Wrong format" means the link answers, but its content cannot be read: an empty or truncated file, or a web page in disguise. The browser test tells the two apart in ten seconds.
Can I shorten the link with a link shortener?
Avoid it. Some platforms refuse shortened addresses, and you lose the ability to compare the pasted link with the original on the day something breaks.
The same link works on one platform and not on the other, how is that possible?
Each platform has its own rules of acceptance. Some convert webcal:// automatically, others do not. Some tolerate a space at the end of a link, others refuse it. A clean link, copied straight from the platform of origin and beginning with https://, passes everywhere.