Specific Errors Scenarios

Incorrect time input

Domain Registration Realtime Listing API calls merely show lately registered domains that are created approximately within 48-hour. If you use a time 48 hours later than your current time in requests for this API input (start_date), the following response will be returned as an error.

$ curl --request POST \
     	 --url 'https://api.deepinfo.com/v1/monitoring/real-time/domains?page=1&page_size=100' \
    	 --header 'Accept: application/json' \
    	 --header 'Content-Type: application/json' \
    	 --data '
{
     "strict": false,
     "start_date": "2021-10-20T21:15:00Z"
}
'

HTTP/1.1 400 BAD REQUEST ERROR
...
{
  "code": 10400,
  "reason": "body.start_date The start_date field can't be earlier than 2 days, please update it for 2 days and beyond.."
}

Missing input time format

You should be careful about missing time formats. The API returns the following error if you do not provide valid time values.

$ curl --request POST \
     --url 'https://api.deepinfo.com/v1/monitoring/real-time/domains?page=1&page_size=100' \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --data '
{
     "strict": false,
     "start_date": "2021-10-20"
}

HTTP/1.1 400 BAD REQUEST ERROR
...
{
  "code": 10400,
  "reason": "body.start_date can't compare offset-naive and offset-aware datetimes."
}

Invalid input time format

You should be careful about invalid time formats. The API returns the following error if you do not provide accurate time values.

curl --request POST \
     --url 'https://api.deepinfo.com/v1/monitoring/real-time/domains?page=1&page_size=100' \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --data '
{
     "strict": false,
     "start_date": "2021-25-10T10:15:00Z"
}

HTTP/1.1 400 BAD REQUEST ERROR
...
{
  "code": 10400,
  "reason": "body.start_date invalid datetime format."
}