api-graveyard
Official Python collector for API Graveyard — automatically tracks your outgoing HTTP dependencies, detects risk events, and surfaces zombie APIs before they take down your product.
Install
pip install api-graveyard
Quick start
Add one call to the top of your app entry point:
import api_graveyard
api_graveyard.init(
api_key="agk_your_key_here",
project_id="your-project-id",
)
# ... rest of your app
That's it. Every outgoing HTTP/HTTPS request your app makes is now automatically captured, batched, and sent to API Graveyard in the background.
Works with
requestshttpx(sync mode)urllib3directly- Any library that uses
urllib3under the hood
Options
| Option | Type | Default | Description |
|---|---|---|---|
api_key |
str |
required | Your agk_... API key from the dashboard |
project_id |
str |
required | Your project ID from the dashboard |
base_url |
str |
https://api-graveyard.com |
Override for self-hosted |
service_name |
str |
None |
Tag events with a service name |
environment |
str |
"production" |
Tag events with an environment |
flush_interval_s |
float |
10.0 |
How often to flush the event buffer (seconds) |
max_batch_size |
int |
100 |
Max events per batch before forcing a flush |
debug |
bool |
False |
Log flush activity |
Django / Flask example
# manage.py or wsgi.py / app factory
import api_graveyard
api_graveyard.init(
api_key=os.environ["API_GRAVEYARD_KEY"],
project_id=os.environ["API_GRAVEYARD_PROJECT_ID"],
service_name="django-backend",
environment=os.environ.get("DJANGO_ENV", "production"),
)
Graceful shutdown
The collector automatically flushes on process exit. For manual control:
import api_graveyard
api_graveyard.shutdown()
What gets captured
- Method, URL, HTTP status code, response time
- Timestamp of each request
- Service name and environment (if configured)
Requests to api-graveyard.com itself are never captured to avoid infinite loops.
Localhost and 127.0.0.1 requests are ignored by default.
Get your API key
- Sign up at api-graveyard.com
- Create a project
- Go to Settings → Integrations and create an API key
License
MIT
Release files for api-graveyard 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| api_graveyard-0.1.2.tar.gz | 6.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| api_graveyard-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / api_graveyard-0.1.2.tar.gz
| Download URL | api_graveyard-0.1.2.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f89f4928f276312bf3212d7f22e0e5604b5083d68fa72350e45c4f5996c721d
|
|
BLAKE2b-256 checksum How to use checksums |
d73dfdbb0a853c5ac02aa3342b124bbf05f4d793c5b64225abe05b69ef90461e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / api_graveyard-0.1.2-py3-none-any.whl
| Download URL | api_graveyard-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f93052c7bdf701427e877271da385d109055d5a887799c0cb1fe820f87178071
|
|
BLAKE2b-256 checksum How to use checksums |
f60a0053d2e1e93202192e9d8a8791a17920f6c6459eb023874ab107b361c4e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|