Answers.Body: <p>I haven't seen anything that does what you are asking. Since you're running headless Craft, it seems safe to assume that you have a public API that could return <strong>CMS A</strong> Glossary Terms. You could then write a custom field type, via a module/plugin installed on <strong>CMS B</strong>, that hits the <strong>CMS A</strong> API endpoint and displays the resulting glossary terms in a dropdown field, for example.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-28T17:12:01.233Z
Answers.Text: Interesting workaround.  Excellent idea.  Yes, indeed it is serving over graphQL.  Is that "populate a dropdown with response from external API" behavior something configurable via some existing plugin, or are you suggesting one would need to develop a new plugin to make this do?
Answers.UserDisplayName: blnkt
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-28T17:17:57.290Z
Answers.Text: Oooo, this is looking very much "in the ballpark": https://plugins.craftcms.com/feed-me
Answers.UserDisplayName: blnkt
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-28T18:12:12.183Z
Answers.Text: I was suggesting developing a custom plugin for the custom field type.
Answers.UserDisplayName: Ben Croker
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-27T10:55:37.663Z
Answers.LastActivityDate: 2022-01-27T10:55:37.663Z
Answers.UserDisplayName: Ben Croker
Body: <p>I am not asking about <a href="https://craftcms.com/docs/3.x/sites.html" rel="nofollow noreferrer">multi-site</a>.  Rather, I am curious if there is existing support for &quot;sharing&quot; data across unique Craft 3 installs.</p>
  <p>For instance, let's say he have 2 Craft 3 installs running as headless CMS.  <strong>Craft CMS A</strong> has a Glossary Section with Glossary Term Entries, each Entry localized in English and Spanish.  <strong>Craft CMS B</strong> has a News Section with News Post Entries, each Entry localized in English and Spanish.  If these Sections were in the same CMS it would be trivial to include hyperlinks to Glossary Terms in a News Post.  But how can I include hyperlinks to <strong>CMS A</strong> Glossary Terms in <strong>CMS B</strong> News Posts?  Is there native, or existing plugin for creating a &quot;connection&quot; between separate Craft CMS Sections &amp; Entries?  I think I'm looking for something like the <a href="https://nystudio107.com/docs/connect/" rel="nofollow noreferrer">Connect plugin</a> but at the CMS Dashboard level, rather than in Twig templating.</p>
  
Tags: <craft3><plugins><database>
Title: Sharing data between Multiple Craft 3 CMS instances
ThreadText: # Sharing data between Multiple Craft 3 CMS instances
  
  (Asked by: username_0 on 2022-01-26)
  
  I am not asking about [multi-site](https://craftcms.com/docs/3.x/sites.html). Rather, I am curious if there is existing support for "sharing" data across unique Craft 3 installs.
  
  For instance, let's say he have 2 Craft 3 installs running as headless CMS. **Craft CMS A** has a Glossary Section with Glossary Term Entries, each Entry localized in English and Spanish. **Craft CMS B** has a News Section with News Post Entries, each Entry localized in English and Spanish. If these Sections were in the same CMS it would be trivial to include hyperlinks to Glossary Terms in a News Post. But how can I include hyperlinks to **CMS A** Glossary Terms in **CMS B** News Posts? Is there native, or existing plugin for creating a "connection" between separate Craft CMS Sections & Entries? I think I'm looking for something like the [Connect plugin](https://nystudio107.com/docs/connect/) but at the CMS Dashboard level, rather than in Twig templating.
  
  **Tags:** craft3, plugins, database
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-01-27. Score: 1
  
  I haven't seen anything that does what you are asking. Since you're running headless Craft, it seems safe to assume that you have a public API that could return **CMS A** Glossary Terms. You could then write a custom field type, via a module/plugin installed on **CMS B**, that hits the **CMS A** API endpoint and displays the resulting glossary terms in a dropdown field, for example.
  
  > **Comments:**
  > **username_0**: Interesting workaround.  Excellent idea.  Yes, indeed it is serving over graphQL.  Is that "populate a dropdown with response from external API" behavior something configurable via some existing plugin, or are you suggesting one would need to develop a new plugin to make this do?  
  > **username_0**: Oooo, this is looking very much "in the ballpark": https://plugins.craftcms.com/feed-me  
  > **username_1**: I was suggesting developing a custom plugin for the custom field type.  
  
  ---
  
  