{"id":3583,"date":"2026-08-14T03:00:00","date_gmt":"2026-08-14T03:00:00","guid":{"rendered":"https:\/\/xinya-ee.com\/blog\/commercial-ev-charger-service-sla-rfq\/"},"modified":"2026-10-23T09:39:41","modified_gmt":"2026-10-23T01:39:41","slug":"servicio-de-carga-comercial-ev-sla-rqf","status":"publish","type":"post","link":"https:\/\/xinya-ee.com\/es\/blog\/commercial-ev-charger-service-sla-rfq\/","title":{"rendered":"SLA de servicio de cargadores comerciales de veh\u00edculos el\u00e9ctricos: alcance y escalamiento de preguntas"},"content":{"rendered":"<article>\n<p style=\"margin:0 0 16px;line-height:1.7\">A <strong>commercial EV charging SLA<\/strong> becomes useful only when it defines the event, severity, clock, evidence, and exclusions. A broad uptime phrase cannot tell an operator who responds, when the timer starts, what is measured, or how planned work is treated.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/03\/7kw-ev-charger-1.webp\" alt=\"XYDF AC charging equipment shown as commercial service-planning context\" loading=\"eager\" width=\"2732\" height=\"1534\" fetchpriority=\"high\"><figcaption>Equipment context only; service terms and performance require a project or contract review.<\/figcaption><\/figure>\n<nav class=\"b2b-toc\" style=\"background:#f5f8fa;padding:16px 20px;border-radius:8px;margin:0 0 24px\">\n<h2 id=\"contents\" style=\"margin:42px 0 14px;scroll-margin-top:96px\">Contents<\/h2>\n<ul style=\"content-visibility: auto;contain-intrinsic-size: auto 262px;margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"#part-1-why-should-an-operator-define-sla-scope-first\">Part 1. Why should an operator define SLA scope first?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-2-how-should-incidents-be-prioritized\">Part 2. How should incidents be prioritized?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-3-what-should-response-and-resolution-targets-say\">Part 3. What should response and resolution targets say?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-4-what-should-uptime-include-and-exclude\">Part 4. What should uptime include and exclude?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-5-how-should-planned-work-be-handled\">Part 5. How should planned work be handled?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-6-which-evidence-should-an-operator-request\">Part 6. Which evidence should an operator request?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-7-what-should-be-in-an-sla-rfq\">Part 7. What should be in an SLA RFQ?<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-1-why-should-an-operator-define-sla-scope-first\">Part 1. Why should an operator define SLA scope first?<\/h2>\n<p>Reliability should be described as observable operating evidence rather than a single marketing number. Ask for failure-mode definitions, session availability, alarm history, response and restoration records, inspection intervals, spare-parts coverage, and the conditions under which the evidence was collected. MTBF or a rated power figure can be part of the review, but neither replaces a clear failure-recovery and maintenance process. For the public planning context, see <a href=\"https:\/\/webstore.iec.ch\/en\/publication\/33644\" rel=\"noopener noreferrer\" target=\"_blank\">IEC 61851-1 conductive charging system requirements<\/a>; the site-specific acceptance record still controls the final decision.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">An SLA can cover equipment, software, communications, site access, field service, parts, or some combination. Write the scope before discussing a target; otherwise two parties may use the same word for different service boundaries.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">The scope should identify the asset, location, service hours, supported interfaces, reporting channel, and the party responsible for each step. A product page cannot substitute for the commercial service document.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-2-how-should-incidents-be-prioritized\">Part 2. How should incidents be prioritized?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use a severity model that reflects operational impact and safety. A complete outage, a single connector issue, a communication alarm, and a cosmetic defect should not automatically start the same clock.<\/p>\n<div class=\"scroll\">\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Severity area<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Example question<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Evidence to retain<\/th>\n<\/tr>\n<\/thead>\n<tbody style=\"content-visibility: auto;contain-intrinsic-size: auto 166px;\">\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Safety concern<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Does use stop pending assessment?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Incident record and escalation<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Site-wide outage<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">How many assets or users are affected?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Time range and affected equipment<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Partial degradation<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Is an alternate service available?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Alarm, connector, or session record<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Information issue<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Can operations continue safely?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Ticket and resolution note<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p style=\"margin:0 0 16px;line-height:1.7\">The categories are starting points only. The operator and supplier must agree definitions that fit the site and contract.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-3-what-should-response-and-resolution-targets-say\">Part 3. What should response and resolution targets say?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">For each service clock, define the start event, service hours, access assumptions, evidence source and stopping rule. This lets an operator compare acknowledgement, remote recovery, on-site response and verified restoration without turning one broad uptime number into four different promises.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Separate acknowledgement, first <strong>response clock<\/strong>, diagnosis, workaround, repair, and <strong>resolution clock<\/strong>. Each has a different meaning and may require a different owner. State when the clock starts, which communication channel qualifies, and what evidence closes it.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/04\/22kw-ac-charger-ce-ukca-ul-smart.webp\" alt=\"XYDF AC charger used to illustrate commercial service-scope discussion\" loading=\"lazy\" width=\"1600\" height=\"1600\" fetchpriority=\"low\"><figcaption>Product context only; response and resolution terms must be agreed for the actual service arrangement.<\/figcaption><\/figure>\n<blockquote>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not present a response-time number without defining the event, clock, service hours, access conditions, exclusions, and evidence source. The <a href=\"https:\/\/iaeimagazine.org\/electrical-fundamentals\/electric-vehicle-charging-infrastructure-stations-equipment-and-planning\/\" target=\"_blank\" rel=\"noopener\">IAEI infrastructure-planning article<\/a> supports treating charging as a coordinated project, not an isolated product promise.<\/p>\n<\/blockquote>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-4-what-should-uptime-include-and-exclude\">Part 4. What should uptime include and exclude?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Define the denominator and measurement interval before accepting an <strong>uptime target<\/strong>. Ask whether uptime means a charger is powered, available to start a session, connected to a network, usable by a specified vehicle, or available across a site. These are not interchangeable measures.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Also identify conditions outside the service commitment: utility outage, site access, vehicle fault, communications dependency, planned maintenance, misuse, severe events, or an unapproved change. Exclusions should be explicit rather than hidden in a headline percentage.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For a scoped example, the <a href=\"https:\/\/www.energy.ca.gov\/programs-and-topics\/programs\/clean-transportation-program\/ev-charger-data-and-reliability-1\" target=\"_blank\" rel=\"noopener\">California Energy Commission&#8217;s EV charger reliability rules<\/a> apply, with exceptions, to publicly funded DC fast chargers installed after January 1, 2024, including state, ratepayer, and federal funds administered through a state agency. Covered ports require 97% uptime for six years; being online alone is insufficient: ports must be available and successfully dispense electricity.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">The CEC permits exclusions for grid power loss and natural disasters, but caps vandalism exclusions at ten days per incident and planned maintenance at 72 hours annually. A private SLA can allocate liability; it cannot broaden these regulatory exclusions. An unlimited maintenance exclusion therefore does not satisfy the covered project&#8217;s calculation. Keep the reason, duration, and supporting evidence for each excluded interval. These are jurisdiction-specific rules, not a global uptime definition or an XYDF service commitment.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-5-how-should-planned-work-be-handled\">Part 5. How should planned work be handled?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">The SLA should state how planned maintenance, software changes, inspections, parts replacement, and site access are notified. Include notice period, approval contact, expected impact, rollback or recovery path, and the record supplied afterward.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Planned work is not automatically an incident, but it can still affect operations. The operator needs a shared calendar and a named escalation route when work exceeds the agreed window.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-6-which-evidence-should-an-operator-request\">Part 6. Which evidence should an operator request?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Request evidence that can be compared across incidents and reporting periods: ticket ID, timestamps, severity, affected assets, actions, parts, cause classification, resolution, and any follow-up recommendation. Ask who owns the source data and how corrections are handled. Where an outage involves connected systems, agree <a href=\"https:\/\/xinya-ee.com\/blog\/commercial-ev-charger-cybersecurity-rfq\/\">security-incident evidence and escalation<\/a> with the party responsible for those systems.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">A <a href=\"https:\/\/xinya-ee.com\/blog\/public-ev-charging-station-preventive-maintenance-plan\/\">preventive-maintenance plan<\/a> defines routine work, while <a href=\"https:\/\/xinya-ee.com\/blog\/ev-charger-warranty-terms-b2b-comparison\/\">warranty terms<\/a> define cover and exclusions. The service SLA should state how incident response and restoration are handled alongside those obligations.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-7-what-should-be-in-an-sla-rfq\">Part 7. What should be in an SLA RFQ?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Give suppliers a structured question set so responses can be compared without assuming an outcome.<\/p>\n<div class=\"scroll\">\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Buyer should request or define<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody style=\"content-visibility: auto;contain-intrinsic-size: auto 291px;\">\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Asset and service scope<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Establishes what the SLA covers<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Severity definitions<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Sets the event classification<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Response and resolution clocks<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Makes targets measurable<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Uptime denominator and exclusions<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Prevents incomparable percentages<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Planned-work notice and access rules<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Keeps scheduled work visible<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Evidence and reporting format<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Enables operational review<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Escalation contacts and exceptions<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Defines what happens when normal support fails<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p style=\"margin:0 0 16px;line-height:1.7\">After the service boundary is clear, buyers can review the <a href=\"https:\/\/xinya-ee.com\/dc-fast-charger\/\">DC fast charger range<\/a> and send the requirement through the <a href=\"https:\/\/xinya-ee.com\/contact\/\">contact page<\/a>. This article does not claim any XYDF SLA, uptime, response, resolution, remote-monitoring, field-service, or parts promise.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/05\/dc-charger30-40kw-300x300-1.webp\" alt=\"XYDF DC charger shown for commercial SLA RFQ context\" loading=\"lazy\" width=\"300\" height=\"300\" fetchpriority=\"low\"><figcaption>Equipment context only; commercial service terms require a documented project agreement.<\/figcaption><\/figure>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"frequently-asked-questions\">Frequently asked questions<\/h2>\n<h3 style=\"margin:28px 0 12px\" id=\"what-should-an-ev-charging-sla-include\">What should an EV charging SLA include?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Define asset and service scope, severity, response and resolution clocks, measurement, exclusions, planned work, evidence, contacts, and escalation. A headline uptime number without these fields is incomplete.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"how-are-incidents-prioritized\">How are incidents prioritized?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use agreed severity categories that distinguish safety concerns, site-wide outages, partial degradation, and lower-impact information issues. The operator and supplier should define the actual matrix.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"who-owns-first-response\">Who owns first response?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The contract should name the intake channel and the party responsible for acknowledgement, diagnosis, field coordination, and escalation. Do not infer ownership from a product category.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"does-uptime-include-the-vehicle-or-grid\">Does uptime include the vehicle or grid?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">It depends on the agreed denominator. Buyers should distinguish equipment availability, session start, network connection, vehicle compatibility, and utility availability before accepting a percentage.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"what-records-should-an-operator-request\">What records should an operator request?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Request ticket ID, timestamps, severity, affected assets, actions, parts, cause classification, resolution, and follow-up. Also identify the data owner and correction method.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"how-are-planned-outages-handled\">How are planned outages handled?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Define notice, approval, expected impact, maintenance window, escalation if work runs late, and the completion record. Planned work should be visible even when it is excluded from an incident clock.<\/p>\n<h3 style=\"margin:28px 0 12px\" id=\"what-should-be-in-an-sla-rfq\">What should be in an SLA RFQ?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Include scope, severity, clocks, uptime denominator, exclusions, planned work, reporting, contacts, escalation, site access, and exceptions. Ask the supplier to identify unsupported assumptions.<\/p>\n<h3>What reliability evidence should an EV charger buyer request?<\/h3>\n<p>Request failure-mode definitions, session-availability records, alarm and reset history, response and restoration times, preventive-maintenance intervals, and spare-parts or service coverage for the exact configuration. Compare the evidence by operating condition and measurement period; do not treat an isolated MTBF value or a supplier uptime claim as proof of the site&#8217;s future availability.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"references\">References<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.hse.gov.uk\/electricity\/\" target=\"_blank\" rel=\"noopener\">HSE electricity safety<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/iaeimagazine.org\/electrical-fundamentals\/electric-vehicle-charging-infrastructure-stations-equipment-and-planning\/\" target=\"_blank\" rel=\"noopener\">IAEI article on EV charging infrastructure planning<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.networkrail.co.uk\/wp-content\/uploads\/2023\/11\/NR-GN-CIV-200-13-Electric-Vehicle-Charging-Points-and-Associated-Infrastructure.pdf\" target=\"_blank\" rel=\"noopener\">Network Rail EV infrastructure guidance<\/a><\/li>\n<\/ul>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What should an EV charging SLA include?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Define asset and service scope, severity, response and resolution clocks, measurement, exclusions, planned work, evidence, contacts, and escalation. A headline uptime number without these fields is incomplete.\"}},{\"@type\":\"Question\",\"name\":\"How are incidents prioritized?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use agreed severity categories that distinguish safety concerns, site-wide outages, partial degradation, and lower-impact information issues. The operator and supplier should define the actual matrix.\"}},{\"@type\":\"Question\",\"name\":\"Who owns first response?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The contract should name the intake channel and the party responsible for acknowledgement, diagnosis, field coordination, and escalation. Do not infer ownership from a product category.\"}},{\"@type\":\"Question\",\"name\":\"Does uptime include the vehicle or grid?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It depends on the agreed denominator. Buyers should distinguish equipment availability, session start, network connection, vehicle compatibility, and utility availability before accepting a percentage.\"}},{\"@type\":\"Question\",\"name\":\"What records should an operator request?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Request ticket ID, timestamps, severity, affected assets, actions, parts, cause classification, resolution, and follow-up. Also identify the data owner and correction method.\"}},{\"@type\":\"Question\",\"name\":\"How are planned outages handled?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Define notice, approval, expected impact, maintenance window, escalation if work runs late, and the completion record. Planned work should be visible even when it is excluded from an incident clock.\"}},{\"@type\":\"Question\",\"name\":\"What should be in an SLA RFQ?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Include scope, severity, clocks, uptime denominator, exclusions, planned work, reporting, contacts, escalation, site access, and exceptions. Ask the supplier to identify unsupported assumptions.\"}},{\"@type\":\"Question\",\"name\":\"What reliability evidence should an EV charger buyer request?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Request failure-mode definitions, session-availability records, alarm and reset history, response and restoration times, preventive-maintenance intervals, and spare-parts or service coverage for the exact configuration. Compare the evidence by operating condition and measurement period; do not treat an isolated MTBF value or a supplier uptime claim as proof of the site's future availability.\"}}]}<\/script><br \/>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>Defina un SLA de servicio de cargador EV con plazos de cobertura, gravedad, respuesta y resoluci\u00f3n medibles, factores de disponibilidad, exclusiones, reportes y titularidad de la escalada de incidentes.<\/p>","protected":false},"author":8,"featured_media":1023,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,24],"tags":[],"product-features":[],"class_list":["post-3583","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-newsblog"],"_links":{"self":[{"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/posts\/3583","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/comments?post=3583"}],"version-history":[{"count":5,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/posts\/3583\/revisions"}],"predecessor-version":[{"id":5405,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/posts\/3583\/revisions\/5405"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/media\/1023"}],"wp:attachment":[{"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/media?parent=3583"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/categories?post=3583"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/tags?post=3583"},{"taxonomy":"xinya_product_feature","embeddable":true,"href":"https:\/\/xinya-ee.com\/es\/wp-json\/wp\/v2\/product-features?post=3583"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}