Manual Event Submission
Overview
Pay-i provides two Ingest API methods for manually submitting event data to track usage that occurs outside the standard instrumentation flow. Both methods accomplish the same goal but are designed for different environments and programming languages.
Manual event submission is particularly valuable for these key use cases:
- Tracking Custom Resources - Submit usage data for custom resources not directly supported by Pay-i
- Submitting Historical Data - Record individual past events for complete usage visibility
- External System Integration - Align Pay-i data with other tracking systems
Choose Your Method
Pay-i offers two approaches for manual event submission:
For Python applications:
- Use the Python SDK Ingest API for the most convenient integration
- Provides type safety, simplified parameter handling, and native Python objects
For all other languages:
- Use the REST Ingest API
- Language-agnostic approach with standard HTTP requests
Both methods provide identical functionality and access to the same Pay-i features.
Common Limitations
Both methods support the same features as standard Pay-i Instrumentation, except for Block
limits. This is because Pay-i cannot block requests it doesn't directly proxy. Pay-i will still calculate costs based on reported units and associate data with any provided tags, use cases, and Allow
limits for tracking and analysis.
Related Resources
- Historical Data Backfill - Strategies for importing historical usage data
- Custom Categories and Resources - Setting up tracking for custom models
- Bulk Ingest API Documentation - API reference for submitting multiple events
Updated 2 days ago