{"id":1257,"date":"2026-05-24T10:18:02","date_gmt":"2026-05-24T17:18:02","guid":{"rendered":"https:\/\/www.eckmandesign.com\/blog\/?p=1257"},"modified":"2026-05-30T09:32:36","modified_gmt":"2026-05-30T16:32:36","slug":"api-integration-for-business-process-ownership","status":"publish","type":"post","link":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/","title":{"rendered":"API Integrations Break When Nobody Owns The Process"},"content":{"rendered":"\n

API integration for business fails when teams connect systems before they define the process those systems are supposed to support.<\/p>\n\n\n\n

An API integration is not just a technical connection. It is a business handoff between two systems.<\/p>

The integration needs owners, triggers, source-of-truth rules, duplicate handling, and exception paths before it can be trusted.<\/p>

Good API integration for business starts with the workflow, then chooses the endpoints and data fields.<\/p>

The goal is not to move data faster. The goal is to move the right data through the right process with fewer hidden failures.<\/p><\/blockquote>\n\n\n\n

API integration work often starts with a reasonable request: connect the CRM to the billing tool, send form leads into the project system, push fulfillment updates into the customer portal, or sync support tickets with a knowledge base. The request sounds technical because APIs are involved.<\/p>\n\n\n\n

However, the failure usually starts before the endpoint. The team has not decided which system owns the record, which event should trigger the sync, what counts as a duplicate, who reviews errors, or what happens when one system accepts a value the other system rejects.<\/p>\n\n\n\n

That is why API integration for business should start as process design. The integration may require code, credentials, webhooks, queues, and monitoring, but the business problem is still about how work moves between systems.<\/p>\n\n\n\n

An API connection is a workflow handoff.<\/h2>\n\n\n\n

An API connection is a workflow handoff because one system is asking another system to accept, change, or return information. The handoff needs the same operational clarity as a human handoff: trigger, input, owner, rule, and exception path.<\/p>\n\n\n\n

For example, a website lead form may create a CRM record. The CRM may assign an owner, send a notification, and trigger a follow-up sequence. Later, a qualified opportunity may create a project workspace and a billing customer. That chain is not just data movement. It is the operating path from interest to delivery.<\/p>\n\n\n\n

If the form sends incomplete fields, the CRM creates duplicates, and the project system receives unqualified work, the integration will look successful while the workflow creates more cleanup. The systems are connected, but the business process is not designed.<\/p>\n\n\n\n

This is the same pattern that appears in manual work. Eckman Design covered the human version in Manual Handoffs Make The Best Workflow Automation Examples<\/a>. API integrations are system handoffs, so the same discipline applies.<\/p>\n\n\n\n

The source of truth must be decided before data moves.<\/h2>\n\n\n\n

The source of truth must be decided before data moves because two connected systems can disagree faster than two disconnected systems. An integration can copy bad data, overwrite useful context, or create circular updates when ownership rules are missing.<\/p>\n\n\n\n

A practical integration plan should name which system owns each record and field. The CRM might own the customer relationship. The billing tool might own payment status. The project system might own delivery milestones. The support system might own service history. A dashboard may summarize all of them, but it should not become the hidden source of truth.<\/p>\n\n\n\n

This ownership map protects the business from a common failure: every system has a slightly different version of the same customer, project, invoice, or ticket. When that happens, people stop trusting automation and go back to screenshots, spreadsheets, and private notes.<\/p>\n\n\n\n

Eckman Design has written about the trust problem in Your CRM Is Not the System of Record If Nobody Trusts It<\/a>. API integrations make that problem more visible because they expose whether the organization actually knows where truth lives.<\/p>\n\n\n\n

Reliable integrations need duplicate and retry rules.<\/h2>\n\n\n\n

Reliable integrations need duplicate and retry rules because system-to-system work does not happen in a perfect environment. Requests time out, users submit forms twice, webhooks retry, network conditions change, and one system may process a request after another system thinks the attempt failed.<\/p>\n\n\n\n

Technical teams use patterns such as idempotency to make repeated requests safer. Stripe’s idempotent request documentation<\/a> explains how a client can use an idempotency key so repeated requests do not accidentally create duplicate operations. The business lesson is broader: every important integration needs a plan for retries, duplicate detection, and safe recovery.<\/p>\n\n\n\n

The business does not need to know every implementation detail. The business does need to answer operational questions before the integration goes live.<\/p>\n\n\n\n

Integration Question<\/th>Operational Risk If Missing<\/th>Better Rule<\/th><\/tr><\/thead>
What makes a record unique?<\/td>Duplicate customers, tickets, or projects appear.<\/td>Define matching keys and merge behavior.<\/td><\/tr>
What happens when a request fails?<\/td>People do not know whether work moved.<\/td>Create retry, alert, and review rules.<\/td><\/tr>
Which system can overwrite a field?<\/td>Good data gets replaced by stale data.<\/td>Assign field-level ownership.<\/td><\/tr>
Who reviews integration errors?<\/td>Failures sit inside logs nobody reads.<\/td>Create an exception queue with an owner.<\/td><\/tr>
When should the integration stop?<\/td>Bad data spreads across systems.<\/td>Pause on risky conditions and ask for review.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Exceptions need an operating path, not just logs.<\/h2>\n\n\n\n

Exceptions need an operating path because logs alone do not run the business. A failed API request may be visible to a developer, but the operational impact belongs to sales, support, finance, delivery, or leadership. If no one owns the exception, the business discovers the failure through customer confusion.<\/p>\n\n\n\n

A useful exception path should explain what happened, what record is affected, which system has the current state, who owns the next action, and whether the work can continue manually. The team should not need to decode raw error messages during a customer-facing problem.<\/p>\n\n\n\n

This is also where a narrow internal tool can beat another general-purpose subscription. A simple admin surface that shows failed syncs, duplicate candidates, blocked records, and retry status can make an integration usable for the people who operate the workflow. Eckman Design covered the broader build-versus-buy pattern in Internal Tools Are Often Better Than Another SaaS Subscription<\/a>.<\/p>\n\n\n\n

A business-ready integration has five owners.<\/h2>\n\n\n\n

A business-ready integration usually needs five ownership decisions. These decisions keep the integration from becoming a hidden technical dependency that only gets attention when something breaks.<\/p>\n\n\n\n

  1. Workflow owner: the person responsible for the business process the integration supports.<\/li>
  2. Source owner: the person responsible for the quality of the originating data.<\/li>
  3. Destination owner: the person responsible for how received data is used.<\/li>
  4. Exception owner: the person responsible for blocked, duplicate, or failed records.<\/li>
  5. Technical owner: the person responsible for credentials, monitoring, code, and vendor changes.<\/li><\/ol>\n\n\n\n

    One person can hold more than one role in a small business, but the roles still need names. When ownership is implicit, the integration becomes fragile. When ownership is explicit, the integration becomes part of the operating model.<\/p>\n\n\n\n

    Connect systems only after the workflow is explainable.<\/h2>\n\n\n\n

    The safest integration work starts with an explainable workflow. The team should be able to describe the trigger, the record, the owner, the source system, the destination system, the validation rules, the exception path, and the success metric before the API work begins.<\/p>\n\n\n\n

    That approach does not slow the project down. It prevents the project from producing a fast connection that creates slow cleanup. The integration becomes easier to test because the team knows what correct behavior looks like.<\/p>\n\n\n\n

    If your systems are connected but your team still reconciles records by hand, the problem may not be the API. The problem may be that the process was never owned clearly enough for the integration to work.<\/p>\n\n\n\n

    Eckman Design helps teams turn disconnected tools, manual handoffs, and fragile data movement into practical systems that are easier to operate.<\/p>\n","protected":false},"excerpt":{"rendered":"

    API integration for business fails when teams connect tools before defining owners, triggers, duplicate handling, exceptions, and source-of-truth rules.<\/p>\n","protected":false},"author":2,"featured_media":1264,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[71],"tags":[118,119,98,67,62,74],"class_list":["post-1257","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-systems","tag-api-integration","tag-api-integration-for-business","tag-business-workflow-software","tag-digital-operations","tag-operational-design","tag-software-systems"],"yoast_head":"\nAPI Integration For Business Needs Process Ownership<\/title>\n<meta name=\"description\" content=\"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"API Integration For Business Needs Process Ownership\" \/>\n<meta property=\"og:description\" content=\"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/\" \/>\n<meta property=\"og:site_name\" content=\"Eckman Design\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-24T17:18:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-30T16:32:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-featured.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"900\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Chris Eckman\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@eckmandesign\" \/>\n<meta name=\"twitter:site\" content=\"@eckmandesign\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Chris Eckman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/\"},\"author\":{\"name\":\"Chris Eckman\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cfa32ec7412d4f546a33e3a8f110ff1b\"},\"headline\":\"API Integrations Break When Nobody Owns The Process\",\"datePublished\":\"2026-05-24T17:18:02+00:00\",\"dateModified\":\"2026-05-30T16:32:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/\"},\"wordCount\":1239,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/api-integration-for-business-process-ownership-v2-featured.webp\",\"keywords\":[\"API Integration\",\"API Integration For Business\",\"Business Workflow Software\",\"Digital Operations\",\"Operational Design\",\"Software Systems\"],\"articleSection\":[\"Software Systems\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/\",\"name\":\"API Integration For Business Needs Process Ownership\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/api-integration-for-business-process-ownership-v2-featured.webp\",\"datePublished\":\"2026-05-24T17:18:02+00:00\",\"dateModified\":\"2026-05-30T16:32:36+00:00\",\"description\":\"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/api-integration-for-business-process-ownership-v2-featured.webp\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/api-integration-for-business-process-ownership-v2-featured.webp\",\"width\":1600,\"height\":900,\"caption\":\"API integration for business shown as a technical blueprint with systems, ownership gates, retries, and error paths\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/api-integration-for-business-process-ownership\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"API Integrations Break When Nobody Owns The Process\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\",\"name\":\"Eckman Design\",\"description\":\"AI Automation Software & Workflow Systems\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\",\"name\":\"Eckman Design, LLC.\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/04\\\/eckman_design_twitter_card.png\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/04\\\/eckman_design_twitter_card.png\",\"width\":1200,\"height\":630,\"caption\":\"Eckman Design, LLC.\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/Eckman-Design-913317988788314\\\/\",\"https:\\\/\\\/x.com\\\/eckmandesign\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cfa32ec7412d4f546a33e3a8f110ff1b\",\"name\":\"Chris Eckman\",\"sameAs\":[\"https:\\\/\\\/www.eckmandesign.com\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"API Integration For Business Needs Process Ownership","description":"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.","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:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/","og_locale":"en_US","og_type":"article","og_title":"API Integration For Business Needs Process Ownership","og_description":"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.","og_url":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/","og_site_name":"Eckman Design","article_publisher":"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","article_published_time":"2026-05-24T17:18:02+00:00","article_modified_time":"2026-05-30T16:32:36+00:00","og_image":[{"width":1600,"height":900,"url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-featured.webp","type":"image\/webp"}],"author":"Chris Eckman","twitter_card":"summary_large_image","twitter_creator":"@eckmandesign","twitter_site":"@eckmandesign","twitter_misc":{"Written by":"Chris Eckman","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#article","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/"},"author":{"name":"Chris Eckman","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/cfa32ec7412d4f546a33e3a8f110ff1b"},"headline":"API Integrations Break When Nobody Owns The Process","datePublished":"2026-05-24T17:18:02+00:00","dateModified":"2026-05-30T16:32:36+00:00","mainEntityOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/"},"wordCount":1239,"commentCount":0,"publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-v2-featured.webp","keywords":["API Integration","API Integration For Business","Business Workflow Software","Digital Operations","Operational Design","Software Systems"],"articleSection":["Software Systems"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/","url":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/","name":"API Integration For Business Needs Process Ownership","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#primaryimage"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-v2-featured.webp","datePublished":"2026-05-24T17:18:02+00:00","dateModified":"2026-05-30T16:32:36+00:00","description":"API integration for business needs process ownership, clear triggers, duplicate handling, source rules, and exception paths.","breadcrumb":{"@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#primaryimage","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-v2-featured.webp","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/api-integration-for-business-process-ownership-v2-featured.webp","width":1600,"height":900,"caption":"API integration for business shown as a technical blueprint with systems, ownership gates, retries, and error paths"},{"@type":"BreadcrumbList","@id":"https:\/\/www.eckmandesign.com\/blog\/api-integration-for-business-process-ownership\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.eckmandesign.com\/blog\/"},{"@type":"ListItem","position":2,"name":"API Integrations Break When Nobody Owns The Process"}]},{"@type":"WebSite","@id":"https:\/\/www.eckmandesign.com\/blog\/#website","url":"https:\/\/www.eckmandesign.com\/blog\/","name":"Eckman Design","description":"AI Automation Software & Workflow Systems","publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.eckmandesign.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.eckmandesign.com\/blog\/#organization","name":"Eckman Design, LLC.","url":"https:\/\/www.eckmandesign.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2016\/04\/eckman_design_twitter_card.png","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2016\/04\/eckman_design_twitter_card.png","width":1200,"height":630,"caption":"Eckman Design, LLC."},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","https:\/\/x.com\/eckmandesign"]},{"@type":"Person","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/cfa32ec7412d4f546a33e3a8f110ff1b","name":"Chris Eckman","sameAs":["https:\/\/www.eckmandesign.com\/"]}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/comments?post=1257"}],"version-history":[{"count":0,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1257\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media\/1264"}],"wp:attachment":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media?parent=1257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/categories?post=1257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/tags?post=1257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}