Connectors
==========
A connector is a part of a charging station, where one charging stations
can have one to many connectors. A connector is often used to identify certain
actions on remote calls or necessary for other entities
(e.g. maintenance windows).

Reading
-------
Connectors can be accessed via the `connectors` `GET` endpoint.
This endpoint will return a list of all visible stations in be.ENERGISED.

The list endpoint is using
`offset pagination <pagination.html#offset-based-pagination>`__.

.. code-block:: bash

    curl --location --request GET 'https://<slug>.beenergised.cloud/api/cpoapi/v1/connectors/' \
    --header 'Authorization: <access_token>' \
    --header 'Content-Type: application/json'

Connectors might also be accessed in the context of a charging station.

The list endpoint is using
`offset pagination <pagination.html#offset-based-pagination>`__.

.. code-block:: bash

    curl --location --request GET 'https://<slug>.beenergised.cloud/api/cpoapi/v1/cp/:cpuuid/connectors/' \
    --header 'Authorization: <access_token>' \
    --header 'Content-Type: application/json'

A single connector can be either fetched directly with a
uuid or it can be loaded in the context of a station.

Together with the cp uuid.

.. code-block:: bash

    curl --location --request GET 'https://<slug>.beenergised.cloud/api/cpoapi/v1/cp/:cpuuid/connectors/:connectoruuid' \
    --header 'Authorization: <access_token>' \
    --header 'Content-Type: application/json'

Directly with the uuid:

.. code-block:: bash

    curl --location --request GET 'https://<slug>.beenergised.cloud/api/cpoapi/v1/connectors/:connectoruuid' \
    --header 'Authorization: <access_token>' \
    --header 'Content-Type: application/json'