{"id":530,"date":"2024-05-22T12:54:10","date_gmt":"2024-05-22T17:54:10","guid":{"rendered":"https:\/\/readmeprd.wpenginepowered.com\/?p=530"},"modified":"2025-12-16T19:53:30","modified_gmt":"2025-12-17T01:53:30","slug":"how-to-engage-your-api-users","status":"publish","type":"post","link":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users","title":{"rendered":"How to Engage Your API Users (and Get More of Them)"},"content":{"rendered":"\n<p>What\u2019s the point of building an API if nobody uses it?<\/p>\n\n\n\n<p>In the API world, the saying \u201cIf you build it they will come,\u201d absolutely doesn\u2019t hold true. As a matter a fact, if you build an API without marketing, explaining, and documenting it well, you\u2019re on your way to getting lots of people to hate your business.<\/p>\n\n\n\n<p>Before we get into the weeds, let&#8217;s make sure you have the basics covered: <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"landing-experience\">The landing page: Your documentation&#8217;s &#8220;cover&#8221;<\/h3>\n\n\n\n<p>The old adage says not to choose a book by its cover, but we all know that in the age of short attention spans, that&#8217;s exactly what happens \u2014 and your API is no exception to this pattern of behavior. <\/p>\n\n\n\n<p>There are other ways for users to accomplish what your API allows them to do. <strong>Convince them that your API is the best way. <\/strong>Users will make instant assumptions about your technical prowess, software design, and support immediately after landing on your developer hub. What do you want them to come away thinking?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"why-should-businesses-use-your-api\">Give them the &#8220;why&#8221;<\/h3>\n\n\n\n<p><strong>Your developer hub needs to explain <em>why<\/em> companies should use your API. <\/strong>Think about it: most companies wouldn&#8217;t dream of creating a marketing site that consists exclusively of dry product specs. But when it comes time to publish their API documentation, suddenly it&#8217;s acceptable to dump a page of endpoint URLs on somebody and say, \u201cFigure it out!\u201d<\/p>\n\n\n\n<p>At the bare minimum, you need to: <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Clearly convey the benefits<\/strong> \u2014 what does your API let them do? How does it make their work easier, improve the lives of their users, or save them money? <\/li>\n\n\n\n<li><strong>Showcase common use cases, <\/strong>as well as linking to the guides they&#8217;ll need to implement those use cases<\/li>\n<\/ul>\n\n\n\n<p>In general, you want to do everything you can to ground your API in real-world problems (and show how it&#8217;s the solution to those problems). <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"how-do-developers-get-started\">Tell them how to start<\/h3>\n\n\n\n<p>Now your users know you have an API, and they know why they should use it, but do they know where to get started? Specifically, they need to know how to get access and where to go for support (should they need it). If you need inspiration, check out <a href=\"https:\/\/readme.com\/resources\/the-most-effective-api-quickstarts-in-8-examples\/\">this list of quick start examples<\/a> (or just keep reading!). <\/p>\n\n\n\n<p>Of course, these are just the basics \u2014 now it&#8217;s time to build on them and create a community of engaged users: <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How do I keep my API users engaged? <\/h2>\n\n\n\n<p>You have a kickass API and your landing page checks all the 101 boxes \u2014 now it&#8217;s time to get people to engage. The only problem is that this&#8230;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.readme.com\/content\/images\/2016\/11\/twilio-code.png\" alt=\"Screenshot of sample code from Twilio's API documentation\"\/><\/figure>\n\n\n\n<p>&#8230;isn&#8217;t exactly sexy. Nor does it show what your API is capable of. <strong>You can show an example call or curl command, or part of the feed that your API returns, and none of that would even come close to showing off the well-designed API your team is so proud of building.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"collaboratewithyourusers\">Collaborate with your users<\/h2>\n\n\n\n<p>Static documentation written as a one-and-done deal isn&#8217;t going to engage your users. Developers are going to come to your page, browse through the docs, get bored, and bounce. But all those devs are working on their own projects and are chock-full of great ideas for cool things to do with your API. Not collaborating with them is a huge missed opportunity.<\/p>\n\n\n\n<p><strong>Create a community around your API so that you can learn from your users and adjust your documentation and design accordingly. <\/strong>Your community of developers will feel more invested in your product, and you&#8217;ll learn more about what&#8217;s possible with your own API.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Crowdsource your docs<\/h3>\n\n\n\n<p>If open source software has taught us anything, it&#8217;s that hundreds of developers QAing a product is better than one. Same goes for documentation. Instead of creating static documentation, like the hundred-page PDF manuals of the previous decade, create an interactive developer hub. Having <a href=\"https:\/\/docs.readme.com\/main\/docs\/suggested-edits\">a &#8220;suggest edits&#8221; button<\/a> is a great way to actively incorporate user feedback, without adding a ton of extra work to your team&#8217;s to-do list. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Open up lines of communication<\/h3>\n\n\n\n<p>The more lines of communication you have with your API users, the easier it will be to stir up a community. Use several mediums to announce updates in order to get your API users excited about new use cases and help spread the word.<\/p>\n\n\n\n<p>For example, Stripe regularly shares updates about their documentation, including when they add new features or content \u2014 like launching their app integration directory:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.readme.com\/content\/images\/2016\/11\/stripe-tweet.png\" alt=\"Tweet from Stripe announcing app directory for integrations\"\/><\/figure>\n\n\n\n<p>They even <a href=\"https:\/\/x.com\/StripeDev\">created another Twitter account<\/a> to share updates that are specific to developers and improving their developer experience. This strategy has worked well for them over the years, and now they have a strong following of developers, and <a href=\"https:\/\/docs.stripe.com\/\">comprehensive documentation<\/a> to meet the needs of those developers. <\/p>\n\n\n\n<p><strong>Try to fire on all fronts and engage users through several mediums.<\/strong> Other platforms you can use include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Hacker News<\/strong>: If you&#8217;re willing to put your API to the scrutiny of the <a href=\"https:\/\/news.ycombinator.com\/newest\">Hacker News<\/a> community, it&#8217;s a great way to stimulate conversation around new updates.<\/li>\n\n\n\n<li><strong>Product Hunt:<\/strong> Make sure that your post meets the <a href=\"https:\/\/www.producthunt.com\/faq\">community guidelines<\/a>. Once you post it, email your community to let them know. Upvotes can help it make the front page, in which case your API engagement will go through the roof.<\/li>\n\n\n\n<li><strong>Slack<\/strong>: Some companies create a <a href=\"http:\/\/slack.com\/\">Slack<\/a> community for their customers to ask questions and get instant answers from someone on the dev team. This is a great way to share updates and proactively seek feedback from your users. <em>(You can <a href=\"https:\/\/readme.com\/slack\">join the ReadMe Slack community<\/a> here!)<\/em><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Give the gift of beta access<\/h3>\n\n\n\n<p><strong>People love first dibs. <\/strong>The sooner you can tinker with something, the better. Extending beta access to your users will make them feel like an extension of your team. They&#8217;ll push the API to its limits, and feel compelled to reach out when something goes wrong. Best of all, they&#8217;ll feel more comfortable giving you feedback on the API in later stages, which means less bugs slip through the cracks.<\/p>\n\n\n\n<p>When <a href=\"https:\/\/clearbit.com\/\">Clearbit<\/a> did this, they even went a step further by offering a discount for the service after it launchedt:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.readme.com\/content\/images\/2016\/11\/clearbit--1-.png\" alt=\"Email from Clearbit announcing beta access to their API and a discount for beta users after public release\"\/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"makeiteasytodomore\">Make it easy to do more<\/h2>\n\n\n\n<p><strong>The faster a user can try their hand at your API, the more accessible it is. <\/strong>The obvious benefit is getting more developers integrating your platform. The less obvious benefit is encouraging each individual developer to go deeper into what&#8217;s possible with your API.<\/p>\n\n\n\n<p>You need to make the learning curve for your API as easy as possible, which means filling out the docs page with plenty of tools that make it quick and hassle-free to get started.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Quick start guides as marketing<\/h3>\n\n\n\n<p>As you get to know your API community, you&#8217;ll get acquainted with all the most popular use cases for your product. Once you know what those use cases are, you can create quick start guides to encourage both existing and potential users.<\/p>\n\n\n\n<p>For bonus points, add a time estimate for how long the process will take. If a developer knows they&#8217;ll be able to go through the entire tutorial in 15 minutes, they&#8217;re much more likely to give it a go than if they think it might be a several hour process. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sandboxing to try before you buy<\/h3>\n\n\n\n<p>Developers are curious people, but their curiosity will only take them so far. If they have to rework their dev environment and then go through a complicated authentication process, they&#8217;re likely to blow it off and get back to work. <strong>But if you set up sandbox functionality, you&#8217;ll tempt them to pursue that curiosity just a bit further.<\/strong><\/p>\n\n\n\n<p>Sonar, a <a href=\"http:\/\/www.sendsonar.com\">multi-platform communication tool for sales teams<\/a>, has sandbox functionality in their documentation, so you can check out all their most popular calls with relatively little effort.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"583\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-44-1024x583.png\" alt=\"Screenshot of API documentation from Sonar, showing interactive elements\" class=\"wp-image-2795\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-44-1024x583.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-44-300x171.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-44-768x438.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-44.png 1455w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Like Sonar, you can provide a curl command that devs can just drop into their command line, or, alternatively, you can add <a href=\"https:\/\/readme.com\/documentation\">interactive elements to your API docs<\/a>, enabling users to make a call right from the page.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Reputation is everything<\/h2>\n\n\n\n<p>At the end of the day, you <em>need<\/em> to have a well-designed well-documented API to maintain a good reputation in the dev community. No bells and whistles will make up for that.<\/p>\n\n\n\n<p>But engaging with your API users will get them invested and excited about your product. <strong>Not only will that get them to stick around, but it&#8217;ll get them to spread the word about your platform and all of its potential.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>What\u2019s the point of building an API if nobody uses it? In the API world, the saying \u201cIf you build it they will come,\u201d absolutely doesn\u2019t hold true. As a matter a fact, if you build an API without marketing, explaining, and documenting it well, you\u2019re on your way to getting lots of people to [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":2916,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[22,41],"tags":[42],"ppma_author":[49],"class_list":["post-530","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-api-tips","category-api-users","tag-api-tips"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library\" \/>\n<meta property=\"og:description\" content=\"What\u2019s the point of building an API if nobody uses it? In the API world, the saying \u201cIf you build it they will come,\u201d absolutely doesn\u2019t hold true. As a matter a fact, if you build an API without marketing, explaining, and documenting it well, you\u2019re on your way to getting lots of people to [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users\" \/>\n<meta property=\"og:site_name\" content=\"ReadMe: Resource Library\" \/>\n<meta property=\"article:published_time\" content=\"2024-05-22T17:54:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-12-17T01:53:30+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png\" \/>\n\t<meta property=\"og:image:width\" content=\"200\" \/>\n\t<meta property=\"og:image:height\" content=\"200\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kanad Gupta\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kanad Gupta\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users\",\"url\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users\",\"name\":\"How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library\",\"isPartOf\":{\"@id\":\"https:\/\/readme.com\/resources\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage\"},\"image\":{\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage\"},\"thumbnailUrl\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png\",\"datePublished\":\"2024-05-22T17:54:10+00:00\",\"dateModified\":\"2025-12-17T01:53:30+00:00\",\"author\":{\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/5ff0ec37fac9e314594c7a5564ee24ad\"},\"breadcrumb\":{\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage\",\"url\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png\",\"contentUrl\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png\",\"width\":200,\"height\":200},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/readme.com\/resources\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Engage Your API Users (and Get More of Them)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/readme.com\/resources\/#website\",\"url\":\"https:\/\/readme.com\/resources\/\",\"name\":\"ReadMe: Resource Library\",\"description\":\"Making API documentation better for everyone\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/readme.com\/resources\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/5ff0ec37fac9e314594c7a5564ee24ad\",\"name\":\"Kanad Gupta\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/image\/f411bab14c6f25f8d94c6658c39badd3\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/e1918540f557e223e19f33cf4db88f78bee3594cbcc066d92c4b609b68123058?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/e1918540f557e223e19f33cf4db88f78bee3594cbcc066d92c4b609b68123058?s=96&d=mm&r=g\",\"caption\":\"Kanad Gupta\"},\"description\":\"Joining us remotely from Minneapolis, Kanad forms the newly-minted Minnesota branch of the ReadMe team! We love Minnesota. Kanad just bought a bike and is loving riding around Minneapolis, but he\u2019s less enthused by the whole peddling aspect of it. While biking around MPLS, Kanad is probably listening to Janelle Mon\u00e1e\u2014his Spotify artist of the decade.\",\"url\":\"https:\/\/readme.com\/resources\/author\/kanad\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users","og_locale":"en_US","og_type":"article","og_title":"How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library","og_description":"What\u2019s the point of building an API if nobody uses it? In the API world, the saying \u201cIf you build it they will come,\u201d absolutely doesn\u2019t hold true. As a matter a fact, if you build an API without marketing, explaining, and documenting it well, you\u2019re on your way to getting lots of people to [&hellip;]","og_url":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users","og_site_name":"ReadMe: Resource Library","article_published_time":"2024-05-22T17:54:10+00:00","article_modified_time":"2025-12-17T01:53:30+00:00","og_image":[{"width":200,"height":200,"url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png","type":"image\/png"}],"author":"Kanad Gupta","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kanad Gupta","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users","url":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users","name":"How to Engage Your API Users (and Get More of Them) - ReadMe: Resource Library","isPartOf":{"@id":"https:\/\/readme.com\/resources\/#website"},"primaryImageOfPage":{"@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage"},"image":{"@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage"},"thumbnailUrl":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png","datePublished":"2024-05-22T17:54:10+00:00","dateModified":"2025-12-17T01:53:30+00:00","author":{"@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/5ff0ec37fac9e314594c7a5564ee24ad"},"breadcrumb":{"@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/readme.com\/resources\/how-to-engage-your-api-users"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#primaryimage","url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png","contentUrl":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/EngagingAPIUsers.png","width":200,"height":200},{"@type":"BreadcrumbList","@id":"https:\/\/readme.com\/resources\/how-to-engage-your-api-users#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/readme.com\/resources\/"},{"@type":"ListItem","position":2,"name":"How to Engage Your API Users (and Get More of Them)"}]},{"@type":"WebSite","@id":"https:\/\/readme.com\/resources\/#website","url":"https:\/\/readme.com\/resources\/","name":"ReadMe: Resource Library","description":"Making API documentation better for everyone","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/readme.com\/resources\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/5ff0ec37fac9e314594c7a5564ee24ad","name":"Kanad Gupta","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/image\/f411bab14c6f25f8d94c6658c39badd3","url":"https:\/\/secure.gravatar.com\/avatar\/e1918540f557e223e19f33cf4db88f78bee3594cbcc066d92c4b609b68123058?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/e1918540f557e223e19f33cf4db88f78bee3594cbcc066d92c4b609b68123058?s=96&d=mm&r=g","caption":"Kanad Gupta"},"description":"Joining us remotely from Minneapolis, Kanad forms the newly-minted Minnesota branch of the ReadMe team! We love Minnesota. Kanad just bought a bike and is loving riding around Minneapolis, but he\u2019s less enthused by the whole peddling aspect of it. While biking around MPLS, Kanad is probably listening to Janelle Mon\u00e1e\u2014his Spotify artist of the decade.","url":"https:\/\/readme.com\/resources\/author\/kanad"}]}},"authors":[{"term_id":49,"user_id":6,"is_guest":0,"slug":"kanad","display_name":"Kanad Gupta","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/e1918540f557e223e19f33cf4db88f78bee3594cbcc066d92c4b609b68123058?s=96&d=mm&r=g","first_name":"Kanad","last_name":"Gupta","position":"Developer Advocate & API Engineer","slogan":"Developer Advocate &amp; API Engineer (he\/him)","description":"Joining us remotely from Minneapolis, Kanad forms the newly-minted Minnesota branch of the ReadMe team! We love Minnesota.\r\n\r\nKanad just bought a bike and is loving riding around Minneapolis, but he\u2019s less enthused by the whole peddling aspect of it. While biking around MPLS, Kanad is probably listening to Janelle Mon\u00e1e\u2014his Spotify artist of the decade."}],"_links":{"self":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts\/530","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/comments?post=530"}],"version-history":[{"count":0,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts\/530\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/media\/2916"}],"wp:attachment":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/media?parent=530"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/categories?post=530"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/tags?post=530"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/ppma_author?post=530"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}