| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [View Raw Code] [Original HTTPS Page] |
These notes summarize basic concepts used in many Python Data/BI workflows.
An API allows software systems to exchange data through defined endpoints.
A typical API workflow is:
Many APIs return JSON.
JSON stands for JavaScript Object Notation.
In Python, JSON data usually becomes:
| JSON concept | Python equivalent |
|---|---|
| object | dictionary |
| array | list |
| string | string |
| number | int or float |
| true / false | True / False |
| null | None |
Nested JSON responses are common in API work. For Data/BI workflows, selected nested values often need to be transformed into a flat table.
OAuth2 is an authorization framework.
It is often used when an application needs controlled access to a service on behalf of a user or system.
Important terms:
| Term | Meaning |
|---|---|
| Client ID | Public identifier for an application |
| Client Secret | Private secret for an application |
| Access Token | Short-lived token used to call protected APIs |
| Refresh Token | Token used to request a new access token |
| Scope | Permission level requested by the application |
| Redirect URI | URL where the authorization server sends the result |
| Authorization Server | System that issues tokens |
| Resource Server | API that accepts valid access tokens |
Never commit real secrets to Git.
Do not commit:
Use .env.example files or placeholders instead.
API and OAuth2 basics matter because many real Data/BI systems need to connect to external platforms, internal tools or cloud services.
A safe workflow must separate:
This repository keeps OAuth2 as concept notes for now. That is intentional.
| Back | FazBrowse Home | New Git URL |