The ProgrammableWeb directories are about cataloging APIs, SDKs, libraries, frameworks, Web apps and applications that consume APIs (primarily mashups and mobile apps), and pointers to sample source code found elsewhere on the Web. The purpose of this form is to make a record of libraries that play a role in the API ecosystem. While we know that not everyone shares this view, ProgrammableWeb reserves the word “library” for bits of software that result in the provisioning (aka “standing-up”) of an API (if the bit of software you have is for consuming APIs, we reserve those for our SDK directory). For example, we’ve observed a lot of locally installable server applications that come with no APIs and for many of those server apps, third party developers will often build libraries that, once installed, result in the addition of RESTful APIs to those server apps.
Before submitting a library to our directory, please be sure first add the frameworks it depends on to the framework directory and any APIs that it may provision to our API directory. The reason for this is that the form below asks you to pick any related frameworks and APIs. So, any related assets need to pre-exist in our directories in order for you to select them.
After adding a library to ProgrammableWeb’s directory, be sure to use our forms to add any related APIs, frameworks, SDKs, pointers to sample source code, and examples of applications that are some how involved with the library or whatever depends on it. If you have any questions about our forms, their fields, and the data model behind our directories, we recommend that you read ProgrammableWeb's New API Directory Data Model Explained. If you still have questions, feel free to email us at firstname.lastname@example.org.