{"id":263741,"date":"2026-09-19T10:01:03","date_gmt":"2026-09-19T17:01:03","guid":{"rendered":"https:\/\/messengerbot.app\/appointment-reminder-templates\/"},"modified":"2026-09-19T11:35:54","modified_gmt":"2026-09-19T18:35:54","slug":"appointment-reminder-templates","status":"publish","type":"post","link":"https:\/\/messengerbot.app\/ja\/appointment-reminder-templates\/","title":{"rendered":"Appointment Reminder Templates: Text and Email Examples"},"content":{"rendered":"<input type=\"hidden\" value=\"\" data-essbisPostContainer=\"\" data-essbisPostUrl=\"https:\/\/messengerbot.app\/ja\/appointment-reminder-templates\/\" data-essbisPostTitle=\"Appointment Reminder Templates: Text and Email Examples\" data-essbisHoverContainer=\"\"><p><strong>Updated September 2026<\/strong> &mdash; A reminder should make the next step obvious without making the customer hunt for the date, time, location, or reply option. This guide gives you ready-to-edit appointment reminder templates for text messages and email, then shows how to choose timing, handle confirmations, and recover gracefully when someone does not respond.<\/p>\n<p>Use the examples as starting points, not as a reason to send the same sentence to every customer. A salon appointment, a dental visit, a consultation, and a video call each need different details. Keep the useful structure, replace the placeholders, and check your consent and channel rules before sending.<\/p>\n<h2>What a useful appointment reminder includes<\/h2>\n<p>A good reminder answers the questions a customer is most likely to ask in the few seconds after opening it:<\/p>\n<ul>\n<li><strong>Who:<\/strong> the business name or team the customer recognizes.<\/li>\n<li><strong>What:<\/strong> the service, appointment type, or named provider.<\/li>\n<li><strong>When:<\/strong> the local date, time, and time zone when a customer could reasonably be in another region.<\/li>\n<li><strong>Where:<\/strong> a street address, room, video link label, or a clear instruction to check the confirmed booking.<\/li>\n<li><strong>What to do next:<\/strong> confirm, reschedule, arrive early, prepare a document, or reply for help.<\/li>\n<li><strong>How to get help:<\/strong> a monitored phone number, inbox, or reply path that someone actually checks.<\/li>\n<\/ul>\n<p>Keep private information out of the message unless the customer needs it for this appointment. A reference such as \u201cyour Thursday consultation\u201d is often safer than adding a full account number. If you use a link, send customers to the same booking or support destination they saw when they scheduled; avoid adding a surprise redirect.<\/p>\n<h2>Short appointment reminder text templates<\/h2>\n<p>SMS works best when the message can be understood at a glance. The templates below use square brackets for fields your booking system or team should fill in before sending.<\/p>\n<figure class=\"wp-block-image size-full in-content-visual\"><img decoding=\"async\" src=\"https:\/\/messengerbot.app\/wp-content\/uploads\/2026\/09\/reminder-sequence-diagram.png\" alt=\"Appointment reminder sequence from booking to customer response\" title=\"\"><\/figure>\n<h3>General confirmation<\/h3>\n<p>Hi [First name], this is [Business]. Your [service] appointment is [Day, date] at [time] [time zone] at [location]. Reply <strong>YES<\/strong> to confirm or [reschedule instruction]. Questions? Reply here or call [phone].<\/p>\n<h3>One-day reminder<\/h3>\n<p>Reminder from [Business]: we will see you tomorrow, [date], at [time] for [service]. Please arrive [arrival instruction]. Need a different time? [reschedule path].<\/p>\n<h3>Same-day reminder<\/h3>\n<p>Today at [time]: your [service] appointment with [Business], [location or video instruction]. Bring [one useful item] if needed. Reply HELP if you need directions or a change.<\/p>\n<h3>Video appointment<\/h3>\n<p>Hi [First name], your [service] call with [Business] starts [date] at [time] [time zone]. Open the meeting link from your confirmation email [x minutes] before the appointment. Reply here if the link is missing.<\/p>\n<h3>Appointment that needs preparation<\/h3>\n<p>Your [service] with [Business] is [date] at [time]. Please complete [short preparation] before you arrive. If you need accessibility help or a new time, reply [keyword] and our team will help.<\/p>\n<p>Write the reply path in plain language. \u201cReply YES\u201d is clear; \u201cinteract with the automated confirmation workflow\u201d is not. If your system cannot read replies, do not promise that it can. Give the customer a real support route instead.<\/p>\n<h2>Appointment reminder email templates<\/h2>\n<p>Email gives you room to include directions, preparation, cancellation terms, and a calendar link. Put the appointment details near the top so the reader does not have to search through a long paragraph.<\/p>\n<h3>Simple confirmation email<\/h3>\n<p><strong>Subject:<\/strong> Confirm your [service] appointment on [date]<\/p>\n<p>Hi [First name],<\/p>\n<p>Your appointment with [Business] is booked:<\/p>\n<ul>\n<li><strong>Service:<\/strong> [service]<\/li>\n<li><strong>Date and time:<\/strong> [date], [time] [time zone]<\/li>\n<li><strong>Location:<\/strong> [address or meeting instructions]<\/li>\n<li><strong>Duration:<\/strong> [duration, if known]<\/li>\n<\/ul>\n<p>Please <strong>confirm or change the appointment<\/strong> before [cutoff, if applicable] using the booking link from your original confirmation. If you need assistance, reply to this email or call [phone].<\/p>\n<p>Thank you,<br \/>[Business team]<\/p>\n<h3>Friendly day-before email<\/h3>\n<p><strong>Subject:<\/strong> Tomorrow: [service] at [time]<\/p>\n<p>Hi [First name],<\/p>\n<p>This is a quick reminder that your [service] appointment is tomorrow, [date], at [time] [time zone]. We are at [location]. Please [arrival or preparation instruction].<\/p>\n<p>If the time no longer works, use [reschedule path] as soon as possible so we can offer the slot to another customer. Reply to this message if you are unsure what to do.<\/p>\n<h3>Consultation with a preparation checklist<\/h3>\n<p><strong>Subject:<\/strong> Before your [service] consultation on [date]<\/p>\n<p>Hi [First name],<\/p>\n<p>We look forward to speaking with you on [date] at [time]. To make the conversation useful, please have these items ready:<\/p>\n<ul>\n<li>[item or question one]<\/li>\n<li>[item or question two]<\/li>\n<li>[accessibility or language request, if relevant]<\/li>\n<\/ul>\n<p>Your appointment details are [location or meeting instructions]. You can change the time here: [reschedule path].<\/p>\n<h3>Customer-friendly cancellation or reschedule message<\/h3>\n<p><strong>Subject:<\/strong> Need to change your [service] appointment?<\/p>\n<p>Hi [First name],<\/p>\n<p>If you cannot make your [date] appointment, please use [reschedule path] or reply with a preferred day. We would rather help you find a workable time than have you worry about missing the visit. [Business-specific notice] applies, so contact us as soon as you know.<\/p>\n<h2>When to send a reminder<\/h2>\n<p>Timing depends on how far ahead customers book, how much preparation a visit needs, and how easy it is to fill a cancelled slot. A simple schedule to test is:<\/p>\n<figure class=\"wp-block-image size-full in-content-visual\"><img decoding=\"async\" src=\"https:\/\/messengerbot.app\/wp-content\/uploads\/2026\/09\/reminder-checklist.png\" alt=\"Appointment reminder checklist for time, location, confirmation, and help\" title=\"\"><\/figure>\n<table>\n<thead>\n<tr>\n<th>Moment<\/th>\n<th>Purpose<\/th>\n<th>Best message focus<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Immediately after booking<\/td>\n<td>Set expectations<\/td>\n<td>Details, location, change path, and what happens next<\/td>\n<\/tr>\n<tr>\n<td>Two to three days before<\/td>\n<td>Catch calendar mistakes<\/td>\n<td>Confirm the time and invite a change before the slot is close<\/td>\n<\/tr>\n<tr>\n<td>The day before<\/td>\n<td>Reduce forgotten appointments<\/td>\n<td>Short recap, arrival time, preparation, and reply route<\/td>\n<\/tr>\n<tr>\n<td>The day of<\/td>\n<td>Remove last-minute friction<\/td>\n<td>Directions, meeting link, parking, or a concise check-in instruction<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Do not send every reminder through every channel by default. Ask what the customer agreed to receive, honor opt-outs, and make the frequency easy to understand. Test the schedule with a small internal group before applying it to all appointments.<\/p>\n<h2>How to write reminders for different businesses<\/h2>\n<h3>Salons, spas, and independent professionals<\/h3>\n<p>Include the service, provider, start time, address, parking or arrival note, and the easiest way to reschedule. A customer may have several services in one visit, so \u201cyour appointment\u201d can be too vague. Keep the tone warm, but do not bury the time under personality copy.<\/p>\n<h3>Clinics and dental practices<\/h3>\n<p>Use the wording and privacy practices required by your organization and jurisdiction. Limit the message to the appointment logistics. Do not put diagnoses, treatment details, or sensitive health information in a general reminder channel. Give patients a direct route to the office when a change requires staff help.<\/p>\n<h3>Home services<\/h3>\n<p>Customers care about the arrival window, address, preparation, and what to do if the technician cannot access the property. State the window exactly as it appears in the booking record. If the team will call before arrival, say that only when the process is reliable.<\/p>\n<h3>Consultants and agencies<\/h3>\n<p>Explain who will attend, the meeting format, the intended outcome, and any short pre-read. Avoid promises about a deliverable that has not been agreed. A useful reminder helps the customer arrive prepared without turning the email into a sales pitch.<\/p>\n<h2>Confirmation, rescheduling, and no-response workflows<\/h2>\n<p>A reminder is only as helpful as the action behind it. Decide what each response means before you write the copy:<\/p>\n<ul>\n<li><strong>Confirmed:<\/strong> mark the appointment as confirmed and stop duplicate nudges for that channel.<\/li>\n<li><strong>Needs a change:<\/strong> offer the next safe scheduling step, not a vague \u201cwe will get back to you.\u201d<\/li>\n<li><strong>Unclear reply:<\/strong> route it to a person or a bounded help flow; do not guess what the customer meant.<\/li>\n<li><strong>No response:<\/strong> send only the follow-up your consent and policy allow, then provide a human contact path.<\/li>\n<li><strong>Opt-out:<\/strong> record the preference and suppress future reminders in that channel.<\/li>\n<\/ul>\n<p>Keep an audit trail of the appointment state and the customer\u2019s response without exposing private identifiers in reports or exported examples. Teams should be able to answer \u201cwhat is booked, what changed, and who needs help?\u201d without searching through raw message bodies.<\/p>\n<h2>Make the templates sound human<\/h2>\n<p>Start with the customer\u2019s next decision, then remove anything that does not help them make it. Replace \u201cThis is an automated notification regarding your upcoming appointment\u201d with \u201cYour dental cleaning is tomorrow at 10:00 a.m.\u201d Replace \u201cPlease be advised that changes may be subject to policy\u201d with the actual change instruction and a contact route.<\/p>\n<p>Use the customer\u2019s first name only when the field is trustworthy. If the name is missing or malformed, fall back to a neutral greeting. Keep dates and times in a format the audience recognizes, and spell out the time zone when a remote appointment could cross regions.<\/p>\n<p>Read the message on a small phone. Links should be recognizable, buttons should describe the action, and the key appointment details should remain visible before a long signature. The <a href=\"\/messenger-bot-tutorials\/\">Browse Our Tutorials<\/a> area can help your team map reminder copy to the rest of a conversation workflow. If you are evaluating automation for customer conversations, review <a href=\"\/messenger-bot-pro\/\">Upgrade to Pro<\/a> only after confirming the current feature and plan details.<\/p>\n<h2>Measure the workflow without guessing<\/h2>\n<p>Track the operational outcomes that your booking system can actually verify:<\/p>\n<ul>\n<li>delivery or send status by channel;<\/li>\n<li>confirmed, rescheduled, cancelled, and unanswered appointments;<\/li>\n<li>time between a reminder and a response;<\/li>\n<li>staff follow-ups created by unclear replies;<\/li>\n<li>no-show counts using one consistent definition.<\/li>\n<\/ul>\n<p>Compare like with like. A holiday week, a new booking source, a staffing change, or a seasonal appointment mix can move the numbers even when the reminder copy stays the same. Test one change at a time, such as the send window or the first sentence, and keep the original version available for rollback.<\/p>\n<p>Do not promise that a reminder will prevent every no-show. The copy can make the appointment easier to remember and easier to change; it cannot control a customer\u2019s circumstances.<\/p>\n<h2>Adapt one template without losing the essentials<\/h2>\n<p>Start with the smallest complete version, then make one controlled edit for the audience. For a first visit, explain where to go and what to bring. For a repeat appointment, the customer may need only the service, time, and change path. For a remote call, the meeting instructions matter more than a street address. The message should feel specific without becoming a data dump.<\/p>\n<p>Keep the appointment time in one consistent format across booking, reminder, and calendar records. If a booking system converts time zones, check the rendered message with a test record from a different region. A one-hour error is more damaging than a less clever subject line. If the appointment is a window rather than a fixed time, label it as a window and explain how the customer will receive the arrival update.<\/p>\n<p>Use conditional blocks only when the underlying data is reliable. If a provider name is optional, hide the entire \u201cwith [provider]\u201d phrase when the field is empty. If a preparation item is not relevant to every service, show it only for the correct appointment type. Never leave brackets or internal field names in a customer message. A pre-send preview with a test record catches these errors quickly.<\/p>\n<p>Keep cancellation language factual and respectful. State the notice period or fee only when the current policy supports it, and provide a route to ask for help. Do not threaten a customer for missing an appointment or suggest that a reminder creates a payment obligation that was not already disclosed. A calm change path is more useful than pressure.<\/p>\n<h2>Accessibility and privacy checks<\/h2>\n<p>Write dates in a format that is hard to misread, especially when the audience spans countries. \u201cSeptember 24 at 2:00 p.m. Pacific Time\u201d is clearer than \u201c09\/24 at 2.\u201d Avoid relying on emoji or color to communicate a required action. In email, make links descriptive and ensure the same action is available without an image loading.<\/p>\n<p>Keep the content necessary for logistics. Do not place a full customer profile, payment detail, health detail, or private note in a general reminder. If staff need a richer record, keep that detail in the protected booking workspace and give the customer a support route that does not expose it. Review who can see delivery logs and exports, too; a secure template can still create risk if the reporting view is too broad.<\/p>\n<p>Offer a human route for accessibility requests, language needs, and unusual scheduling situations. A keyword such as \u201cHELP\u201d is useful only if it reaches a monitored team or a tested handoff. Test the route after business hours and during staff coverage changes so the message does not promise a response that nobody can provide.<\/p>\n<h2>Build a small, reversible reminder program<\/h2>\n<p>Document the default sequence in one place: the trigger, delay, channel, template version, response mapping, opt-out behavior, and owner for exceptions. Give each template a plain-language name such as \u201cday-before clinic visit\u201d instead of an internal database label. When the copy changes, record what changed and keep the prior version available until the new one has passed a real test.<\/p>\n<p>Run a test appointment through the full path before enabling a new reminder. Check the booking record, rendered text, link destination, reply handling, staff alert, and cancellation state. Test an empty optional field and a time-zone difference as well as the happy path. Confirm that the workflow does not send a duplicate when a customer reschedules or confirms more than once.<\/p>\n<p>Review the first small cohort manually. Look for wrong times, missing locations, unhelpful replies, repeated nudges, and customers who asked for a person but received another automated message. Fix the data or workflow before increasing volume. This makes the program easier to roll back and gives the team a clear explanation when a customer asks what happened.<\/p>\n<p>Use the same discipline for automation that you use for manual reminders: clear ownership, a tested escalation route, and a safe stop. If a booking integration changes, pause the affected template until a test record confirms that the required fields still map correctly. A reminder program earns trust through predictable details, not through the number of messages it sends.<\/p>\n<p>Keep a short change log beside the templates. Record the date, the audience, the reason for the edit, and the test record used. That small habit helps a new team member understand why a field is present and makes it easier to compare performance without mixing different versions. It also gives you a clean rollback point when seasonal hours, locations, or booking rules change.<\/p>\n<h2>Appointment reminder checklist<\/h2>\n<ol>\n<li>Confirm the appointment record has the correct customer, service, date, time, and time zone.<\/li>\n<li>Choose the channel the customer agreed to receive.<\/li>\n<li>Put the next action in one clear sentence.<\/li>\n<li>Use a monitored reply, phone, or rescheduling path.<\/li>\n<li>Remove sensitive details that are not needed for logistics.<\/li>\n<li>Test links, dates, merge fields, and opt-out handling.<\/li>\n<li>Preview the message on a narrow phone screen.<\/li>\n<li>Record the result and keep a reversible copy of the template.<\/li>\n<\/ol>\n<p>For more customer-conversation setup ideas, you can <a href=\"\/pricing\/\">Check Current Pricing<\/a> after reviewing the workflow requirements and the current plan details. Start with the smallest useful reminder sequence, then expand only when the response data shows that customers need another step.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>What should an appointment reminder say?<\/h3>\n<p>It should name the business and service, state the date and time with the relevant time zone, give the location or meeting instruction, and explain how to confirm, reschedule, or get help.<\/p>\n<h3>Should an appointment reminder be a text or an email?<\/h3>\n<p>Use the channel the customer agreed to receive and the one your team can monitor. Text is compact and timely; email is better for longer directions, preparation, and calendar information. Do not add a second channel simply because it is available.<\/p>\n<h3>How far in advance should I send a reminder?<\/h3>\n<p>Many businesses test an immediate confirmation, a day-before reminder, and an optional same-day logistics note. The right schedule depends on booking lead time, preparation, and how quickly a cancelled slot can be filled, so measure your own workflow and adjust one interval at a time.<\/p>\n<h3>What if a customer does not reply?<\/h3>\n<p>Follow the consent and contact policy you already use, then provide a clear human route. A no-response state should not be treated as confirmation, and the reminder should not claim that a reply was received when it was not.<\/p>\n<h3>Can I automate appointment reminders?<\/h3>\n<p>You can automate parts of the workflow when the booking data, consent, reply handling, and escalation path are tested. Keep a human review option for unclear or sensitive requests, and verify the current capabilities of any automation tool before promising a specific channel or action.<\/p>\n<p>  <script type=\"application\/ld+json\">\n  {\n    \"@context\": \"https:\/\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n      {\"@type\":\"Question\",\"name\":\"What should an appointment reminder say?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It should name the business and service, state the date and time with the relevant time zone, give the location or meeting instruction, and explain how to confirm, reschedule, or get help.\"}},\n      {\"@type\":\"Question\",\"name\":\"Should an appointment reminder be a text or an email?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use the channel the customer agreed to receive and the one your team can monitor. Text is compact and timely; email is better for longer directions, preparation, and calendar information. Do not add a second channel simply because it is available.\"}},\n      {\"@type\":\"Question\",\"name\":\"How far in advance should I send a reminder?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Many businesses test an immediate confirmation, a day-before reminder, and an optional same-day logistics note. The right schedule depends on booking lead time, preparation, and how quickly a cancelled slot can be filled, so measure your own workflow and adjust one interval at a time.\"}},\n      {\"@type\":\"Question\",\"name\":\"What if a customer does not reply?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Follow the consent and contact policy you already use, then provide a clear human route. A no-response state should not be treated as confirmation, and the reminder should not claim that a reply was received when it was not.\"}},\n      {\"@type\":\"Question\",\"name\":\"Can I automate appointment reminders?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"You can automate parts of the workflow when the booking data, consent, reply handling, and escalation path are tested. Keep a human review option for unclear or sensitive requests, and verify the current capabilities of any automation tool before promising a specific channel or action.\"}}\n    ]\n  }\n  <\/script><\/p>\n<h2>Source notes<\/h2>\n<p>This draft uses the current template and notification guidance from <a href=\"https:\/\/acuityscheduling.com\/learn\/appointment-reminder-templates\" rel=\"nofollow noopener\" target=\"_blank\">Acuity\u2019s reminder guide<\/a>, <a href=\"https:\/\/appointmentreminder.com\/resources\/email-reminder-templates\/\" rel=\"nofollow noopener\" target=\"_blank\">AppointmentReminder\u2019s email examples<\/a>, <a href=\"https:\/\/bookedin.com\/blog\/appointment-reminder-templates-service-business\/\" rel=\"nofollow noopener\" target=\"_blank\">BookedIN\u2019s service-business templates<\/a>, and <a href=\"https:\/\/calendly.com\/help\/calendly-scheduling-notifications\" rel=\"nofollow noopener\" target=\"_blank\">Calendly\u2019s notification documentation<\/a>. Check each source and your own policy again at publication time because scheduling interfaces and consent requirements can change.<\/p>\n","protected":false},"excerpt":{"rendered":"<input type=\"hidden\" value=\"\" data-essbisPostContainer=\"\" data-essbisPostUrl=\"https:\/\/messengerbot.app\/ja\/appointment-reminder-templates\/\" data-essbisPostTitle=\"Appointment Reminder Templates: Text and Email Examples\" data-essbisHoverContainer=\"\"><p>Updated September 2026 &mdash; A reminder should make the next step obvious without making the customer hunt for the date, time, location, or reply option. This guide gives you ready-to-edit appointment reminder templates for text messages and email, then shows how to choose timing, handle confirmations, and recover gracefully when someone does not respond. Use the examples as starting points, not as a reason to send the same sentence to every customer. A salon appointment, a dental visit, a consultation, and a video call each need different details. Keep the useful structure, replace the placeholders, and check your consent and channel rules before sending. What a useful appointment reminder includes [&hellip;]<\/p>\n","protected":false},"author":14928,"featured_media":263738,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":"","rank_math_title":"Appointment Reminder Templates: Text + Email Examples","rank_math_description":"Copy appointment reminder templates for text and email, with timing, consent, confirmations, and practical edits for service businesses.","rank_math_focus_keyword":"appointment reminder template","rank_math_canonical_url":"","rank_math_robots":"","rank_math_facebook_title":"","rank_math_facebook_description":"","rank_math_twitter_title":"","rank_math_twitter_description":""},"categories":[31],"tags":[],"class_list":["post-263741","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/posts\/263741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/users\/14928"}],"replies":[{"embeddable":true,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/comments?post=263741"}],"version-history":[{"count":3,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/posts\/263741\/revisions"}],"predecessor-version":[{"id":263749,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/posts\/263741\/revisions\/263749"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/media\/263738"}],"wp:attachment":[{"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/media?parent=263741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/categories?post=263741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/messengerbot.app\/ja\/wp-json\/wp\/v2\/tags?post=263741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}