This API provides functionality for charge providers to send charge activity. You must have \"Client Credentials\" issued to you to be able to start using this API. Please get in touch if you do not have this information. You can send charges in two ways:
\n/dataProvider.charges.addWithIntervals/dataProvider.charges.addOAuth 2.0 authentication with the client_credentials grant type is used to authenticate with the API.
An example request can be seen below
\nPOST https://login.chargepass.co.uk/ausa4dehw4Wb8CLSd417/v1/token
grant_type: \"client_credentials\"\nscope: \"chargepass.homecharge.charge.write\"\nclient_id: \"CLIENT_ID\"\nclient_secret: \"CLIENT_SECRET\"\n\nhttps://login.chargepass.co.uk/oauth2/ausa4dehw4Wb8CLSd417/v1/tokenchargepass.homecharge.charge.writeWhen sending us charges, you can use the status value for each charge on the response to understand whether the charge has been successfully received.
The possible status values are:
\nSuccess - You can be assured that we've received and stored the chargeDuplicate - We recognise the charge as one you have sent previously (based on the chargeExternalId and chargePointExternalId values). The charge will be ignored and will not be persistedIf a 400 Bad Request is returned, the whole request will be rejected by our validation rules. In this case, none of the charges on the request will be ingested in our system.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"27848775","collectionId":"f3987b4f-2d97-479e-ade1-3a3f8db16d0b","publishedId":"2sA3rwLDeo","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"f76f77"},"publishDate":"2024-08-02T10:06:12.000Z"},"item":[{"name":"dataProvider.charges.addWithIntervals","id":"e0ca2a79-032f-477a-b19d-18a4c850db88","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"charges\": [\r\n {\r\n // The unique ID for the charge.\r\n \"chargeExternalId\": \"{{chargeExternalId}}\", \r\n\r\n // The unique ID for the charge point.\r\n \"chargePointExternalId\": \"{{chargePointExternalId}}\", \r\n\r\n // One or more charge intervals - each has a maximum duration of 30 minutes and a minimum duration of 1 minute.\r\n \"intervals\": [ \r\n {\r\n // ISO 8601 date/time when the charge interval started.\r\n \"from\": \"{{from}}\",\r\n\r\n // ISO 8601 date/time when the charge interval finished.\r\n \"to\": \"{{to}}\",\r\n\r\n // Energy consumption for the charge interval in kWh.\r\n \"consumption\": {{consumption}}\r\n }\r\n ]\r\n }\r\n ]\r\n}","options":{"raw":{"language":"json"}}},"url":"https://api.mina.co.uk/dataProvider.charges.addWithIntervals","description":"Ingest one or more charges as a collection of 30 minute intervals. We'll determine when each charge started/finished based on the first/last interval respectively. Charge consumption will be calculated by summing the consumption values for all intervals.
\nThis is the preferred method of ingesting charges because it produces the highest quality of data. We can then calculate 100% accurate reimbursement amounts for drivers, especially for those on variable tariffs.
\n","auth":{"type":"oauth2","oauth2":{"basicConfig":[],"advancedConfig":[{"key":"clientSecret","value":"Ingest one or more charges based on when they started/finished.
\nThis is the most basic method of ingesting charges. Consumption will be evenly distributed across the duration of the charge in 30-minute intervals. As a result, drivers on variable tariff won't receive 100% accurate reimbursement amounts.
\n","auth":{"type":"oauth2","oauth2":{"basicConfig":[],"advancedConfig":[{"key":"clientSecret","value":"Retrieve a list of chargers registered in our system.
\n","auth":{"type":"oauth2","oauth2":{"basicConfig":[],"advancedConfig":[{"key":"clientSecret","value":"The datetime (ISO 8601) when to find chargers from.
\n","type":"text/plain"},"key":"since","value":"2024-01-01T00:00:00.000Z"}],"variable":[]}},"response":[{"id":"a9617cf6-dffb-451a-ab5e-4d31bc8546b2","name":"Success (200 OK)","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://api.mina.co.uk/dataProvider.chargePoint.findMany?since=2021-01-01T06:34:56.000000Z","host":["https://api.mina.co.uk"],"path":["dataProvider.chargePoint.findMany"],"query":[{"key":"since","value":"2021-01-01T06:34:56.000000Z","description":"The date/time (ISO 8601) when to find chargers from"}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json","name":"Content-Type","description":"","type":"text"}],"cookie":[],"responseTime":null,"body":"{\n \"data\": [\n {\n \"externalId\": \"chargePoint-1\",\n \"creationTimestamp\": \"2021-03-04T12:17:30.000000Z\"\n },\n {\n \"externalId\": \"chargePoint-2\",\n \"creationTimestamp\": \"2021-09-21T15:06:16.000000Z\"\n }\n ]\n}"}],"_postman_id":"499fcd5c-e043-4c0d-80c7-6a3ab42ccd76"},{"name":"dataProvider.charges.findMany","id":"41bda860-6181-4d25-ad92-489e4888b714","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n\t// The unique ID's for the charge points.\n\t\"chargePointExternalIds\": [\n \"{{chargePointExternalId}}\"\n ],\n\n\t// ISO 8601 date/time when the charge period started.\n\t\"chargesReceivedFrom\": \"{{chargesReceivedFrom}}\",\n\n // ISO 8601 date/time when the charge period ended.\n\t\"chargesReceivedTo\": \"{{ChargesReceivedTo}}\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.mina.co.uk/dataProvider.charges.findMany","description":"Retrieve a list of charges registered in our system.
\n","auth":{"type":"oauth2","oauth2":{"basicConfig":[],"advancedConfig":[{"key":"clientSecret","value":"