Introduction to PulsePI
PulsePI introduces a Logic-first API design. Unlike conventional REST APIs that rely on multiple endpoints and HTTP methods tied to specific resources, PulsePI utilizes a single POST endpoint to handle all functionalities.
Key Features
- Single POST Endpoint: Acts as a central hub, processing requests based on the specified module, action, and parameters within the request body.
- Simplified Data Retrieval: Instead of requiring developers to write complex database queries, PulsePI provides intuitive mechanisms for data manipulation through projections (_fields) and filtering (filters).
- REST-like Development, GraphQL-like Data: Define actions in a manner reminiscent of REST but retrieve data with the precision and efficiency of GraphQL-like queries.
- Batch Requests: Call multiple modules and actions in a single request for efficient data fetching.
Available Modules & Actions
| Module | Actions |
|---|---|
| blog | getTrendingPosts |
| posts | getPosts, getUsers |
| user | list, getByEmail, create, deleteByEmail |
📦 Models Registered:
Posts, User
Basic Request Structure
json
{
"module": "posts",
"action": "getPosts",
"params": {}
}While still under development, PulsePI aims to abstract away much of the underlying complexity, enabling developers to concentrate on implementing core application logic.