Answers.Body: <p>As long as the Developer Guide (<a href="https://docs.civicrm.org/dev/en/latest/api/" rel="nofollow noreferrer">https://docs.civicrm.org/dev/en/latest/api/</a>) only mentions API3 I would recommned using that one.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-08T14:04:40.340Z
Answers.LastActivityDate: 2018-08-08T14:04:40.340Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>Coleman sent the following to the <a href="https://lists.civicrm.org/lists/arc/civicrm-dev/2018-07/msg00006.html" rel="nofollow noreferrer">dev list 3 weeks ago</a>.  The line I have emphasised below seems particularly relevant to your question.</p>
  
  <blockquote>
    <p>As you probably know, CiviCRM api v4 has been quietly being developed
    over in an extension. The nice thing about being in an extension is
    that we can commit code without going through the core PR process and
    iterate rapidly, but the downside is that it doesn't get as much
    attention or visibility.</p>
    
    <p>But that's about to change. I intend for CiviCRM 5.5 to ship with the
    Api4 extension bundled in the tarball. At first it will be disabled by
    default, but at some point that too will change.</p>
    
    <p>It has a test suite that is being run on a nightly basis here:
    <a href="https://test.civicrm.org/view/All/job/CiviCRM-Ext-Matrix/" rel="nofollow noreferrer">https://test.civicrm.org/view/All/job/CiviCRM-Ext-Matrix/</a> (soon I want
    api4 tests running with every core PR).</p>
    
    <p>I've now developed my first extension using api4, and I'm happy enough
    with it to start recommending that other developers give it a try. <strong>IMO
    if you are starting off writing a new extension and want to ensure
    longevity for that project, api4 is a good choice (even though we
    currently have no plans to deprecate api3, someday it may happen).</strong></p>
    
    <p>So I suggest you download the api4 extension and play around with the
    new, angular-based api explorer to have a look at what it can do (the
    explorer is not 100% feature-complete but it's still fun to play
    with). Enjoy :)</p>
  </blockquote>
  
  <p>Advantages: intended to be lots!<br>
  Disadvantages: it's new.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-08T16:07:20.623Z
Answers.Text: I will certainly have a play with it :-)
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-08T15:59:13.613Z
Answers.LastActivityDate: 2018-08-08T15:59:13.613Z
Answers.UserDisplayName: Aidan
Body: <p>What is the recommended version of API to use at this point in time? I am about to do a major rewrite of an extension to manage small groups and I want to future proof it.</p>
  
  <p>Are there any advantages/disadvantages to using API4?</p>
  
  <p>Thanks!</p>
  
Tags: <api>
Title: Use API3 or API4?
ThreadText: # Use API3 or API4?
  
  (Asked by: username_0 on 2018-08-08)
  
  What is the recommended version of API to use at this point in time? I am about to do a major rewrite of an extension to manage small groups and I want to future proof it.
  
  Are there any advantages/disadvantages to using API4?
  
  Thanks!
  
  **Tags:** api
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2018-08-08. Score: 4 | Accepted answer
  
  Coleman sent the following to the [dev list 3 weeks ago](https://lists.civicrm.org/lists/arc/civicrm-dev/2018-07/msg00006.html). The line I have emphasised below seems particularly relevant to your question.
  
  > As you probably know, CiviCRM api v4 has been quietly being developed
  > over in an extension. The nice thing about being in an extension is
  > that we can commit code without going through the core PR process and
  > iterate rapidly, but the downside is that it doesn't get as much
  > attention or visibility.
  >
  > But that's about to change. I intend for CiviCRM 5.5 to ship with the
  > Api4 extension bundled in the tarball. At first it will be disabled by
  > default, but at some point that too will change.
  >
  > It has a test suite that is being run on a nightly basis here:
  > <https://test.civicrm.org/view/All/job/CiviCRM-Ext-Matrix/> (soon I want
  > api4 tests running with every core PR).
  >
  > I've now developed my first extension using api4, and I'm happy enough
  > with it to start recommending that other developers give it a try. **IMO
  > if you are starting off writing a new extension and want to ensure
  > longevity for that project, api4 is a good choice (even though we
  > currently have no plans to deprecate api3, someday it may happen).**
  >
  > So I suggest you download the api4 extension and play around with the
  > new, angular-based api explorer to have a look at what it can do (the
  > explorer is not 100% feature-complete but it's still fun to play
  > with). Enjoy :)
  
  Advantages: intended to be lots!  
  Disadvantages: it's new.
  
  > **Comments:**
  > **username_1**: I will certainly have a play with it :-)  
  
  ---
  
  ### Answer by username_1 on 2018-08-08. Score: 3
  
  As long as the Developer Guide (<https://docs.civicrm.org/dev/en/latest/api/>) only mentions API3 I would recommned using that one.
  
  
  ---
  
  