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

# Get Support Snapshot

Returns what support needs to know about a charger and its location at one moment: what the charger is, whether it was online, its connectors and faults, the events and OCPP calls before the moment, the transaction, the meter values around it, the location's settings and power management, its operators and open alerts. `text` holds the snapshot as plain English text, ready to paste into a support conversation.

The snapshot only reads what is already stored or held live. It never sends the charger a command.

Each section is cut to your access level. `meta.missing` lists what is not in the snapshot and why.

<ParamField path="charger" type="string" required>
  The UUID of the charger.
</ParamField>

<ParamField query="at" type="string">
  The moment, as an ISO 8601 timestamp, not in the future. Defaults to now. Live state (the proxy view, reconnects, whether power management runs and why it holds back, the operators' connection state) is only known when the moment is within two minutes of now.
</ParamField>

<ParamField query="transaction" type="integer">
  The ID of the transaction the question is about. Without it, the transaction running at the moment, else the last one before it.
</ParamField>

<ParamField query="connector" type="integer">
  Limit the connectors and meter values to one connector.
</ParamField>

<ParamField query="events" type="integer" default="25">
  How many logbook events to include, from 1 to 100.
</ParamField>

## Access levels

| Level | Who | Gets |
| - | - | - |
| `full` | The team that owns the location | Every section, with the SIM's ICCID and IMSI. Never an IP address. |
| `sensitive` | A team on the location with data access | As `full`, without the ICCID and IMSI. |
| `basic` | A team on the location without data access | The charger, connection, connectors, fault history, transaction, location, power management settings, operators and alerts. No events, OCPP calls, proxy view, card, meter serial number, meter values, allocations or operator connection state. |
| `third_party` | Anyone else who can see the charger, such as a charger brand | As `basic`, without the charger name, the location's name, address and other chargers, the meter code and the operators. |

## Response

<ResponseField name="data" type="object">
  <Expandable title="snapshot">
    <ResponseField name="meta" type="object">
      `generated_at`, `at`, `live` (whether the moment is now), `level`, `timezone` of the location, and `missing`: a list of `{field, reason}` with reason `not_allowed`, `no_data`, `not_kept` or `only_live`.
    </ResponseField>

    <ResponseField name="charger" type="object">
      `identity`, `reference`, `serial_number`, `brand`, `model`, `firmware_version`, `is_mid`, `licenses`, `setup_completed`, `created_at`.
    </ResponseField>

    <ResponseField name="connection" type="object">
      `status`, the last connection, disconnection and heartbeat, the heartbeats just before and after the moment, `reconnects_last_hour`, and `proxy`: the proxy's live view of the charger socket.
    </ResponseField>

    <ResponseField name="connectivity" type="object">
      The last boot, the meter in the charger, whether it has a Volt Time SIM, and for the owner the ICCID and IMSI.
    </ResponseField>

    <ResponseField name="connectors" type="object[]">
      Per connector: `status`, `error` (never `NoError`), `error_info`, `vendor_error_code`, `max_amperage`, `min_current`, `current_limit`.
    </ResponseField>

    <ResponseField name="fault_history" type="object">
      How often the charger reported Faulted in the 30 days up to the moment, the first and the last time, and the last code.
    </ResponseField>

    <ResponseField name="events" type="object">
      The charger's logbook up to the moment, in the shape of `GET /v3/chargers/{charger}/events`: `data`, `operators`, `cards`.
    </ResponseField>

    <ResponseField name="ocpp_tail" type="object[]">
      The last 15 OCPP calls up to the moment, without heartbeats, meter values, charging profiles, security events and configuration calls.
    </ResponseField>

    <ResponseField name="transaction" type="object">
      The transaction: `id`, `running_at` (whether it ran at the moment), start, stop, energy, stop reason, the card UID and its name on the location, and which backend authorized it.
    </ResponseField>

    <ResponseField name="meter_values" type="object[]">
      Per measurand, phase and location: `min`, `max`, `avg`, `first`, `last` and `count`, from ten minutes before to five minutes after the moment.
    </ResponseField>

    <ResponseField name="location" type="object">
      The name, address, country, timezone, energy price settings (scheduled charging or dynamic price charging) and the other chargers on the location.
    </ResponseField>

    <ResponseField name="power_management" type="object">
      `groups`: the charger's group and every group above it, with limits, method, solar, peak shaving, the meter and its code (for Chargee the V3 code) and, when the moment is now, whether power management runs. `connectors`: what it allocated and requested in the five minutes up to the moment, the last charging profile and its answer, and when the moment is now the live reason.
    </ResponseField>

    <ResponseField name="operators" type="object[]">
      Each operator besides Plugchoice: `name`, `role` (`billing` or `data_and_control`) and, when the moment is now, its connection state.
    </ResponseField>

    <ResponseField name="alerts" type="object[]">
      Up to ten service alerts on the charger or its location that were open at the moment.
    </ResponseField>

    <ResponseField name="text" type="string">
      The snapshot as plain English text: a first line on what it is about, then sections under a heading, with a coloured dot for connection, connector status and faults. It ends with an open question for the customer.
    </ResponseField>
  </Expandable>
</ResponseField>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.