api

Drupal 6 modules typically defined their own tables, had their own code to maintain them and then used nodeapi to hook into the system. Or, defined node types but still maintained their own tables. In Drupal 7 instead you should just create fields, instance them on node types you want to work with. Instead of altering a form directly you can write a widget. Display your data with a formatter. Don't worry about data storage, field API handles that for you. And then there is the EntityFieldQuery class to help with finding things.

This module introduces a common repository for libraries in sites/all/libraries resp. sites//libraries for contributed modules.

An API is an abstraction that defines and describes an interface for the interaction with a set of functions used by components of a software system. The software that provides the functions that are described by an API is said to be an implementation of the API.

The permissions_api module provides a method for granting and revoking permissions for a given role. This module helps with the issue of staging a Drupal site across multiple environments, from development sandbox to production environment.

Manages relationships between node ids and menu items.

The Menu Node API project fills in one of the "missing tables" in Drupal 6. This module does nothing on its own. Instead, it creates and maintains a {menu_node} table. This table maps the relationship between a node and its menu item (if any).

The module requires the optional core Menu module to be enabled. It also requires Drupal 6.10 or higher. (See this issue for why).