GitHub vs Notion API Comparison

This project examined how two very different APIs represent data, relationships, content and user-defined structures.

I compared GitHub's resource-oriented approach with Notion's more flexible, schema-driven model, using real API responses and documentation examples to investigate:

• JSON objects, arrays and nested data

• Resource relationships and URL-based navigation

• Pagination and query parameters

• Authentication and object identifiers

• GitHub REST and GraphQL approaches

• Notion blocks, database properties and schemas

• How API design choices affect developer experience

A central finding was that the two APIs reflect the systems they represent:

GitHub is closer to a map of connected resources. Notion is closer to a set of configurable building blocks.

The project moves from technical observation to practical comparison, using API evidence to explain not only what the data looks like, but why the structures differ and how those differences affect developers working with each API.

What this project demonstrates: technical research, API analysis, information structuring, clear explanation of complex concepts, and the ability to turn detailed technical evidence into accessible documentation.