- Public API
- Private API
- Partner API
- Composite API
Let's discuss them in detail π§΅ππ»
1οΈβ£ Public API
Public APIs are accessible to all developers with a low or moderate level of authentication and authorization.
For example, the Windows API of Microsoft is a public API.
Stability is an essential factor of any public API. Any changes in the public API, let's say adding a new parameter, might break the applications that depend on that API.
2οΈβ£ Private API
Private APIs, also known as Internal APIs, are only accessible to the developers within the organization or enterprise.
Private APIs serve the various features:
- Cross-department Data Access
- Building An App-Enabled Business
- Enabling Contractors to Build Features
- Manage supply chain efficiently
3οΈβ£ Partner API
Partner APIs are accessible to business partners. They are not available publicly and need specific authentication to access them.
4οΈβ£ Composite API
Composite API is a design approach in which we bundle multiple API requests into a single API call.
We can use the response body of one request as the input for the other request.
All the response bodies and the HTTP statuses are returned in a single response body.
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
A quick introduction to smart contracts and decentralized API ποΈ
π§΅ππ»
Before diving into Decentralized API or dAPI, we need to understand Smart Contracts. ππ»
Consider Smart contracts like typical contracts but they are programmatically generated and completely digital. Smart contracts are stored on a blockchain (a system of recording information in a way that makes it difficult or impossible to change, hack, or cheat the system).
Let's talk about widely used HTTP request methods and how to test them.
In this thread, we will cover:
- GET
- POST
- PUT
- DELETE
π§΅ππ»
π GET
The GET method is the widely used request method. It is used to get the desired resources from the server.
For example, making a request to the /posts endpoint will return all the available posts.
One thing to note here is that we have used plural noun (/posts) for URL naming.
Using plural nouns for naming URLs is the best practice. It simply reduces the confusion about whether there are one or more posts in the resource collection.