# Revoked recurring token

Webhooks notify about a revoked recurring token for alternative payment methods.
Duplicate webhook events can occur. Implement idempotency on your end to avoid processing the same event twice.

Endpoint: POST APMRevokedRecurringToken
Version: 1.0.0
Security: merchant, signature

## Security:

  - `merchant` (unknown)
    apiKey in header merchant

  - `signature` (unknown)
    apiKey in header signature

## Header parameters:

  - `merchant` (string, required)

  - `signature` (string, required)

  - `solidgate-event-id` (string, required)
    Unique event identifier.

  - `solidgate-event-created-at` (string, required)
    Event creation time in UTC as ISO 8601 with milliseconds.

  - `solidgate-event-type` (string, required)
    Event type, indicating the specific event that occurred.

## Request fields (application/json):

  - `token` (string, required)
    Recurring token.
    Example: 923bb4e6-4a5f-41ec-81fb-28eb8a152e55

  - `initial_order_id` (string, required)
    Initial order identifier.
    Example: 22738n

  - `cancelled_at` (string, required)
    Datetime when the token was cancelled.
    Example: 2024-12-21 11:21:30

## Request examples:

  - `Revoked recurring token` (unknown)

## Response 2XX:

  - `2XX` (unknown)
    Return any 2XX status to confirm successful data receipt