Apollo配置中心OpenAPI接口文档 ## 认证方式 所有API接口都需要通过Authorization header进行身份验证。 ### 获取Token的方式: 1. **Portal管理界面获取**: - 登录Apollo Portal管理界面 - 进入\"管理员工具\" -> \"开放平台授权管理\" - 创建第三方应用,获取Token 2. **Token格式**: ``` Authorization: token_value ``` 3. **Token权限**: - Token具有对应应用的读写权限 - 不同Token可能有不同的环境和命名空间权限 - 建议为不同用途创建不同的Token ### 使用示例: ```bash curl -X GET \"http://localhost:8070/openapi/v1/apps\" \ -H \"Authorization: your_token_here\" ```
Metadata
Release files for apollo-openapi 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| apollo_openapi-0.0.1.tar.gz | 66.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apollo_openapi-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.6 kB
Release files / apollo_openapi-0.0.1.tar.gz
| Download URL | apollo_openapi-0.0.1.tar.gz |
|---|---|
| Size | 66.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4d0752850b98ab23d056af0ad0af2fc72b113def64eb1619da2adbacdc47f3b
|
|
BLAKE2b-256 checksum How to use checksums |
77ceb204e5983933d9dab443e6b44d728746dd2da53b6a2d48777eeac6d54b40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.4
|
Release files / apollo_openapi-0.0.1-py3-none-any.whl
| Download URL | apollo_openapi-0.0.1-py3-none-any.whl |
|---|---|
| Size | 134.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
148f28edeece393a0862bc28e3e035be7a04a78672a63496402fa29575e38eaa
|
|
BLAKE2b-256 checksum How to use checksums |
fb1b9c9b7e9579940958fc532efadce8c3115612d323a5d73343a8a6c8b49628
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.4
|
Security for apollo-openapi 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.