# API-Verified Quest (RESTFUL)
## Introduction
CARV allows the use of OpenAPI to verify whether a user has completed a quest.
## Sequence Digram
## Specifications
**Request**
The API used for verification must be an open API. \
You can choose to use either **email** or **wallet address** or **user ID of third-party platforms** as the identifier to verify a user. \
You can choose *optionally* to add custom headers to the request, such as an API key.\
We will also include **begin time** and **end time** (timestamp in milliseconds) for a quest in case this information is required for verification.
So a GET Request will look like the followings:
{% code overflow="wrap" %}
```sh
# wallet address
curl https:///?address=&begin_time=&end_time=
```
{% endcode %}
OR
{% code overflow="wrap" %}
```sh
# email
curl https:///?email=&begin_time=&end_time=
```
{% endcode %}
OR
{% code overflow="wrap" %}
```sh
# Telegram id
curl https:///?telegram_id=&begin_time=&end_time=
```
{% endcode %}
OR
{% code overflow="wrap" %}
```sh
# Line id
curl https:///?line_id=&begin_time=&end_time=
```
{% endcode %}
#### Response Format
{% code overflow="wrap" %}
```json
{
"result":{ //required on success
"isValid": //boolean: whether the user completed the quest.
},
"error":{ //required on error, this field MUST NOT exist if there was no error triggered during invocation.
"code":, //number
"message":""
}
}
```
{% endcode %}
