tencent/apijson

🏆 Real-Time no-code, powerful and secure ORM 🚀 providing APIs and Docs without coding by Backend, and Frontend(Client) can customize response JSONs 🏆 实时...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 3rd, 2026
Created on November 21st, 2016
Open Issues & Pull Requests: 236 (+0)
GitHub issues: Enabled
Number of forks: 2,276
Total Stargazers: 18,408 (+0)
Total Subscribers: 393 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 days
Mean response time: 218.8 days
90th percentile: 784.5 days
Tracked items: 203

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Bug 漏洞" is answered fastest, typically in about 11 hours, while "Job/Interview 工作/面试" waits about 24 months. Only 7% of issues opened in the past year have been closed. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 59
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 791 days
Stale 30+ days: 56
Stale 90+ days: 53

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Popularize 宣传/推广/布道 (82)
  • Question 使用问题 (50)
  • Document 文档 (41)
  • Bug 漏洞 (20)
  • Fortune500 财富500强 (19)
  • Job/Interview 工作/面试 (16)
  • help wanted (13)
  • Ecosystem 周边生态 (12)

Detailed Description

APIJSON is a no-code ORM that enables backend teams to provide APIs and documentation without writing code, while allowing frontend clients to customize the structure and content of JSON responses.

The tool addresses the friction between backend API development and frontend data consumption by eliminating the need for backend developers to write endpoint code. Instead of creating individual endpoints for each data shape, APIJSON lets clients specify their exact data requirements through JSON queries. The backend defines database schemas and access permissions, then the ORM automatically handles query execution, validation, and response generation based on client requests. This shifts control over response structure to the consuming application while maintaining security through permission rules.

Teams should adopt APIJSON when frontend and backend development cycles are misaligned, or when API requirements change frequently based on client needs. It works well for projects with multiple clients consuming the same data in different shapes, reducing the backend workload of creating and maintaining numerous endpoints. The tool supports multiple database backends including PostgreSQL, Oracle, SQL Server, and specialized systems like ClickHouse, Elasticsearch, and Snowflake, making it suitable for organizations with heterogeneous data infrastructure. It is particularly valuable in rapid prototyping, mobile app development, and scenarios where backend teams are resource-constrained.

The project receives issue reports primarily from external users rather than the core team, indicating a meaningful base of production adopters. Response times to issues and pull requests typically span one to two weeks. The issue tracker shows that work concentrates on community engagement and promotion, user support questions, and documentation improvements, suggesting the maintainers prioritize helping adopters succeed with the tool and growing awareness of its capabilities.