{"id":1517,"date":"2021-11-13T10:45:49","date_gmt":"2021-11-13T10:45:49","guid":{"rendered":"https:\/\/arzhost.com\/blogs\/?p=1517"},"modified":"2025-09-30T14:04:19","modified_gmt":"2025-09-30T09:04:19","slug":"mysql-error-1062-duplicate-entry-for-key-primary","status":"publish","type":"post","link":"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/","title":{"rendered":"How to Resolve MySQL Error 1062 Duplicate Entry for Key Primary"},"content":{"rendered":"<p>A screw-up we now and again see in MySQL servers while reviving, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d. Restoring or copying databases is: Error No: 1062 or Error Code: 1062 or ERROR 1062 (23000)<\/p>\n<p>Around here at <span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/www.arzhost.com\/\"><strong>ARZHOST<\/strong><\/a><\/span>, couldn&#8217;t execute the Write rows event on the table my database name. table; Duplicate segment 174465 for key PRIMARY, Error code: 1062; regulator error HA_ERR_FOUND_DUPP_KEY; the events ace log MySQL-bin.000004, end_log_pos 60121977<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_74 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#What_is_MySQL_Error_No_1062\" >What is MySQL Error No: 1062?<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Weve_seen_essentially_4_clarifications_behind_this_error\" >We\u2019ve seen essentially 4 clarifications behind this error:<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Bit_by_bit_directions_to_fix_Error_No_1062_when_your_web_application_is_broken\" >Bit by bit directions to fix Error No 1062 when your web application is broken<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Web_application_error_game_plan\" >Web application error game plan<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#The_code_checks_out_along_these_lines\" >The code checks out along these lines:<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#The_best_strategy_to_fix_MySQL_replication_Error_Code_1062\" >The best strategy to fix MySQL replication Error Code: 1062<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Bit_by_bit_guidelines_to_delete_the_line\" >Bit by bit guidelines to delete the line<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Then_respite_and_start_the_slave\" >Then, respite and start the slave:<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#The_best_technique_to_keep_away_from_the_line\" >The best technique to keep away from the line<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Proceed_cautiously\" >Proceed cautiously<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#The_best_strategy_to_fix_MySQL_restore_errors\" >The best strategy to fix MySQL restore errors<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Guidelines_to_fix_duplicate_sections_in_database_dumps\" >Guidelines to fix duplicate sections in database dumps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#If_your_record_report_is_polluted\" >If your record report is polluted<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#Conclusion\" >Conclusion<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/arzhost.com\/blogs\/mysql-error-1062-duplicate-entry-for-key-primary\/#People_Also_Ask\" >People Also Ask<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"What_is_MySQL_Error_No_1062\"><\/span><strong>What is MySQL Error No: 1062? <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"color: #000000;\">\u201c<strong>MYSQL Error 1062 Duplicate Entry for Key Primary<\/strong><\/span>\u201d, screw up 1062 is shown when MySQL notices a DUPLICATE of a segment. You are endeavoring to implant.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Weve_seen_essentially_4_clarifications_behind_this_error\"><\/span><u>We\u2019ve seen essentially 4 clarifications behind this error: <\/u><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>The web application has a bug that adds fundamental key by gigantic options and drains quite far.<\/li>\n<li>MySQL bunch replication endeavors to re-install a field.<\/li>\n<li>An informational collection dump record contains duplicate lines because of a coding error.<\/li>\n<li>MySQL list table has duplicate segments.<\/li>\n<\/ul>\n<p>In phenomenal cases, this mix-up is shown when the table ends up being excessively wonderful. \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d yet let\u2019s not worry about that for the present.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Bit_by_bit_directions_to_fix_Error_No_1062_when_your_web_application_is_broken\"><\/span><strong>Bit by bit directions to fix Error No 1062 when your web application is broken <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Every database-driven application like WordPress, Drupal. Open Cart remembers one customer or helpful record from another using something many allude to as a fundamental field. This fundamental field should be recorded for each customer, post, etc<\/p>\n<p><u>Web applications use a code like this to insert data: <\/u><\/p>\n<ul>\n<li><code>Expansion INTO table ('id','field1','field2','field3') VALUES ('NULL','data1','data2','data3');<\/code><\/li>\n<\/ul>\n<p>Where it is the exciting primary key, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d and is set to auto-increment. (That is a number installed will reliably be more unmistakable than the beyond one to avoid duplicates).<\/p>\n<p>This will work right if the value inserted is NULL and the informational index table is set to auto-increment. Some web applications, unfortunately, pass the value as<\/p>\n<ul>\n<li><code>Characteristics ('','data1','data2','data3');<\/code><\/li>\n<\/ul>\n<p>Where the essential field is barred. This will insert sporadic numbers into the fundamental field, rapidly growing the number to the best field limit (typically 2147483647 for numbers).<\/p>\n<p>\u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d All following requests will again effort to over-create the field with 2147483647, which MySQL unties as a Duplicate.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Web_application_error_game_plan\"><\/span><strong>Web application error game plan <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Exactly when we see a potential web application code error. The specialists at our Website Support Services make a fix to the application report that fixes the informational index question.<\/p>\n<p>We have the non-sequential fundamental key table to be fixed. For that, we make another part (otherwise called field), set it as auto-expansion. A while later make it the fundamental key.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"The_code_checks_out_along_these_lines\"><\/span><strong><u>The code checks out along these lines: <\/u><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>change table table1 drop fundamental key;<\/li>\n<li>change table table1 add field2 into the not invalid auto-increment fundamental key;<\/li>\n<\/ul>\n<p>At the point when the fundamental key fields are stacked up with progressive characteristics, the name of the new field can be changed to the past one. So that all web application requests will proceed as in the past. These orders can get very amazing, amazingly fast. \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d if you don&#8217;t have the foggiest idea. How these commands work, it&#8217;s best to get ace assistance.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_best_strategy_to_fix_MySQL_replication_Error_Code_1062\"><\/span><strong>The best strategy to fix MySQL replication Error Code: 1062 <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>As a result of variability\u2019s in the organization or harmonizing MySQL is once in a known effort to create a section when it is free in the slave. Subsequently, when we see this slip-up in a slave, we effort both of the going with depending upon many elements, for instance, DB create traffic, period of the day, etc<\/p>\n<ul>\n<li><strong>Remove the segment &#8211;<\/strong> This is the quicker and safer method of continuing if you understand that the line being formed is just about as old as of now present.<\/li>\n<li><strong>Skirt the line &#8211;<\/strong> If you don&#8217;t know there be a data accident, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, you can have a go at keeping away from the line.<\/li>\n<\/ul>\n<h2><\/h2>\n<h2><a href=\"https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062.jpg\"><img fetchpriority=\"high\" decoding=\"async\" class=\"alignnone  wp-image-14275\" title=\"mysql replication error 1062\" src=\"https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062-300x157.jpg\" alt=\"mysql replication error 1062\" width=\"732\" height=\"383\" srcset=\"https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062-300x157.jpg 300w, https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062-1024x536.jpg 1024w, https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062-768x402.jpg 768w, https:\/\/arzhost.com\/blogs\/wp-content\/uploads\/2025\/09\/mysql-replication-error-1062.jpg 1200w\" sizes=\"(max-width: 732px) 100vw, 732px\" \/><\/a><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Bit_by_bit_guidelines_to_delete_the_line\"><\/span><strong>Bit by bit guidelines to delete the line <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>\u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d First remove the line using the fundamental key.<\/p>\n<ul>\n<li>remove from table1 where field1 is key1;<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Then_respite_and_start_the_slave\"><\/span><u>Then, respite and start the slave: <\/u><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><code>stop slave;<\/code><\/li>\n<li><code>start slave;<\/code><\/li>\n<li><code>select sleep (5);<\/code><\/li>\n<\/ul>\n<p>At whatever point it is done, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d truly investigates the slave status to check whether replication is continuing.<\/p>\n<ul>\n<li><code>show slave status;<\/code><\/li>\n<\/ul>\n<p>On the off chance that everything is extraordinary, you\u2019ll believe \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, Seconds_Behind_Master to be a number. If not, your replication is broken and it ought to be fixed.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_best_technique_to_keep_away_from_the_line\"><\/span><strong>The best technique to keep away from the line <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>\u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, For this, you can set the Skip counter to 1.<\/p>\n<p><u>Here\u2019s how it could look like: <\/u><\/p>\n<ul>\n<li><code>stop slave;<\/code><\/li>\n<li><code>set overall SQL_SLAVE_SKIP_COUNTER = 1;<\/code><\/li>\n<li><code>start slave;<\/code><\/li>\n<li><code>select sleep (5);<\/code><\/li>\n<\/ul>\n<p>Then, truly investigate the slave status to check whether replication is continuing.<\/p>\n<ul>\n<li><code>show slave status;<\/code><\/li>\n<\/ul>\n<p>Again, on the off chance that everything is incredible. You\u2019ll believe \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, Seconds_Behind_Master to be a number. If not, your replication is broken and it ought to be fixed.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Proceed_cautiously\"><\/span><strong>Proceed cautiously <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Ending and starting the slave can&#8217;t cause any issue except if you have an outstandingly clamoring database for any situation. The remove clarification, skipping, and returning to a wrecked replication requires ace data about MySQL affiliation and working<\/p>\n<p>If you don&#8217;t have the foggiest idea of what these orders will mean for your database. \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d we approve your chat with a DB director.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_best_strategy_to_fix_MySQL_restore_errors\"><\/span><strong>The best strategy to fix MySQL restore errors <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>\u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, Restore error generally show up as:<\/p>\n<ul>\n<li><code>Screw up 1062 (23000) at line XXXX: Duplicate segment XXXXXX for key X<\/code><\/li>\n<\/ul>\n<p><u>While restoring informational index dumps, this error can happen given 2 reasons: <\/u><\/p>\n<ul>\n<li>The SQL dump record has duplicate areas.<\/li>\n<li>The record archive is duplicate lines.<\/li>\n<\/ul>\n<p>To find what is turning out gravely. We look at the consistent lines and check whether they have something almost identical or different data. Expecting its comparable data, the issue could be a result of duplicate rundown lines. If it is different data, the SQL dump record ought to be fixed.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Guidelines_to_fix_duplicate_sections_in_database_dumps\"><\/span><strong>Guidelines to fix duplicate sections in database dumps <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The current situation can happen when something like two tables is dumped into a singular report without checking for duplicates. To decide this, the single heading we\u2019ve used is to make one more fundamental key field with auto-expansion. subsequently, change the requests to implant NULL value into it.<\/p>\n<p>Then, continue with the landfill. At the point when the new fundamental field table is populated, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d, the name of the field is changed to the old fundamental table name to save the old inquiries.<\/p>\n<p><u>The change table request will look like this: <\/u><\/p>\n<ul>\n<li>adjust table table1 change portion &#8216;new primary&#8217; &#8216;old primary&#8217; varchar (255) not invalid;<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"If_your_record_report_is_polluted\"><\/span><strong>If your record report is polluted <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There\u2019s no upfront method of fixing a documented record if there are duplicate areas in it.<\/p>\n<p>You\u2019ll need to delete the record archive and restore that report either from lines or from another server. Where your informational index dump is restored to another DB server. The means included are extremely minded confusing to run through here. \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d We recommend that you counsel a DB ace if you hypothesize the rundown record is damaged.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span><strong>Conclusion<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>MySQL error no 1062 can happen in light of buggy web applications, damaged dump records, or replication issues. \u201c<a href=\"https:\/\/en.wikipedia.org\/wiki\/MySQL\" target=\"_blank\" rel=\"noopener\">MYSQL<\/a> Error 1062 Duplicate Entry for Key Primary\u201d Today at ARZHOST, we\u2019ve seen the various habits by which the justification behind this error can be recognized. How it might be settled.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"People_Also_Ask\"><\/span><strong>People Also Ask<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>Question # 1: What is meant by the duplicate entry for key primary?<\/strong><\/p>\n<p>Answer: When creating a primary key or unique constraint after loading the data, you can get a \u201cDuplicate entry for key &#8216;PRIMARY&#8217;\u201d error. If the data in the source database is valid and there are no duplicates you should check which collation is used in your MySQL database.<\/p>\n<p><strong>Question # 2: What is a duplicate entry?<\/strong><\/p>\n<p>Answer: Definition of duplicate (Entry 3 of 3) 1a: either of two things exactly alike and usually produced at the same time or by the same process. b: an additional copy of something (such as a book or stamp) already in a collection. 2: one that resembles or corresponds to another counterpart.<\/p>\n<p><strong>Question # 3: How do I fix a duplicate entry in MySQL?<\/strong><\/p>\n<p>Answer: Unique values are labeled with row number 1, while duplicates are 2, 3, and so on. Therefore, to remove duplicate rows. You need to delete everything except the ones marked with 1. This is done by running a DELETE query with the row_number as the filter.<\/p>\n<p><strong>Question # 4: How do I ignore duplicate records in SQL?<\/strong><\/p>\n<p>Answer: To remove duplicates from a result set, you use the DISTINCT operator in the SELECT clause as follows: SELECT DISTINCT column1, column2, FROM table1; If you use one column after the DISTINCT operator. The database system uses that column to evaluate duplicates.<\/p>\n<p><strong>Question # 5: How do you prevent duplicates in SQL queries?<\/strong><\/p>\n<p>Answer: When the result set from a SELECT statement contains duplicate rows. You may want to remove them and keep every row data to be unique for a column or combination of columns. You can use the DISTINCT or DISTINCTROW identifier to eliminate duplicate records.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A screw-up we now and again see in MySQL servers while reviving, \u201cMYSQL Error 1062 Duplicate Entry for Key Primary\u201d. Restoring or copying databases is: Error No: 1062 or Error Code: 1062 or ERROR 1062 (23000) Around here at ARZHOST, couldn&#8217;t execute the Write rows event on the table my database name. table; Duplicate segment [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":7176,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,22,14,26,16],"tags":[],"table_tags":[],"class_list":["post-1517","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledge","category-hosting","category-news","category-server","category-tutorial"],"_links":{"self":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/1517","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/comments?post=1517"}],"version-history":[{"count":5,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/1517\/revisions"}],"predecessor-version":[{"id":14276,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/1517\/revisions\/14276"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/media\/7176"}],"wp:attachment":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/media?parent=1517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/categories?post=1517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/tags?post=1517"},{"taxonomy":"table_tags","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/table_tags?post=1517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}