{"id":3864,"date":"2024-04-17T10:21:56","date_gmt":"2024-04-17T10:21:56","guid":{"rendered":"https:\/\/www.warmy.io\/blog\/how-to-fix-smtp-email-error-535-5-7-3-solved\/"},"modified":"2026-06-17T12:50:27","modified_gmt":"2026-06-17T12:50:27","slug":"how-to-fix-smtp-email-error-535-5-7-3-solved","status":"publish","type":"post","link":"https:\/\/www.warmy.io\/blog\/how-to-fix-smtp-email-error-535-5-7-3-solved\/","title":{"rendered":"SMTP Error 535 5.7.3: Authentication Failed \u2014 Causes and How to Fix It"},"content":{"rendered":"\n<p>SMTP Error 535 5.7.3 means your email server rejected the outgoing message because it could not verify your identity. The fix is almost always one of three things: wrong credentials, misconfigured SMTP settings, or a security policy change on your email provider\u2019s end. In most cases, updating your password in the email client, using the correct SMTP port (587 with STARTTLS), and switching to an App Password or OAuth token resolves the issue within minutes.<\/p>\n\n\n\n<p>This error is one of the most common <a href=\"https:\/\/www.warmy.io\/blog\/smtp-error-codes-and-messages\/\" target=\"_blank\" rel=\"noopener noreferrer\">SMTP authentication failures<\/a> affecting Gmail, Outlook, Yahoo, and custom SMTP setups alike. It blocks outgoing email entirely\u2014disrupting campaigns, client communication, and automated workflows. Left unresolved, it can also damage your sender reputation over time.<\/p>\n\n\n\n<p>This guide walks you through every root cause and the exact steps to fix SMTP Error 535 5.7.3 for Gmail, Outlook, Yahoo, and other providers\u2014plus what to do after the fix to protect your deliverability long-term.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is SMTP 535 5.7.3?<\/h2>\n\n\n\n<p>While email functions over many general protocols, the vast majority of sending and receiving email across servers falls under the <a href=\"https:\/\/www.warmy.io\/blog\/what-is-smtp-and-how-does-the-smtp-server-work\/\" target=\"_blank\" rel=\"noopener noreferrer\">Simple Mail Transfer Protocol (SMTP).<\/a>&nbsp;<\/p>\n\n\n\n<p><strong>SMTP<\/strong><strong> Error 535 5.7.3 means your email wasn\u2019t sent because the server can\u2019t authenticate the sender.<\/strong><\/p>\n\n\n\n<p>While the error notification message differs from program to program, the general message is similar to \u201cInvalid Authentication Credential\u201d or \u201cAuthentication Failed.\u201d<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For example, Microsoft Outlook says \u201cError 535 5.7.3 Authentication unsuccessful,\u201d<\/li>\n\n\n\n<li>Apple Mail says, \u201cCannot send mail. The username or password for [SMTP server] is incorrect.\u201d\u00a0<\/li>\n<\/ul>\n\n\n\n<p><em>Q: What is authentication?<\/em><\/p>\n\n\n\n<p><em>A: Authentication is a form of security verification that guarantees a user has permission to send through the specific mail server.<\/em> <em>So when the email program on the host machine creates these necessary credentials for authentication and the server denies them, an error is generated.<\/em><\/p>\n\n\n\n<p><strong>\ud83d\udd16 Related Reading:<\/strong> <a href=\"https:\/\/www.warmy.io\/blog\/understanding-and-fixing-the-smtp-535-error-incorrect-authentication-data\" target=\"_blank\" rel=\"noopener\">Understanding and Fixing the SMTP 535 Error: Incorrect Authentication Data<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying causes of SMTP error 535 5.7.3<\/h2>\n\n\n\n<p>Primarily, SMTP Error 535 5.7.3 occurs when there are issues with the authentication process of the server required to send emails.<\/p>\n\n\n\n<p>Below are some possible causes that could lead to error 535 5.7.3.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Using invalid or outdated credentials<\/h3>\n\n\n\n<p>This implies that there is something wrong with the password and ID. Possible causes include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some sort of typographical error<\/li>\n\n\n\n<li>A password change has not propagated yet through the email client<\/li>\n\n\n\n<li>The email user used to have access but does not have access anymore<\/li>\n\n\n\n<li>The old credentials do not comply with the new server security settings<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Misconfiguration of server-port configurations<\/h3>\n\n\n\n<p>Another reason for server authentication errors is misconfiguration. For instance, what the email client configured doesn\u2019t match what\u2019s really valid.<\/p>\n\n\n\n<p>Since the SMTP server needs proper authentication, this fails because the server-port configurations are wrong.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Publisher security update<\/h3>\n\n\n\n<p>This means something changed on the publisher\/email service provider\u2019s end in terms of security settings or the authentication it offers.<\/p>\n\n\n\n<p>Should the email recipient fail to follow what\u2019s been published\u2014meaning, if it stays at a less secure authentication when the more secure authentication is now required\u2014this is the response it receives for noncompliance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Account lockout phenomenon<\/h3>\n\n\n\n<p>The email host server might lock the accounts if it registers suspicious activities or when a breach has occurred.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Software condlicts<\/h3>\n\n\n\n<p>The email client installed uses outdated software that no longer complies with the server\u2019s required settings.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A step-by-step guide to resolving SMTP email error 535 5.7.3<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">For Gmail users<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Verify password and username.<\/strong>\u00a0Verify that the username and password in your email client are current and accurate. Update your Gmail password in your email client as well, if you\u2019ve changed it recently.<\/li>\n\n\n\n<li>Use an App Password or OAuth 2.0. Google permanently removed the \u201cLess Secure Apps\u201d option in 2025. If you use 2-Step Verification (which Google now requires), you must generate a 16-character App Password at myaccount.google.com\/apppasswords and enter it in place of your regular password. Alternatively, use an email client that supports <a href=\"https:\/\/oauth.net\/2\/\" rel=\"noopener\" target=\"_blank\" rel=\"noopener noreferrer\">OAuth 2.0<\/a> to avoid this issue entirely.<\/li>\n\n\n\n<li><strong>Verify SMTP settings:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>SMTP Server:<\/strong> smtp.gmail.com<\/li>\n\n\n\n<li><strong>Port:<\/strong> 587 for TLS\/SSL<\/li>\n\n\n\n<li><strong>Authentication required:<\/strong> Yes<\/li>\n\n\n\n<li><strong>Username:<\/strong> Your full Gmail address<\/li>\n\n\n\n<li><strong>Password:<\/strong> Your Gmail password<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">For Outlook users<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Update password.<\/strong>\u00a0Ensure your password is correct, especially if you have recently changed it.<\/li>\n\n\n\n<li><strong>Check SMTP Settings:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>SMTP Server:<\/strong> smtp-mail.outlook.com<\/li>\n\n\n\n<li><strong>Port:<\/strong> 587<\/li>\n\n\n\n<li><strong>Encryption Method:<\/strong> STARTTLS<\/li>\n\n\n\n<li><strong>Authentication Required:<\/strong> Yes<\/li>\n\n\n\n<li><strong>Username:<\/strong> Your full Outlook email address<\/li>\n\n\n\n<li><strong>Password:<\/strong> Your Outlook password<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">For Yahoo Mail users<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Password verification.<\/strong>\u00a0Confirm that the password and username are correctly entered in your email client.<\/li>\n\n\n\n<li><strong>Adjust SMTP settings:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>SMTP Server:<\/strong> smtp.mail.yahoo.com<\/li>\n\n\n\n<li><strong>Port:<\/strong> 587<\/li>\n\n\n\n<li><strong>Encryption Method:<\/strong> STARTTLS<\/li>\n\n\n\n<li><strong>Authentication Required:<\/strong> Yes<\/li>\n\n\n\n<li><strong>Username:<\/strong> Your full Yahoo email address<\/li>\n\n\n\n<li><strong>Password:<\/strong> Your Yahoo password<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">For other email services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Confirm authentication details. <\/strong>Double-check your username and password. Reset your password if unsure and update the new password in the email client.<\/li>\n\n\n\n<li><strong>Correct SMTP settings.<\/strong>\u00a0Refer to your email provider\u2019s help documentation for the correct SMTP server settings, including server address, port, and encryption method.<\/li>\n\n\n\n<li><strong>Contact support.<\/strong>\u00a0If you continue to have issues, contact your email provider\u2019s technical support for guidance on specific settings.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Pro Tips: Prevent SMTP 535 5.7.3 From Coming Back<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udca1 Pro Tip #1: Always use App Passwords for third-party tools<\/h3>\n\n\n\n<p>If you connect your Gmail or Outlook to a CRM, email automation tool, or warmup platform, never use your main account password. Generate a dedicated App Password for each third-party connection. This keeps your primary login secure and prevents authentication errors when you change your main password.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udca1 Pro Tip #2: Validate your SPF, DKIM, and DMARC before sending at scale<\/h3>\n\n\n\n<p>SMTP Error 535 5.7.3 is a login-level error, but it often surfaces alongside deeper deliverability problems. Before scaling your sending volume, verify that your SPF record authorizes your sending server, DKIM signatures are properly configured, and your DMARC policy is set to at least \u201cp=none\u201d to begin monitoring. Warmy.io\u2019s free SPF Record Generator and DMARC Record Generator tools can help you set these up correctly in minutes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udca1 Pro Tip #3: Run a deliverability test after every major configuration change<\/h3>\n\n\n\n<p>Whenever you change your SMTP settings, update credentials, or migrate to a new sending infrastructure, send a test through Warmy.io\u2019s free Email Deliverability Test. It checks inbox placement across Gmail, Outlook, and Yahoo simultaneously, verifies your authentication records, and flags blacklist issues\u2014giving you confirmation that the fix actually worked before you resume regular sending.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"965\" height=\"643\" src=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts.png\" alt=\"warmy experts\" class=\"wp-image-6923\" title=\"\" srcset=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts.png 965w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts-300x200.png 300w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts-768x512.png 768w\" sizes=\"auto, (max-width: 965px) 100vw, 965px\" \/><\/figure>\n\n\n\n<p>\ud83d\udea8 Still struggling with SMTP errors or landing in spam? Warmy.io\u2019s dedicated deliverability experts work with you one-on-one to identify what\u2019s blocking your emails and build a lasting fix. <a href=\"https:\/\/www.warmy.io\/book-a-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book a free demo<\/a> and get personalized guidance from an expert today.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Enhancing email deliverability with Warmy.io<\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/warmy-blog-wordpress-bucket.s3.amazonaws.com\/wp-content\/uploads\/2024\/03\/11092751\/525shots_so.png\" alt=\"525shots so\" title=\"\"><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>SMTP Email Error 535 5.7.3 workarounds may be challenging however, Warmy.io can help.<\/p>\n\n\n\n<p>Fixing SMTP Error 535 5.7.3 resolves the immediate authentication block\u2014but it doesn\u2019t protect you from landing in spam once emails start flowing again. Deliverability depends on sender reputation, authentication records, warmup history, and more. Warmy.io addresses all of these with a suite of tools built specifically for email senders who need reliable inbox placement.<\/p>\n\n\n\n<p>Warmy is the only email warmup platform with a dedicated AI\u2014<a href=\"https:\/\/www.warmy.io\/product\/ai\" target=\"_blank\" rel=\"noopener noreferrer\">Adeline AI<\/a>\u2014built exclusively to optimize your email deliverability. It analyzes your sending patterns, adjusts warmup settings in real time, and helps prevent the kind of reputation damage that causes authentication rejections and spam placement in the first place.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">AI-driven email warmup to prevent server rejections and spam flags<\/h3>\n\n\n\n<p>Warmy.io helps improve your sending reputation which is currently based on the performance and history of all emails you\u2019ve ever sent. Essentially, Warmy helps you be seen as a legitimate sender by various email servers so your future emails will land in inboxes\u2014and not the spam folder.&nbsp;<\/p>\n\n\n\n<p>Warmy.io\u2019s AI-powered email warmup helps your deliverability through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Gradually increasing email volume to prevent sudden spikes that could trigger mail server rejections.<\/li>\n\n\n\n<li>Simulating human-like interactions\u00a0 to ensure emails are opened, replied to, and marked as important.<\/li>\n\n\n\n<li>Monitoring email reputation to identify potential issues before they impact campaigns.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/warmy-blog-wordpress-bucket.s3.amazonaws.com\/wp-content\/uploads\/2025\/03\/11093354\/8shots_so.webp\" alt=\"Graph showing email warmup performance with a line chart. The x-axis represents dates from June 1 to June 9, and the y-axis represents email volume. Two lines indicate sent (1,200) and received (1,100) emails. Background is a soft gradient.\" title=\"\"><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free email deliverability test for diagnosing issues<\/h3>\n\n\n\n<p>Warmy.io\u2019s free <a href=\"https:\/\/www.warmy.io\/free-tools\/email-deliverability-test\" target=\"_blank\" rel=\"noopener noreferrer\">Email Deliverability Test<\/a> helps identify technical and reputation-based issues before they impact your campaigns. The test gives a comprehensive report of the percentage of your emails landing in the inbox, promotions, spam\u2014and even the unreceived ones.<\/p>\n\n\n\n<p>It also reveals if your domain or IP is included in any blacklists\u2014yet another major factor that affects deliverability.<\/p>\n\n\n\n<p><em>Q: What are blacklists and how do these impact deliverability?<\/em><\/p>\n\n\n\n<p><em>A: <\/em><em>Blacklists are databases that track IP addresses or domains known for sending spam or engaging in suspicious email behavior. Being blacklisted can lead to emails being blocked, sent to spam, or throttled.<\/em><\/p>\n\n\n\n<p><strong>\ud83d\udd16 Related Reading: <\/strong><a href=\"https:\/\/www.warmy.io\/blog\/are-blacklists-killing-your-emails-a-deep-dive-into-how-they-influence-email-providers\" target=\"_blank\" rel=\"noopener noreferrer\">Are Blacklists Killing Your Emails? A Deep Dive into How They Influence Email Providers<\/a><\/p>\n\n\n\n<p>The test also checks your email authentication settings<a href=\"https:\/\/www.warmy.io\/blog\/why-do-you-need-to-configure-spf-dkim-and-dmarc\" target=\"_blank\" rel=\"noopener noreferrer\"> (SPF, DKIM, and DMARC)<\/a> if they are properly authenticated.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe title=\"The Complete Tool For Email Deliverability: Meet Warmy.io!\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/jFXzuA-F-Nc?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Additional warmup preferences to maximize inbox placement<\/h3>\n\n\n\n<p>Warmup Preferences helps senders have full control over the warmup process from both sender and user levels.&nbsp;<\/p>\n\n\n\n<p>Warmy offers the most advanced warmup customization on the market. Unlike competitors that only let you control sending schedules, Warmy gives you granular control over:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Distribution across providers (Gmail, Outlook, Yahoo, and more) so warmup activity matches your actual recipient mix<\/li>\n\n\n\n<li>Topic selection for warmup emails\u2014a feature most competitors do not offer at all<\/li>\n\n\n\n<li>Multiple language options for warmup emails\u2014rare among warmup tools<\/li>\n\n\n\n<li>B2B or B2C engagement pattern selection, spintax on user templates, and temperature settings\u2014giving you the most precise control over how your warmup activity looks to email providers<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/warmy-blog-wordpress-bucket.s3.amazonaws.com\/wp-content\/uploads\/2025\/03\/11092845\/290shots_so-copy-1-1024x768.png\" alt=\"A dashboard displaying a profile section with a circular chart titled WARM-UP PREFERENCES. The chart shows percentages for Gmail, Outlook, G-Suite, Yahoo, and others. A table beneath lists specific percentages and email services.\" title=\"\"><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Advanced seed list ensures strong inbox placement<\/h3>\n\n\n\n<p>Other traditional warmup lists can only simulate opening of emails, but <a href=\"https:\/\/www.warmy.io\/product\/seed-list\" target=\"_blank\" rel=\"noopener noreferrer\">Warmy\u2019s advanced seed lists<\/a> offer actual engagement.<\/p>\n\n\n\n<p>What does this look like? Your emails are opened, scrolled through, clicked on, and replied to. If there are emails that land in spam, these are removed and marked as important to let the ESPs know you are credible.<\/p>\n\n\n\n<p>It can also be integrated into any email client to improve your email performance testing. Warmy will supply genuine email addresses from Google, Outlook, and Yahoo that will act as seeds for testing and improving your email deliverability.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Leverage Warmy.io to transform your email game<\/h2>\n\n\n\n<p>The need for troubleshooting SMTP Error 535 5.7.3 is essential.<\/p>\n\n\n\n<p>After all, this error prevents you from being able to send emails\u2014which jeopardizes customer relationships, fails to impress potential business connections, and puts one\u2019s professional reputation at risk.<\/p>\n\n\n\n<p>Therefore, troubleshooting this issue and understanding proper configurations of the email settings is necessary.&nbsp;<\/p>\n\n\n\n<p><strong>However, configurations are just one part of the email deliverability landscape. <\/strong>There are many other factors that impact your deliverability and simply focusing on resolving SMTP Error 535 5.7.3 will not automatically get rid of your deliverability issues.<\/p>\n\n\n\n<p>Thankfully, Warmy provides tools and strategies that can cover deliverability as a whole.<\/p>\n\n\n\n<p><a href=\"https:\/\/www.warmy.io\/book-a-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book a demo<\/a> with an expert today and see how it can transform your email deliverability and business.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe title=\"How to Set Up SPF, DKIM, and DMARC for Gmail in 2026 (google workspace)\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/bXxcDJa84uA?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<p>\ud83d\udcdc <strong>Related articles<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.warmy.io\/blog\/understanding-and-fixing-the-smtp-535-error-incorrect-authentication-data\" target=\"_blank\" rel=\"noopener\">Google Error 535-5.7.8: Username and Password Not Accepted<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.warmy.io\/blog\/how-to-fix-smtp-email-error-535-5-7-3-solved\/\" target=\"_blank\" rel=\"noopener\">SMTP Email Error 535 5.7.3 \u2013 How to Resolve [SOLVED]<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.warmy.io\/blog\/free-email-spam-checker-guide\/\" target=\"_blank\" rel=\"noopener\">How to Use Free Spam Checker to Improve Email Deliverability<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>SMTP Error 535 5.7.3 means your email server rejected the outgoing message because it could not verify your identity. The fix is almost always one of three things: wrong credentials, misconfigured SMTP settings, or a security policy change on your email provider\u2019s end. In most cases, updating your password in the email client, using the [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":7242,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[104],"tags":[],"class_list":["post-3864","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-deliverability"],"acf":[],"lang":"en","translations":{"en":3864},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3864","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/comments?post=3864"}],"version-history":[{"count":6,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3864\/revisions"}],"predecessor-version":[{"id":7258,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3864\/revisions\/7258"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/media\/7242"}],"wp:attachment":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/media?parent=3864"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/categories?post=3864"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/tags?post=3864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}