mirror of
https://github.com/twirl/The-API-Book.git
synced 2025-05-31 22:09:37 +02:00
naming consistency
This commit is contained in:
parent
bd61d04bd7
commit
17d987d615
@ -1,4 +1,4 @@
|
||||
### API Business Models
|
||||
### The API Business Models
|
||||
|
||||
Before we proceed to the API product management principles description, let us draw your attention to the issue of profits that companies providing APIs might extract from it. As we will demonstrate in the next chapters, this issue directly affects making product decisions and setting KPIs for the API team. [In brackets, we will provide examples of such models applicable to our coffee-machine API study.]
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
### API Services Range
|
||||
### The API Services Range
|
||||
|
||||
The important rule of API product management that any major API provider will soon learn formulates like that: there is no sense to ship one specific API; there is always a room for a range of products, and this range is two-dimensional.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
### API Key Performance Indicators
|
||||
### The API Key Performance Indicators
|
||||
|
||||
As we described in the previous chapters, there are many API monetization models, both direct and indirect. Importantly, most of them are fully or conditionally free for partners, and the direct to indirect benefits ratio tends to change during the API lifecycle. That naturally leads us to the question of how exactly shall we measure the API success and what goals are to be set for the product team.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
### Technical Means of Preventing ToS Violations
|
||||
### The Technical Means of Preventing ToS Violations
|
||||
|
||||
Implementing the paradigm of a centralized system of preventing partner endpoints-bound fraud, which we described in the previous chapter, in practice faces non-trivial difficulties.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user