Query station operators
Charge stations are often exploited by various operators. To get an overview of the operators in your station database you can use the
operatorList query. All operator details are available for you to query. Keeping the number of attributes as low as possible will improve performance.
The entire list of operators can be accessed using the
operatorList query, along with the attributes you would like to receive. Optionally you can use pagination and filters to improve your results.
To filter your operator list you can use the
filter argument. You can then use
excluded to specify how you want to filter the list.
To search for an operator you can use the
Deprecated: Replaced by filter & search params
Search operator by name
Filter operators by parameters
Number of elements (count) to return, default: 10
Page number to return, default: 0
Frequently used fields
Unique operator ID
Name of an operator
Link to an operator’s website
Image link to an operator’s logo
External ID of an operator provided by the operator data source
Deprecated: Not used anymore, please use countries property instead
ISO-3166 alpha-2 country codes an operator is active in.
Show CountryCodeAlpha2 enum values
Ranking level on which the operator is placed or null in case the operator is not on any ranking level
Flag which indicates if the operator is in the excluded list
A response can either contain a
data or an
errors object. The response header will always return
200 as a status code.
When successful, a
data object will be returned with the
requested fields. If there are no fields present the
data object will return the operation name with the
appropriate return type. If the operation was a query, this output
will be an object of the schema’s query root type; if the operation
was a mutation, this output will be an object of the schema’s mutation
If unsuccessful, an
errors object will be returned with
more details in the
extensions object. The error object
can contain any of the following objects.