Data services
Manage APIs and calling applications. Developers create, test, and publish APIs; consumers discover/request them; administrators review requests and monitor calls. This differs from marketplace product requests and offline delivery.
Choose a task
| Task | Guide | Verify |
|---|---|---|
| Discover services | API marketplace | Endpoint, parameters, response |
| Develop/publish | API development | Tested and discoverable |
| Create/request an application | Applications | State, credentials, grants |
| Review/monitor | Approvals | Traceable decisions and calls |
Start with Quick start.
Understand objects
| Object | Meaning | Relationship |
|---|---|---|
| API | Data access interface definition | Market entry after testing/publication |
| Application | Calling identity | Requests APIs and can be shared by approval |
| API request | Application's right to an API | Verify grant/validity after review |
| Application request | Use another owner's application | Separate approval |
| Call record | API/application monitoring | Not data delivery evidence |
Before you begin
Administrators assign feature rights and development, application, request, and review responsibilities. Engineers prepare definitions, test sources, applications, and purposes. Visibility is not invocation authorization. Role names in source material describe responsibilities and can be customized.
Distinguish the marketplace
Data Marketplace discovers business assets/products and records requests with offline fulfillment. Data Services develops, publishes, authorizes, and invokes APIs. Their request objects and results differ.