Answers.Body: <p>I think that you should call the CiviCRM API directly. This allows you direct access to the CiviCRM system.</p>
  
  <p>If you use Drupal Web Services you still would need to wrap the services around CiviCRM API calls (or direct calls if needed). </p>
  
  <p>So Drupal Web Services just adds additional complexity to something that the CiviCRM API does an excellent job of all ready.  Just use the CiviCRM API services.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-16T20:29:48.683Z
Answers.LastActivityDate: 2015-08-16T20:29:48.683Z
Answers.UserDisplayName: DaveD
Body: <p>What is recommended to collect data from CiviCRM to external Drupal application and why? <a href="https://www.drupal.org/project/services" rel="nofollow">Drupal web services</a> or <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/Using+the+API" rel="nofollow">CiviCRM API</a></p>
  
Tags: <drupal><cms-integration>
Title: What is recommended using Drupal web services or CiviCRM APIs
ThreadText: # What is recommended using Drupal web services or CiviCRM APIs
  
  (Asked by: username_0 on 2015-08-16)
  
  What is recommended to collect data from CiviCRM to external Drupal application and why? [Drupal web services](https://www.drupal.org/project/services) or [CiviCRM API](http://wiki.civicrm.org/confluence/display/CRMDOC/Using+the+API)
  
  **Tags:** drupal, cms-integration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-08-16. Score: 7 | Accepted answer
  
  I think that you should call the CiviCRM API directly. This allows you direct access to the CiviCRM system.
  
  If you use Drupal Web Services you still would need to wrap the services around CiviCRM API calls (or direct calls if needed).
  
  So Drupal Web Services just adds additional complexity to something that the CiviCRM API does an excellent job of all ready. Just use the CiviCRM API services.
  
  
  ---
  
  