Answers.Body: <p>Yes, there is a very capable API - see <a href="https://docs.civicrm.org/dev/en/latest/api/" rel="nofollow noreferrer">https://docs.civicrm.org/dev/en/latest/api/</a> (Use APIv4 for any new work.)</p>
  <p>Your process could continue as is and the very last part 'store it on our systems' would use the API to create the membership (and maybe contact as well).</p>
  <p>Alternatively you could look the <a href="https://docs.civicrm.org/formprocessor/en/latest/" rel="nofollow noreferrer">FormProcessor</a> extension to process the form data.</p>
  <p>If you are open to changing the first 3 steps, then look at the <a href="https://github.com/CiviMRF/documentation" rel="nofollow noreferrer">CiviMRF</a> extension (also works with FormProcessor).</p>
  <p>Another option to consider is <a href="https://lab.civicrm.org/extensions/inlayfp" rel="nofollow noreferrer">Inlay &amp; FormProcessor</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-17T11:12:22.683Z
Answers.Text: Maybe add CiviProxy? https://docs.civicrm.org/civiproxy/en/latest/
Answers.UserDisplayName: nielo
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-17T09:15:54.813Z
Answers.LastActivityDate: 2024-04-17T09:15:54.813Z
Answers.UserDisplayName: Aidan
Body: <p>We are evaluating the use of civicrm. Regarding data security we have a need vor very high standards, so the policy is never to store any personal information on a computer that is directly accessible from the web for a prolonged amount amount of time.</p>
  <p>Usually what we do with form entries is:</p>
  <ul>
  <li>on submit: encrypt it (using asynchronous encryption)</li>
  <li>store the encrypted data to a dedicated folder</li>
  <li>have our internal systems pull the data from there every other minutes to our internal systems and delete it from the server thereafter</li>
  <li>decrypt and store it on our systems</li>
  </ul>
  <p>Usually we use a RestAPI system to perform whichever task would otherwise be performed by the (live) form on the website to store the data locally.</p>
  <p><strong>Now, we would like to know: is there a proper/testet/conceivable way to make this happen with civicrm, esp. is there a proper API interface for civicim, and how cumbersome would that probably be?</strong></p>
  <p>I'd appreciate any input and advice greatly!</p>
  
Tags: <api>
Title: membership application form w/o access to civicim
ThreadText: # membership application form w/o access to civicim
  
  (Asked by: username_0 on 2024-04-13)
  
  We are evaluating the use of civicrm. Regarding data security we have a need vor very high standards, so the policy is never to store any personal information on a computer that is directly accessible from the web for a prolonged amount amount of time.
  
  Usually what we do with form entries is:
  
  * on submit: encrypt it (using asynchronous encryption)
  * store the encrypted data to a dedicated folder
  * have our internal systems pull the data from there every other minutes to our internal systems and delete it from the server thereafter
  * decrypt and store it on our systems
  
  Usually we use a RestAPI system to perform whichever task would otherwise be performed by the (live) form on the website to store the data locally.
  
  **Now, we would like to know: is there a proper/testet/conceivable way to make this happen with civicrm, esp. is there a proper API interface for civicim, and how cumbersome would that probably be?**
  
  I'd appreciate any input and advice greatly!
  
  **Tags:** api
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-04-17. Score: 2
  
  Yes, there is a very capable API - see <https://docs.civicrm.org/dev/en/latest/api/> (Use APIv4 for any new work.)
  
  Your process could continue as is and the very last part 'store it on our systems' would use the API to create the membership (and maybe contact as well).
  
  Alternatively you could look the [FormProcessor](https://docs.civicrm.org/formprocessor/en/latest/) extension to process the form data.
  
  If you are open to changing the first 3 steps, then look at the [CiviMRF](https://github.com/CiviMRF/documentation) extension (also works with FormProcessor).
  
  Another option to consider is [Inlay & FormProcessor](https://lab.civicrm.org/extensions/inlayfp)
  
  > **Comments:**
  > **username_2**: Maybe add CiviProxy? https://docs.civicrm.org/civiproxy/en/latest/  
  
  ---
  
  