API
Limits
- Your plan’s caps apply exactly as they do in the app: file size, bytes per month, minutes, and whether the sport pipeline is available at all. A refusal names the reason code, and the codes are in the tables on The endpoints.
domaincannot be changed after the analysis starts. It selects the pipeline, and the run is paid for either way.- One analysis per uploaded object. Naming the same path twice answers
409rather than analysing it again — upload the file again if you genuinely want a second run. - Deleting a broadcast does not give its minutes back. Uploading, analysing and deleting in a loop is not a way around an allowance.
- An object you upload and never analyse stays in the bucket, and counts toward your bytes for the month until you analyse it or it is removed. Nothing removes it for you, so a script that uploads more than it analyses is eventually refused.
- A callback whose address stops resolving publicly is refused at delivery time rather than silently dropped, and the attempt is recorded either way. Repointing the hostname at an internal address after registering it does not work.
Something here wrong or missing? Tell us — it is the kind of bug nobody reports.Back to KAIROS