iRemotech Device API — announced changes

Changes to the /v1 API that have been announced but are not yet in effect. Each entry says what changes, when it applies, and what to do to be ready. Once a change is live it moves to the changelog.

If the API is integrated into an automated workflow — a script, a service, a scheduled job, anything that calls the API without a person watching — check this page at least once a week. Behaviour changes are published here first, before they take effect.

Upload tickets become single-use

• Announced: 2026-09-16
• Effective: with the launch of usage-based billing
• Affects: POST /v1/devices/{id}/media/ticket and the upload endpoint it returns. Dashboard (browser) uploads are not affected.

What changes

• A ticket authorises one upload. Mint one ticket per file.
• A second upload with the same ticket is rejected by the upload endpoint with 409 ticket_already_used.
• max_bytes is set per ticket and may be lower than the 300 MB platform ceiling. Always read it from the ticket response.

What to do now

• Request a ticket immediately before each upload. That pattern works today and after the change, so an integration updated now needs no second change.
• If your integration currently mints one ticket per batch, change it to one per file.