Artifact Ingestion
This guide covers strategies for uploading artifacts to the lake.Basic Upload
Single Artifact Upload
Response Fields
| Field | Description |
|---|---|
id | Unique artifact identifier |
status | Current status (uploaded, active, revoked) |
created_at | Timestamp of upload |
Content Formats
Base64 Encoded
Send file as base64 string:Multipart Form Data
For large files, use multipart upload:Batch Upload
For bulk uploads, use batch endpoint:Check Batch Status
Override Weights
By default, weights come from the template. Override per artifact:Lock Value Validation
Values are validated against template rules:Deduplication
Prevent duplicate uploads with idempotency keys:Nightly Batch Upload Strategy
For insurance carriers with nightly batches:1. Prepare Manifest
2. Upload with Hash Validation
3. Verify Upload Results
Check which artifacts were created vs. skipped:Managing Artifacts
List Artifacts
Get Artifact Details
Revoke Artifact
Remove access to a specific artifact:Rate Limits
| Upload Type | Limit |
|---|---|
| Single upload | 100/minute |
| Batch upload | 10 batches/minute |
| Max batch size | 100 artifacts |
Best Practices
1. Use Batch Uploads for Large Volumes
Instead of 100 single uploads, use one batch.2. Implement Retry Logic
3. Use Idempotency Keys
Prevent duplicate uploads in case of retries.4. Validate Before Upload
Validate lock values client-side before uploading:Next Steps
- Creating Artifact Types - Design templates
- First Ramp Setup - Configure your ramp
- API Reference - Full artifact API