Endpoint principal: GET /api/v1/activations/{id}

Paso a paso

  1. 1
    Use idempotencyGenerate one stable Idempotency-Key for each intended purchase and reuse it only for retries of that purchase.
  2. 2
    Respect rate limitsBack off after errors and avoid high-frequency status polling.
  3. 3
    Persist activation IDsStore the returned ID before updating your own workflow.
  4. 4
    Handle terminal statesTreat finished, cancelled and refunded activations as closed and stop polling them.
  5. 5
    Reconcile the balanceCheck balance and activation history when recovering from an uncertain network response.

Usa números virtuales solo donde lo permitan la ley y los términos del servicio de destino. See the API documentation for the complete parameters and error responses.