Abstract: Application programming interfaces (APIs) may have different API schemas that may have different organizations of schema properties and entities or use different names for schema properties and entities. Where two or more APIs with different schemas are being used, it may be desired to map schema properties and/or entities between them. Semantic representations of API schema properties and entities may be used to assist with the mapping of schema properties and entities. The semantic representations may be used to suggest possible mappings to a user or to automatically determine a mapping without the involvement of a user.

Abstract: A first application programming interface (API) with a first schema may be adapted to work with a second API with a second schema using mappings of schema properties and a directed graph. An API call specification of the first API may receive first API schema properties as input and provide first API schema properties as outputs. The first API schema properties may be mapped to corresponding second API schema properties, such as using semantic representations of the schema properties. An implementation of an API call for the first API may be created by using the schema mappings and selecting a path from a directed graph corresponding to the second API, where the path includes a node corresponding to an API call of the second API. Computer code may be generated using nodes of the path, and the computer code may be stored for later use.