Authentication

Overview

Version 1 of the Mevo API uses basic access authentication.

Read more about basic access authentication here.

Clients consuming the Authorized API Endpoints will require a valid set of credentials. If you’re interested in using the API please email api@mevo.co.nz outlining your desired use case.

Usage

Once you have received your credentials from Mevo, create a base64 encoding of your client ID and secret joined by a colon. You can access protected resources by adding the Authorization header containing your encoded credentials to your request.

Example Request - Nearby Vehicles

curl -H Authorization: Basic <ENCODED_CREDENTIALS> \
     https://api.mevo.co.nz/v1/vehicles/near?latitude=-41.2865&longitude=174.7762

Responses

Status: 200 OK

[
  {
    "id": "3cc60942-63bf-4521-a10c-9350e9ebe292",
    "name": "Volkswagen Polo",
    "latitude": -41.311107,
    "longitude": 174.786007
  },
  {
    "id": "14194604-a082-4762-93a3-bd4c0841a92b",
    "name": "Volkswagen Polo",
    "latitude": -41.299911,
    "longitude": 174.770197
  },
  {
    "id": "e86cb60e-b666-4291-86f9-bde44bd61f74",
    "name": "Audi A3 e-tron",
    "latitude": -41.303143,
    "longitude": 174.779126
  }
]

Status: 401 Unauthorized

Returned if the encoded credentials are incorrect. Ensure that your application client ID and client secret match those provided by Mevo. Check that you have base64 encoded your credentials. You might need to remove newline characters from the encoded string.