{"id":24401,"date":"2026-09-28T11:08:08","date_gmt":"2026-09-28T11:08:08","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=24401"},"modified":"2026-09-28T11:08:08","modified_gmt":"2026-09-28T11:08:08","slug":"build-an-app-like-spotify-in-the-usa","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/build-an-app-like-spotify-in-the-usa\/","title":{"rendered":"How to Build an App Like Spotify in the USA: Licensing, Features, Tech Stack, and Cost"},"content":{"rendered":"<p><b>TL;DR<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The hardest part of building a music streaming app in the US is music licensing, not engineering. Rights come before code.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A realistic US build lands between $60,000 for a narrow MVP and $300,000+ for a full catalog product.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Your three make-or-break systems are adaptive audio delivery, a recommendation engine, and an accurate royalty reporting pipeline.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EngineerBabu builds streaming and AI-heavy products end to end, from MVP to a platform that survives its first traffic spike.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Nobody quits Spotify because the play button is slow. They quit because the app forgot what they like. That gap, between playing audio and understanding a listener, is the real project here.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Plenty of founders assume the challenge is streaming a file to a phone. It isn&#8217;t. Storage is cheap, delivery is a solved problem, and the codecs are decades old. What separates a real product from a weekend prototype is licensed catalog, personalization that improves weekly, and payouts that hold up to an audit.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This guide covers how to build an app like Spotify in the USA, from rights clearance through launch, with the numbers and tradeoffs laid out plainly.<\/span><\/p>\n<h2><b>What does it take to build an app like Spotify?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">To build an app like Spotify in the US, you need four things: licensed music rights, a scalable streaming backend, personalization powered by listening data, and a usage reporting system for royalties.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Expect six to twelve months for a credible first version. Licensing negotiations, not development, usually set your timeline.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Spotify itself just crossed<\/span><a href=\"https:\/\/newsroom.spotify.com\/2026-08-04\/spotify-q2-2026-earnings\/\" target=\"_blank\" rel=\"noopener\"> <span style=\"font-weight: 400;\">300 million Premium subscribers in Q2 2026<\/span><\/a><span style=\"font-weight: 400;\">, a milestone no audio service had reached before. That is the ceiling you are competing under, and it explains why new entrants win by niche, not by catalog size.<\/span><\/p>\n<h2><b>Sort Out Music Licensing Before You Write Any Code<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">This is the section most tutorials skip, and it is the one that kills projects. In the US, streaming a song touches two separate copyrights: the composition and the sound recording. You need permission for both.<\/span><\/p>\n<h3><b>The rights you actually need<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Sound recording rights.<\/b><span style=\"font-weight: 400;\"> Owned by labels or distributors. For on-demand playback, you negotiate directly or license through an aggregator.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Mechanical rights.<\/b><span style=\"font-weight: 400;\"> Covered in the US through a blanket license from The MLC under the Music Modernization Act.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Public performance rights.<\/b><span style=\"font-weight: 400;\"> Licensed from ASCAP, BMI, SESAC, and GMR, usually all four.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Sync rights.<\/b><span style=\"font-weight: 400;\"> Only relevant if users pair music with video.<\/span><\/li>\n<\/ul>\n<h3><b>The shortcut most startups take<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">If your product is radio style rather than on-demand, the statutory license under Section 114 lets you pay SoundExchange instead of negotiating with every label. The catch is strict: no song requests, limited skips, no published playlists in advance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you want true on-demand control, B2B catalog providers such as 7digital or Audiosalad license pre-cleared catalogs with delivery APIs included. You pay more per stream. You launch months earlier.<\/span><\/p>\n<h2><b>The Feature Set That Earns Retention<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Feature bloat is the fastest way to burn a budget. When you build an app like Spotify, split the scope into what listeners see and what your operation quietly needs.<\/span><\/p>\n<h3><b>Listener-facing features<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search across tracks, albums, artists, and lyrics<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Playback with gapless transitions, crossfade, and queue control<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Offline downloads with encrypted local storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Algorithmic mixes plus editorial and user playlists<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Social layers like shared playlists, follows, and activity feeds<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Free tier with ad insertion, paired with subscription upgrade flows<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The social layer deserves real attention, since sharing drives most organic installs. The same mechanics covered in our guide on<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/social-media-app-development\/\"> <span style=\"font-weight: 400;\">social media app development<\/span><\/a><span style=\"font-weight: 400;\"> apply directly to playlist sharing and follows.<\/span><\/p>\n<h3><b>Back-office features you cannot skip<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Artist dashboards showing streams, listener geography, and payouts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Catalog ingestion with metadata validation and duplicate detection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Per-stream logging tied to rights holders for royalty statements<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fraud detection for artificially inflated play counts<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">That last one matters more than founders expect. Labels audit stream counts, and bot traffic on your platform becomes your financial liability.<\/span><\/p>\n<h2><b>How to Build an App Like Spotify: A Five-Step Build Path<\/b><\/h2>\n<h3><b>Step 1: Pick a wedge, then clear rights for it<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Do not start with a global catalog. Pick an audience you can actually serve better than the incumbents, such as independent hip-hop, regional Latin music, audiobooks for commuters, or DJ-focused long-form sets. A narrow scope makes licensing conversations dramatically easier, because you approach ten distributors instead of three majors.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It also gives your recommendation engine dense data in a small space, which produces better results faster. Write down your wedge before your first label call. Every licensing term, from territory to per-stream floor, flows from that single decision.<\/span><\/p>\n<h3><b>Step 2: Build the MVP around one behavior<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Your first release should prove that people return, not that you can ship features. Pick one behavior to nail, usually discovery or offline listening, and build only what supports it. A focused<\/span><a href=\"https:\/\/engineerbabu.com\/services\/mvp-development\"> <span style=\"font-weight: 400;\">MVP development<\/span><\/a><span style=\"font-weight: 400;\"> cycle gets you to real listener data in three to four months instead of a year.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ship with a modest catalog, one platform, and a single subscription tier. Instrument everything, since day-seven and day-thirty retention will tell you whether the product concept works. Founders planning an<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/mvp-development-for-startups-in-the-usa\/\"> <span style=\"font-weight: 400;\">MVP for the US market<\/span><\/a><span style=\"font-weight: 400;\"> should budget for licensing minimums alongside engineering.<\/span><\/p>\n<h3><b>Step 3: Engineer the streaming backbone<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Audio delivery runs on adaptive bitrate streaming through HLS or MPEG-DASH, with AAC encoding at multiple bitrates. Segment every track during ingestion, store the variants in object storage, and serve through a CDN with edge caching near your listeners. Protect the stream with AES-128 or Widevine DRM so downloads cannot be extracted as plain files.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Playback state, queue position, and device handoff belong in Redis for low latency. This layer lives or dies on<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/role-of-cloud-computing-in-app-scalability\/\"> <span style=\"font-weight: 400;\">cloud infrastructure that scales with demand<\/span><\/a><span style=\"font-weight: 400;\">, since listening spikes hard on weekday mornings and Friday releases.<\/span><\/p>\n<h3><b>Step 4: Build recommendations on real signals<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Personalization is why listeners stay, so treat it as a product, not a feature. Start with collaborative filtering on playback events, then layer audio embeddings so new tracks with no listening history still get surfaced. Feed the model explicit signals like saves and skips, plus implicit ones like completion rate and repeat plays.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Skips inside the first thirty seconds are your strongest negative signal. Teams applying<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/ai-in-mobile-app-development\/\"> <span style=\"font-weight: 400;\">AI in mobile app development<\/span><\/a><span style=\"font-weight: 400;\"> usually see the biggest lift from session context, meaning time of day, device, and the track that came before.<\/span><\/p>\n<h3><b>Step 5: Ship, instrument, and harden<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Release to a closed beta in one metro area before a national launch. Watch buffer ratio, time to first audio frame, and crash rate per session, since those three predict churn better than any survey. Test on weak networks, older Android devices, and CarPlay, because a lot of listening happens in cars and subways.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Confirm your royalty reporting matches playback logs exactly before your first statement is due. Continuous<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/strategies-for-mobile-app-performance-optimization\/\"> <span style=\"font-weight: 400;\">performance optimization<\/span><\/a><span style=\"font-weight: 400;\"> after launch protects the experience as your catalog and user base grow.<\/span><\/p>\n<h2><b>Tech Stack Choices That Hold Up<\/b><\/h2>\n<table>\n<tbody>\n<tr>\n<td><b>Layer<\/b><\/td>\n<td><b>Practical choice<\/b><\/td>\n<td><b>Why it works<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Audio delivery<\/span><\/td>\n<td><span style=\"font-weight: 400;\">HLS or DASH, AAC 128 to 320 kbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Adaptive quality across weak networks<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">CDN<\/span><\/td>\n<td><span style=\"font-weight: 400;\">CloudFront, Fastly, or Cloudflare<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Edge caching cuts startup latency<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Backend<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Go or Node.js microservices<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Handles high concurrent stream sessions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Catalog database<\/span><\/td>\n<td><span style=\"font-weight: 400;\">PostgreSQL<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Relational metadata with strong integrity<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Event pipeline<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Kafka<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Playback events feed models and royalties<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Search<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Elasticsearch or OpenSearch<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Typo-tolerant search across millions of tracks<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Recommendations<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Python with PyTorch<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Mature ecosystem for embeddings and ranking<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Mobile apps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Swift and Kotlin, or Flutter<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Native for audio control, cross-platform for speed<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The mobile decision deserves a real conversation. Background audio, lock screen controls, CarPlay, and Android Auto integrate more cleanly with native code. Cross-platform saves roughly 30 to 40 percent of frontend cost.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our breakdown of<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/native-vs-cross-platform-development\/\"> <span style=\"font-weight: 400;\">native versus cross-platform development<\/span><\/a><span style=\"font-weight: 400;\"> covers where each one breaks down.<\/span><\/p>\n<h2><b>What It Costs to Build an App Like Spotify in the USA<\/b><\/h2>\n<table>\n<tbody>\n<tr>\n<td><b>Scope<\/b><\/td>\n<td><b>Typical US range<\/b><\/td>\n<td><b>What you get<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Focused MVP<\/span><\/td>\n<td><span style=\"font-weight: 400;\">$60,000 to $110,000<\/span><\/td>\n<td><span style=\"font-weight: 400;\">One platform, limited catalog, basic personalization<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Mid-scale product<\/span><\/td>\n<td><span style=\"font-weight: 400;\">$120,000 to $250,000<\/span><\/td>\n<td><span style=\"font-weight: 400;\">iOS and Android, offline mode, recommendations, ads<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Full-scale platform<\/span><\/td>\n<td><span style=\"font-weight: 400;\">$300,000+<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Multi-region, artist tools, advanced ML, high availability<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Engineering is only part of the bill. Licensing advances, minimum guarantees, and per-stream royalties often exceed development cost in year one. Budget 15 to 20 percent of the original build annually for maintenance and catalog operations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For a stage-by-stage breakdown of what drives these numbers, read our full guide on<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/mobile-app-development-cost-in-usa\/\"> <span style=\"font-weight: 400;\">mobile app development cost in the USA<\/span><\/a><span style=\"font-weight: 400;\">. If you are pressure testing a schedule with investors, our<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/timeline-to-build-a-mobile-app\/\"> <span style=\"font-weight: 400;\">app development timeline<\/span><\/a><span style=\"font-weight: 400;\"> breakdown is a useful reality check.<\/span><\/p>\n<h2><b>Mistakes That Sink Music Streaming Apps<\/b><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Launching with a huge catalog and no personality.<\/b><span style=\"font-weight: 400;\"> Ten million tracks with weak curation feels emptier than fifty thousand well organized ones.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Treating royalty reporting as an afterthought.<\/b><span style=\"font-weight: 400;\"> Rebuilding a reporting pipeline under contractual pressure costs three times what building it properly would have.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Ignoring offline playback.<\/b><span style=\"font-weight: 400;\"> US listeners use it on flights, commutes, and in dead zones. Skipping it caps your retention.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Underestimating ongoing support.<\/b><span style=\"font-weight: 400;\"> Catalog updates, OS releases, and DRM changes never stop, which is why<\/span><a href=\"https:\/\/engineerbabu.com\/blog\/mobile-app-maintenance-and-support\/\"> <span style=\"font-weight: 400;\">app maintenance and support<\/span><\/a><span style=\"font-weight: 400;\"> belongs in your first budget.<\/span><\/li>\n<\/ul>\n<h2><b>Where EngineerBabu Fits<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">If you want to build an app like Spotify without learning every lesson the expensive way, partner selection matters early. <\/span><a href=\"http:\/\/engineerbabu.com\"><span style=\"font-weight: 400;\">EngineerBabu<\/span><\/a><span style=\"font-weight: 400;\"> builds AI-driven and media-heavy products through a CMMI Level 5 delivery process, with senior engineers staying on the project rather than rotating off after kickoff.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The practical value is in scoping. A team that has shipped streaming architecture knows which 20 percent of the feature list drives retention and which 80 percent can wait until after your licensing deals prove out. Teams comparing options can talk to us directly about<\/span><a href=\"https:\/\/engineerbabu.com\/services\/mobile-app-development\"> <span style=\"font-weight: 400;\">custom mobile app development<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h2><b>Final Thoughts<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The decision to build an app like Spotify is really a licensing decision wearing an engineering costume. Get the rights model right, pick a listener niche you can genuinely serve, and the technical work becomes tractable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Start narrow, ship in months rather than years, and let listening data tell you what to build next. Ready to scope your build? Talk to the EngineerBabu team about your music streaming product.<\/span><\/p>\n<h2><b>FAQs<\/b><\/h2>\n<ul>\n<li aria-level=\"1\">\n<h3><b>How long does it take to build an app like Spotify?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">A focused MVP takes three to four months of development. A full-featured platform takes eight to twelve. Licensing negotiations run in parallel and often become the real bottleneck, sometimes adding two to six months before launch.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Do I need licenses from record labels to launch a music app?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Yes, for on-demand playback. Radio-style services can use the statutory license through SoundExchange instead. Interactive features like song selection and unlimited skips require direct label or aggregator deals.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>What does it cost to build an app like Spotify in the US?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Development ranges from roughly $60,000 for a narrow MVP to $300,000 or more for a full platform. Licensing advances and per-stream royalties are separate and frequently larger in year one.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Can I use a cross-platform framework for a streaming app?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Yes. Flutter and React Native handle most of the interface well. Background audio, CarPlay, and Android Auto often need native modules, so plan for a hybrid approach rather than pure cross-platform.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>What technology powers Spotify-style audio streaming?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Adaptive bitrate streaming over HLS or DASH, AAC encoded audio, CDN edge delivery, and DRM for offline files. Behind that sit event pipelines and recommendation models trained on playback behavior.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR The hardest part of building a music streaming app in the US is music licensing, not engineering. Rights come before code. A realistic US build lands between $60,000 for a narrow MVP and $300,000+ for a full catalog product. Your three make-or-break systems are adaptive audio delivery, a recommendation engine, and an accurate royalty [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":24403,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1258],"tags":[],"class_list":["post-24401","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-app-development"],"_links":{"self":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24401","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/comments?post=24401"}],"version-history":[{"count":1,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24401\/revisions"}],"predecessor-version":[{"id":24404,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24401\/revisions\/24404"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media\/24403"}],"wp:attachment":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media?parent=24401"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/categories?post=24401"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/tags?post=24401"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}