The Resource Endpoint

Last updated: March 31, 2020

After your application receives an access token from the token endpoint, it is now time to use that token to retrieve Meveto ID of the associated user, that requested to login to your application. The details of the endpoint for retrieving Meveto ID of a user are described below.

Resource endpoint

Expected payload

The endpoint is expecting a GET HTTP request with the following parameters.


This is the ID of your application issued by Meveto. When you register your app with Meveto, you will get an ID.

Accept header

Set the Accept header on the request to application/json

Authorization header

Set an Authorization header on the request to the value of the word Bearer and a space and then the access token received from the token endpoint.

Authorization header value example

Bearer ejalskdyee84774sllkdhewooslkhss9488ejj6233s7slsd76

Response of the endpoint

The endpoint will return a JSON response with an HTTP status of 200 or 401 or 403. The response body will contain error, error_description and payload. If there is an error with the request, then the error key will indicate the type of the error that has occurred, and error_description will provide a short description of the error. Otherwise, the payload will contain information about the user. At the moment, inside the payload key, there will be a user key that contains Meveto ID of the user. HTTP statuses other than 200 are described below.

HTTP status 401

If the response HTTP status code is 401, then it means that the provided access token is not valid.

HTTP status 403

If the response HTTP status code is 403, then it means that the associated user with the provided access token has declined your application's request to get their Meveto ID.