> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vultlocal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Unblock Subscriber

> Restore access to a blocked subscriber account

<Info>
  Unblocking restores full access to the subscriber's account and all linked cards.
</Info>

## Request

<ParamField header="Authorization" type="string" required>
  `Bearer olive_live_xxx` or `Bearer eyJ...` (JWT)
</ParamField>

### Path Parameters

<ParamField path="id" type="string" required>
  Subscriber UUID (e.g., `sub_abc123`)
</ParamField>

***

## Response

<ResponseField name="success" type="boolean">
  Whether unblock succeeded
</ResponseField>

<ResponseField name="message" type="string">
  Result message
</ResponseField>

***

## Examples

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://demo.api.vultlocal.com/api/v1/subscribers/sub_abc123/unblock" \
    -H "Authorization: Bearer olive_live_xxx"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  {
    "success": true,
    "message": "Subscriber unblocked successfully",
    "unblocked_at": "2025-01-20T15:30:00Z",
    "unblocked_by": "admin@olive.sl"
  }
  ```

  ```json 404 Not Found theme={null}
  {
    "error": "Subscriber not found",
    "code": "NOT_FOUND"
  }
  ```

  ```json 409 Conflict theme={null}
  {
    "error": "Subscriber is not blocked",
    "code": "NOT_BLOCKED"
  }
  ```
</ResponseExample>

***

## What Gets Restored

<Steps>
  <Step title="Account Activated">
    Subscriber status changes to `ACTIVE`
  </Step>

  <Step title="Cards Unblocked">
    All linked cards become active again
  </Step>

  <Step title="Transactions Enabled">
    All transaction types are enabled
  </Step>

  <Step title="PIN Attempts Reset">
    Failed PIN attempt counter is reset to 0
  </Step>
</Steps>

***

## Permissions

<Warning>
  Only users with `system_admin` or `compliance_user` roles can unblock subscribers.
</Warning>

***

## Errors

| Status | Code             | Description                |
| ------ | ---------------- | -------------------------- |
| 401    | `UNAUTHORIZED`   | Invalid or missing API key |
| 403    | `FORBIDDEN`      | Insufficient permissions   |
| 404    | `NOT_FOUND`      | Subscriber not found       |
| 409    | `NOT_BLOCKED`    | Subscriber is not blocked  |
| 500    | `INTERNAL_ERROR` | Server error               |

***

## Related

<Card title="Block Subscriber" icon="ban" href="/api-reference/subscribers/block">
  Block a subscriber account with a reason
</Card>


## OpenAPI

````yaml olive-openapi.json POST /subscribers/{id}/unblock
openapi: 3.0.0
info:
  description: >-
    API Gateway for OLIVE NFC Card Payment System - Comprehensive payment, card
    management, agent operations, and admin authentication. All /api/v1 routes
    require authentication using either API Key or JWT token.
  title: OLIVE NFC Card Payment API
  termsOfService: http://swagger.io/terms/
  contact:
    name: API Support
    email: support@olive.sl
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.0.0
servers:
  - url: https://olive-gateway-a6ba.onrender.com/api/v1
security: []
paths:
  /subscribers/{id}/unblock:
    post:
      tags:
        - Subscribers
      summary: Unblock a subscriber
      description: Unblock a previously blocked subscriber account
      parameters:
        - description: Subscriber ID
          name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Unblock successful
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
      security:
        - ApiKeyAuth: []
        - BearerAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      description: >-
        API Key for third-party integrations (WhatsApp, Smart PAY, VULT).
        Format: 'Bearer olive_live_xxxxxxxxxxxxx'
      type: apiKey
      name: Authorization
      in: header
    BearerAuth:
      description: >-
        JWT token from admin login for administrative operations. Format:
        'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...'
      type: apiKey
      name: Authorization
      in: header

````