{"id":1440,"date":"2026-07-03T11:11:04","date_gmt":"2026-07-03T11:11:04","guid":{"rendered":"https:\/\/hirium.com\/blog\/?p=1440"},"modified":"2026-07-03T11:11:04","modified_gmt":"2026-07-03T11:11:04","slug":"recruitment-workflow-automation-tasks","status":"publish","type":"post","link":"https:\/\/hirium.com\/blog\/recruitment-workflow-automation-tasks\/","title":{"rendered":"Workflow Automation Software for Recruiters: 7 Tasks You Should Never Do Manually Again"},"content":{"rendered":"

A recruiter screening 200 applications by hand spends 5 to 15 hours on that single job req before a single interview is booked. Multiply that across six open roles and the math stops being a productivity question\u00a0 it becomes a hiring capacity problem. Recruitment workflow automation is not about replacing recruiters. It’s about deciding which of the 40 hours in a recruiter’s week should actually require a human.<\/span><\/p>\n

Most talent acquisition teams already believe they’re “using automation” because they own an applicant tracking system. But owning the software and configuring the workflows inside it are two different things. The gap between the two is where most of the wasted hours live.<\/span><\/p>\n

According to SHRM’s 2026 Recruiting Benchmarking data, organizations with the most effective recruitment practices\u00a0 those that lean on AI to automate repetitive tasks\u00a0 fill open roles roughly five days faster than organizations that don’t, and median time-to-fill for nonexecutive roles has already dropped from 44 days in 2025 to 39 days in 2026 as automation adoption has grown.\u00a0<\/span><\/p>\n

For a hiring team running four or five open roles at once, the difference between manual and automated recruiting isn’t marginal. It’s the difference between a recruiter who spends their week reacting to a backlog and one who spends it building a pipeline ahead of demand. Recruitment workflow automation is what closes that gap, and it’s worth understanding exactly where the hours go before deciding what to fix first.<\/span><\/p>\n

What Is Recruitment Workflow Automation?<\/b><\/h2>\n

Recruitment workflow automation<\/b><\/a> is the use of software to trigger, sequence, and complete repetitive hiring tasks\u00a0 screening, scheduling, status updates, reminders, reporting, and rejections\u00a0 without manual recruiter intervention at each step. It sits on top of or inside an <\/span>applicant tracking system<\/b> and replaces manual data entry with rule-based or AI-driven actions.<\/span><\/p>\n

It’s worth separating this from automation in the abstract. A calendar reminder or a canned email template is a small piece of automation; <\/span>recruitment workflow automation<\/b> specifically refers to connecting those pieces into a sequence that runs across the full candidate lifecycle, from application to onboarding, without a recruiter manually triggering each step in between.<\/span><\/p>\n

\"weekly<\/p>\n

The Core Problem: Recruiter Hours Are Going to the Wrong Work<\/b><\/h2>\n

Most teams underestimate how much of a recruiter’s week disappears into administrative overhead\u00a0 usually by 3 to 4x. It doesn’t feel like 20 hours a week when it’s broken into 15-minute scheduling emails and two-minute status updates. It adds up anyway.<\/span><\/p>\n

A recruiter managing 200 active candidates typically spends 8 to 15 minutes per candidate on manual data entry and status tracking alone\u00a0 27 to 50 hours a month, before sourcing or interviewing even starts. Interview coordination, when done manually, consumes another 5 to 15 hours per recruiter per week, since coordinating one interview across two calendars and a candidate’s inbox routinely takes 30 minutes to 2 hours of back-and-forth.<\/span><\/p>\n

The consequence isn’t just recruiter burnout. It’s slower <\/span>time-to-hire<\/b><\/a>, higher candidate drop-off, and a hiring funnel that scales worse every time headcount targets go up. A team hiring for 15 roles a quarter with no <\/span>recruitment workflow automation<\/b> in place is functionally understaffed, even if the org chart says otherwise.<\/span><\/p>\n

This shows up most clearly at the extremes of hiring volume. A startup hiring for its first 20 employees can often get away with manual processes because the absolute number of applications is low. The moment volume crosses roughly 150\u2013200 applicants per role\u00a0 which happens fast once a company posts to major job boards\u00a0 the manual model breaks. Recruiters stop being able to give every candidate a fair, timely response, and the tasks that get skipped first are exactly the ones candidates notice most: status updates and rejection notices.<\/span><\/p>\n

There’s also a cost dimension most teams don’t calculate. A mid-level recruiter loaded cost (salary, benefits, overhead) typically runs $75,000\u2013$100,000 a year. If half of that time goes to work a workflow tool could do\u00a0 data entry, scheduling logistics, sending the same email forty times\u00a0 the effective cost of manual admin per recruiter is $35,000\u2013$50,000 a year in fully-loaded time, before counting the slower time-to-hire that comes with it.<\/span><\/p>\n

None of this means recruiters are doing their jobs poorly. It means the tooling underneath them hasn’t caught up to the volume they’re expected to handle. <\/span>Recruitment workflow automation<\/b> exists specifically to close that gap\u00a0 not by removing recruiters from the process, but by removing the parts of the process that were never a good use of a recruiter’s judgment in the first place.<\/span><\/p>\n

The 7 Recruiting Tasks You Should Never Do Manually Again<\/b><\/h2>\n

This is the deep section of the actual checklist. Each task below includes the realistic manual-hours cost per week for a mid-size recruiting team (3\u20135 open roles, 150\u2013300 applicants per role) and what automating it typically requires.<\/span><\/p>\n

1. Resume Screening and Shortlisting<\/b><\/h3>\n

Manual cost:<\/b> 5\u201315 hours per week, per open role.<\/span><\/p>\n

Screening 150\u2013300 resumes by hand, at 30\u201390 seconds each, is the single biggest time sink in early-stage hiring\u00a0 and it’s also where <\/span>resume screening automation<\/b><\/a> delivers the fastest payback. Rule-based keyword filters catch obvious mismatches; <\/span>AI resume parsing<\/b> and shortlisting go further by ranking candidates against the actual job requirements, not just keyword density. Startups running high applicant volume against a small team (5:1 or worse recruiter-to-req ratios) see the largest relative gain here, since screening scales linearly with volume and recruiter hours don’t.<\/span><\/p>\n

Setup consideration: parsing accuracy depends on how well the job requirements are structured before the first resume ever arrives. A vague job description produces vague shortlists no matter how good the AI is. Teams that see the best results spend 20\u201330 minutes upfront defining must-have versus nice-to-have criteria before turning screening over to automation\u00a0 skipping that step is the single most common reason automated shortlists disappoint on the first job req.<\/span><\/p>\n

There’s a bias-and-compliance angle here too. Manual screening at 30\u201390 seconds per resume leaves enormous room for inconsistent, unstructured judgment calls between recruiters and even between candidates reviewed by the same recruiter on different days. A properly configured <\/span>candidate database management<\/b> system applies the same criteria to every applicant, which is easier to document and defend if a hiring decision is ever questioned\u00a0 provided the criteria themselves are reviewed periodically for disparate impact.<\/span><\/p>\n

2. Interview Scheduling<\/b><\/h3>\n

Manual cost:<\/b> 5\u201315 hours per week, per recruiter.<\/span><\/p>\n

Coordinating a single interview across a hiring manager’s calendar, a panel’s availability, and a candidate’s timezone takes 30 minutes to 2 hours when done over email. <\/span>AI interview scheduling<\/b><\/a> tools remove this by reading calendar availability directly and letting candidates self-select a slot from pre-approved windows. For high-volume hourly or entry-level hiring, batch scheduling (fixed interview blocks, e.g., every Tuesday 10am\u20131pm) removes coordination almost entirely and tends to improve show-up rates because candidates commit to a specific slot rather than an open-ended “let’s find a time.”<\/span><\/p>\n

Calendar integration is the technical dependency most teams underestimate here. Scheduling automation is only as good as its connection to Outlook or Google Calendar; if hiring managers keep a second, unsynced calendar for interviews, the tool will offer times that are already booked, and recruiters end up doing manual cleanup anyway. Confirming calendar sync across every interviewer before rollout avoids the most common complaint about scheduling automation in the first month.<\/span><\/p>\n

3. Candidate Status Update Emails<\/b><\/h3>\n

Manual cost:<\/b> 3\u20136 hours per week across an active pipeline.<\/span><\/p>\n

Candidates who don’t hear back within a week routinely disengage, and manually updating 150+ candidates per role on where they stand is unrealistic for most recruiters. Automated, stage-triggered <\/span>recruitment email templates<\/b><\/a>\u00a0 “application received,” “moved to interview,” “in final review”\u00a0 keep candidates informed without a recruiter typing the same update forty times a week. This is separate from rejection notices (task 6) because status updates fire mid-pipeline, not at the close of a req.<\/span><\/p>\n

4. Interview and Task Reminders<\/b><\/h3>\n

Manual cost:<\/b> 2\u20134 hours per week.<\/span><\/p>\n

Reminder emails and texts to candidates and hiring managers ahead of interviews reduce no-show rates. One documented case saw no-shows drop from 31% to 8% after automating this single step. Manually sending reminders doesn’t scale past a handful of interviews a week; automated, time-triggered reminders do it identically whether there are 5 interviews or 500.<\/span><\/p>\n

5. Recruiting Reports and Pipeline Analytics<\/b><\/h3>\n

Manual cost:<\/b> 4\u20138 hours per week for a hiring manager or TA lead.<\/span><\/p>\n

Pulling time-to-hire, source effectiveness, offer-acceptance rate, and recruiter workload into a spreadsheet by hand is slow and usually out of date by the time it’s presented. Recruitment analytics dashboards that pull live data directly from the pipeline remove the manual export-and-format cycle and let hiring managers see bottlenecks (a stalled stage, a slow interviewer) while there’s still time to fix them, not after the req has been open for 60 days.<\/span><\/p>\n

\"recruiter<\/p>\n

6. Rejection Notices<\/b><\/h3>\n

Manual cost:<\/b> 2\u20135 hours per week.<\/span><\/p>\n

Sending individual rejection emails to 90%+ of an applicant pool is both time-consuming and the most commonly skipped step\u00a0 which is exactly why 61% of job seekers report being ghosted after an interview. Automated, templated (but not robotic-sounding) rejection notices, triggered the moment a candidate is moved out of consideration, protect employer brand at a fraction of the manual time cost, and they close the loop candidates are explicitly asking for: over three-quarters of job seekers say they want visibility into their application status regardless of outcome.<\/span><\/p>\n

7. Onboarding Handoff<\/b><\/h3>\n

Manual cost:<\/b> 2\u20134 hours per hire.<\/span><\/p>\n

The handoff from recruiter to hiring manager to HR\u00a0 offer letter, background check status, start-date paperwork, IT provisioning requests\u00a0 is where hires quietly fall through the cracks between systems. Automating the handoff as a triggered workflow (offer accepted \u2192 onboarding checklist auto-generated \u2192 relevant teams notified) removes the manual relay race and the delays that come with it.<\/span><\/p>\n

Total manual time reclaimed across all seven tasks: roughly 23\u201357 hours per week for a team running 3\u20135 concurrent open roles, the<\/b> equivalent of adding half a recruiter’s capacity back to the team without a new hire.<\/span><\/p>\n

Integration, Data, and Compliance Considerations Before You Automate<\/b><\/h3>\n

Automating these seven tasks isn’t purely a software decision; three practical considerations determine whether it works cleanly or creates new problems.<\/span><\/p>\n

Integration depth.<\/b> Point tools that don’t talk to each other (a scheduling app that doesn’t update the ATS, an email tool that doesn’t log to the candidate record) recreate manual work at the handoff points between them. An integrated <\/span>applicant tracking system<\/b><\/a> where screening, scheduling, communication, and reporting share one candidate record removes this failure mode entirely, since there’s no second system to keep in sync.<\/span><\/p>\n

Data retention and candidate privacy.<\/b> Automated systems store far more candidate data, more consistently, than manual spreadsheets ever did\u00a0 which is a benefit for reporting but a responsibility for compliance. Retention periods for rejected-candidate data vary by jurisdiction (commonly 6 months to 3 years), and any automation vendor should let you configure deletion schedules rather than retaining data indefinitely by default.<\/span><\/p>\n

Cost structure.<\/b> Recruiting automation platforms are typically priced per seat, per hire, or as a flat monthly fee; a handful, including some ATS platforms built for startups and SMBs, now offer core automation (screening, scheduling, status emails) on a free tier with no per-recruiter fee. For a team evaluating a paid platform against payroll costs, the earlier calculation is worth repeating: 20+ hours a week in reclaimed recruiter time at a fully loaded cost of roughly $35\u201350 an hour puts the value of automation well into five figures annually for a small team, which is usually more than the platform costs outright.<\/span><\/p>\n

Automation Maturity Self-Assessment<\/b><\/h3>\n

Score one point for each that’s true of your current process:<\/span><\/p>\n

    \n
  1. Resumes are screened or ranked by software before a human opens them.<\/span><\/li>\n
  2. Interview scheduling requires zero manual back-and-forth emails.<\/span><\/li>\n
  3. Candidates receive automatic status updates at every pipeline stage.<\/span><\/li>\n
  4. Interview and task reminders fire without a recruiter sending them.<\/span><\/li>\n
  5. Recruiting reports update in real time without manual data pulls.<\/span><\/li>\n
  6. Every rejected candidate receives a notice without a recruiter typing it individually.<\/span><\/li>\n
  7. Onboarding tasks trigger automatically once an offer is accepted.<\/span><\/li>\n<\/ol>\n

    0\u20132:<\/b> Manual-first. Most of the week goes to admin, not recruiting. <\/span>3\u20135:<\/b> Partially automated. Automation exists but has gaps that still eat hours. <\/span>6\u20137:<\/b> Automation-mature. Recruiter time is going toward sourcing, candidate relationships, and hiring manager strategy\u00a0 the work that actually needs a human.<\/span><\/p>\n

    \"recruitment<\/p>\n

    Case Studies: What Automating These Tasks Looks Like in Practice<\/b><\/h2>\n

    A 40-person SaaS <\/span>startup hiring<\/b><\/a> for eight roles simultaneously was manually screening roughly 1,200 applications a month across two recruiters. Screening alone was consuming an estimated 80 hours of combined recruiter time monthly, leaving almost no time for sourcing passive candidates or building relationships with hiring managers.\u00a0<\/span><\/p>\n

    After automating resume screening and interview scheduling, screening time per role dropped from an estimated 10 hours to under 2, and average time-to-fill for individual contributor roles fell from 41 days to under 30 within two hiring cycles. The two recruiters redirected the reclaimed hours toward outbound sourcing, which had previously been the first task cut whenever volume spiked.<\/span><\/p>\n

    A 15-person recruiting team at a mid-market services company automated status emails, reminders, and rejection notices as a single triggered workflow rather than three separate tools. Candidate ghosting complaints on the company’s employer review pages dropped noticeably within one quarter, and the team recovered an estimated 10\u201312 hours per recruiter per week that had previously gone to manual candidate communication.\u00a0<\/span><\/p>\n

    Notably, the team reported no measurable drop in candidate satisfaction scores after switching from individually written emails to templated, stage-triggered ones\u00a0 the templates had been edited for tone before launch, which the team credited as the reason the switch didn’t feel impersonal to candidates.<\/span><\/p>\n

    Comparison: Manual Process vs. Workflow Automation vs. Full ATS Automation<\/b><\/h2>\n

    Not every team needs to automate all seven tasks at once, and not every automation approach delivers the same result. The table below compares the three common setups teams land in, since the difference between them explains most of the variation in outcomes across the case studies above.<\/span><\/p>\n\n\n\n\n\n\n
    Approach<\/b><\/td>\nTime Cost per Week<\/b><\/td>\nCandidate Experience<\/b><\/td>\nBest Fit<\/b><\/td>\n<\/tr>\n
    Fully manual<\/span><\/td>\n25\u201340+ hours on admin alone<\/span><\/td>\nInconsistent, delay-prone<\/span><\/td>\nVery low volume (1\u20132 open roles)<\/span><\/td>\n<\/tr>\n
    Point-solution automation (scheduling tool only, email tool only)<\/span><\/td>\n10\u201320 hours saved, gaps remain between tools<\/span><\/td>\nImproves in the automated step, inconsistent elsewhere<\/span><\/td>\nTeams testing automation before committing<\/span><\/td>\n<\/tr>\n
    Integrated <\/span>recruitment workflow automation<\/b> (screening + scheduling + emails + reporting in one system)<\/span><\/td>\n20\u201335+ hours saved<\/span><\/td>\nConsistent across every stage<\/span><\/td>\nStartups and SMBs scaling hiring volume<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Point solutions solve one bottleneck and leave the rest of the pipeline manual. Integrated automation inside a single <\/span>job posting software<\/b><\/a> and ATS platform removes the handoff gaps between tools, which is usually where the remaining manual hours are hiding. Teams moving from row one to row three directly, rather than stopping at row two, consistently report the largest time recovery because they never rebuild the same manual bridge between disconnected tools.<\/span><\/p>\n

    What Most Teams Get Wrong<\/b><\/h2>\n

    Most teams treat automation as a feature they’ll “turn on later,” not a process they need to design. The most common mistake isn’t choosing the wrong software, it’s buying automation-capable tools and never configuring the workflows inside them, which is functionally the same as not having automation at all.<\/span><\/p>\n

    The second mistake is automating candidate-facing communication without checking the tone. A status update or rejection notice that reads like a form letter does more brand damage than a slightly slower manual one. Templates need editing before they go live, not after candidates start replying to complain.<\/span><\/p>\n

    The third, less obvious mistake: automating reporting before automating the pipeline stages that feed it. Analytics on a partially manual process just produce fast, confident numbers about a broken workflow. Fix the upstream steps first.<\/span><\/p>\n

    A fourth pattern worth naming: teams often automate the tasks that are easiest to automate rather than the ones costing the most hours. Reminders are simple to set up and get automated first; screening, which usually carries the largest time cost, gets pushed to “phase two” because it feels riskier to hand off.\u00a0<\/span><\/p>\n

    The self-assessment above exists specifically to redirect that instinct to rank tasks by hours saved, not by setup difficulty, and the highest-impact automation usually turns out to be resume screening or interview scheduling, not the reminder emails teams reach for first.<\/span><\/p>\n

    \"automation<\/p>\n

    Where to Start<\/b><\/h2>\n

    If your team is scoring 0\u20133 on the self-assessment above, the fastest path forward isn’t a full platform migration; it’s picking the one or two tasks costing you the most hours (usually screening and scheduling) and automating those first before touching reporting or onboarding.<\/span><\/p>\n

    Setup Tips for Rolling Out Recruitment Workflow Automation<\/b><\/h3>\n

    A few practical steps make the rollout smoother regardless of which platform a team chooses:<\/span><\/p>\n

      \n
    1. Start with one job requisition, not the whole pipeline.<\/b> Configure screening and scheduling rules against a single active role, confirm the shortlist quality, then extend the same rules to other open reqs.<\/span><\/li>\n
    2. Write the job requirements before turning on AI screening.<\/b> Automated shortlists are only as accurate as the must-have criteria fed into them.<\/span><\/li>\n
    3. Sync every interviewer’s calendar before enabling self-service scheduling.<\/b> A single unsynced calendar undermines confidence in the whole system within the first week.<\/span><\/li>\n
    4. Edit the default email and rejection templates for tone before launch.<\/b> Generic templates are the fastest way to make automation feel impersonal to candidates.<\/span><\/li>\n
    5. Turn on reporting last, once the upstream stages are stable<\/b>, so the dashboards reflect a working process rather than a partially manual one.<\/span><\/li>\n<\/ol>\n

      In Hirium’s setup flow specifically, these steps map to configuring the job’s screening criteria first, connecting calendars during onboarding, and reviewing the default candidate-facing templates before a role goes live, a sequence most teams complete in under a day for a single req.<\/span><\/p>\n

      Hirium’s workflow automation covers all seven tasks above\u00a0 AI screening, self-service scheduling, triggered status and rejection emails, and real-time reporting\u00a0 inside one <\/span>candidate database<\/b><\/a>, with a free-forever plan and no recruiter fees. If you’re evaluating where to start, the self-assessment above is a reasonable first step before comparing vendors.<\/span><\/p>\n

      \"time-to-fill<\/p>\n

      FAQ<\/b><\/h2>\n

      What recruiting tasks can actually be automated?\u00a0<\/b><\/h3>\n

      Resume screening, interview scheduling, candidate status updates, reminders, reporting, rejection notices, and onboarding handoff are the seven tasks with the clearest automation payback. Sourcing and final hiring decisions generally still require human judgment, though AI tools can support both.<\/span><\/p>\n

      Is recruitment workflow automation worth it for a small team hiring for just 2\u20133 roles?\u00a0<\/b><\/h3>\n

      Yes, though the return scales with volume. A team hiring for one role a quarter will see modest time savings from recruitment workflow automation; a team running 5+ concurrent reqs will typically recover 20+ hours a week, which is closer to adding another recruiter’s worth of capacity.<\/span><\/p>\n

      How much time does automation actually save recruiters?\u00a0<\/b><\/h3>\n

      Documented ranges across screening, scheduling, and candidate communication put total savings between 20 and 55 hours per week for a small-to-mid-size recruiting team, depending on applicant volume and how many of the seven tasks are automated.<\/span><\/p>\n

      What’s the difference between an ATS and workflow automation?\u00a0<\/b><\/h3>\n

      An ATS stores and tracks candidate data. <\/span>Workflow automation<\/b><\/a> is the layer that acts on that data\u00a0 triggering emails, scheduling interviews, and generating reports without manual input. A modern ATS should include both, not just the database.<\/span><\/p>\n

      Does automating recruiting hurt the candidate experience?\u00a0<\/b><\/h3>\n

      Not when it’s configured well. Automated status updates and rejection notices generally improve candidate experience because candidates hear back faster and more consistently than they would from manual, ad hoc communication. The risk is templated messages that sound robotic\u00a0 that’s a tone problem, not an automation problem.<\/span><\/p>\n

      How do I know if my hiring process needs automation?\u00a0<\/b><\/h3>\n

      Score yourself against the seven-task self-assessment above. A score of 0\u20133 means most of your recruiting week is going to admin work rather than recruiting itself, which is the clearest sign automation is overdue.<\/span><\/p>\n

      Can free tools handle recruitment workflow automation, or do I need an expensive platform?\u00a0<\/b><\/h3>\n

      Several ATS platforms, including free-tier options, now include AI screening, scheduling, and automated candidate communication without additional recruiter fees. Cost is no longer the main barrier to automating these tasks; configuration time is.<\/span><\/p>\n

      How long does it take to fully automate a hiring workflow?\u00a0<\/b><\/h3>\n

      Automating one or two high-impact tasks, like screening and scheduling, typically takes a few days of setup once job requirements and calendars are configured correctly. Automating all seven tasks end to end, including reporting and onboarding handoff, usually takes 2\u20134 weeks for a small team to fully roll out and refine.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

      A recruiter screening 200 applications by hand spends 5 to 15 hours on that single job req before a single interview is booked. Multiply that across six open roles and the math stops being a productivity question\u00a0 it becomes a hiring capacity problem. Recruitment workflow automation is not about replacing recruiters. It’s about deciding which […]<\/p>\n","protected":false},"author":3,"featured_media":1441,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-1440","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-in-recruitment"],"_links":{"self":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/comments?post=1440"}],"version-history":[{"count":1,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1440\/revisions"}],"predecessor-version":[{"id":1447,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1440\/revisions\/1447"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media\/1441"}],"wp:attachment":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media?parent=1440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/categories?post=1440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/tags?post=1440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}