Stanford Career Academic Profiles API integration Module

Installs: 55

Dependents: 0

Suggesters: 0

Security: 0

Stars: 5

Watchers: 14

Forks: 11

Open Issues: 35


7.3.0-beta.19 2020-10-26 16:58 UTC


Version 7.x-3.0-dev

Stanford CAP Extensible module builds on some great work. This module provides an interface for administrators to pull information directly from the CAP API into Drupal. This allows profile owners to continue to manage their profile information on the CAP web service and have that information automatically reflected into a Drupal website.

What is CAP?

CAP Network is a virtual workspace, originally created by the School of Medicine, to support collaboration among faculty, graduate students, postdocs and staff. In 2013, it was expanded in partnership with various Schools, Institutes, and administrative offices to create the Stanford Profiles website.

Combining a profile directory with a social networking backend, CAP makes it easy for you to work closely with colleagues and track the projects that matter most to you—all in a private, secure environment


Install this module like any other Drupal module.


Before you get started you will need to have authentication credentials. To get authentication credentials, submit a Help request.


For detailed documentation on the configuration and usage of this module, please see the Docs section.


GitHub page. Collaboration and bug reports are welcome. Please file bug reports on the github issues page. You are also welcome to suggest new functionality in the way of a pull request.

Also included in this package is a module called: capx_issue_collector. If you enable this module you will have a 'report feedback' button added to the bottom right hand corner of your website. This will allow you to post feedback directly to our Jira instance.



CAPx uses https for all API calls. Please follow this best practice as you develop with this module.

httpoxy mitigation:

In July 2016, the httpoxy security exploit was announced for PHP, including libraries such as Guzzle. CAPx installs were by default protected because of https usage (see above). In addition, developers are encouraged to seek their own httpoxy mitigation steps at the server level. Check with your hosting provider to ensure that your implementation is protected from httpoxy. See for details.


  • Trellon, for the original CAP module and all the problems they solved. A great amount of inspiration and information was used from this module.
  • Kenneth Sharp, for his work on CAP lite and for his contributions to functionality.
  • Zach Chandler, for his vision and direction.
  • Stanford Web Services, for putting all the pieces together.
  • CAP working group for all of their invaluable feedback and time spent.
  • Brendan Walsh and the Office of International Affairs, for their sponsorship funding this module.
  • Darryl Dieckman, for all his hard work and support on the API.