Deactivation & charging

You pay for the time a tracking service is confirmed active: from the confirmed activation to the confirmed deactivation, pro rata per second of the calendar month (UK time), at your rate-card price. A parked or offline vehicle is still active and chargeable.

Deactivate

POST /partner-api/v1/services/svc_example_01/deactivations
Idempotency-Key: order-1042-cancel
Content-Type: application/json

{ "effective": "immediate" }

effective is immediate, or scheduled with at (ISO 8601 UTC) for a future stop. The response is 202 with an operation; service.deactivation_completed confirms it and carries effective_at, the moment charging stopped.

The charging boundary

• Charging stops at the confirmed deactivation. Until then the service shows deactivation_pending and stays chargeable.
• If our confirmation takes longer than 240 minutes after your request was accepted, the extra time is credited automatically on your statement.
• A failed deactivation stays visible (service.deactivation_failed, operation failed or requires_attention) and can be requested again.
• Cancelling your own customer's subscription in your billing system does not stop the Fleetalyse service — call this endpoint.
• Deactivating never deletes the device, the fleet or its history.

Reactivate and change plans

• POST /services/{id}/reactivations starts a new charging period for an inactive service (no new access fee).
• POST /services/{id}/plan-changes changes the plan when the service is the only active one in its fleet; otherwise change the fleet's plan.
• Each service allows at most 4 activations or deactivations per day (409 CONFLICT with details.reason = "toggle_limit"), because every toggle day costs a full platform day.

Scheduled stops

A scheduled deactivation can be withdrawn before it runs. A newer request for the same service cancels an older scheduled one explicitly (operation.cancelled); nothing is cancelled silently.