Discovery Operation Status
GET/discovery/status/
Responses
- 200
- 400
- 401
- 500
- application/json
- Schema
- Example (from schema)
Schema
regular
- Regularscheduled
- Scheduledqueued
- Queuedcanceling
- Cancelingcanceled
- Canceledpending
- Pendingin_progress
- In progresscompleted
- Completedfailed
- Failed-
file
- Verifies the domain against a text file in the root directory of the website. Learn more in this article. -
back_office
- Automatically set if manually verified in the back-office. Read-only. -
existing_domain
- Automatically set if the upper-level domain is verified. For example, "my.example.com" is automatically verified if "example.com" is verified. Read-only. -
dns_txt
- Verifies the domain against a TXT record in the Domain Name System (DNS). Learn more in this article. -
dns
- Same asdns_txt
. -
dns_cname
- Verifies the domain against a CNAME record in the Domain Name System (DNS). Learn more in this article. -
meta_tag
- Verifies the domain against a meta tag in the index page of the website. Learn more in this article. -
whitelist
- Automatically verifies if the domain is in the whitelist -
email
- Automatically verifies a domain if the user's email is in the same domain as the target -
aws_route53
- Automatically verifies a domain if the hostname exists as an AWS Route53 Zone. -
cloudflare
- Automatically verifies a domain if the host name exists and is verified as a CloudflareZone. -
waved
- Automatically verifies a domain if there is a waver agreement.
Number of discovery scans currently running.
last_complete_scan objectrequired
The most recent discovery scan completed.
A unique Base58 value identifying this object.
Possible values: [regular
, scheduled
]
Possible values: [queued
, canceling
, canceled
, pending
, in_progress
, completed
, failed
]
Status of the discovery scan
domain_then objectrequired
Possible values: Value must match regular expression ^(?:(?:0|25[0-5]|2[0-4][0-9]|1[0-9]?[0-9]?|[1-9][0-9]?)(?:\.(?:0|25[0-5]|2[0-4][0-9]|1[0-9]?[0-9]?|[1-9][0-9]?)){3}|\[[0-9a-f:.]+\]|([a-z\u00a1-\uffff0-9](?:[a-z\u00a1-\uffff0-9_-]{0,61}[a-z\u00a1-\uffff0-9])?(?:\.(?!-)[a-z\u00a1-\uffff0-9-]{1,63}(?<!-))*(\.(?!-)(?:[a-z\u00a1-\uffff-]{2,63}|xn--[a-z0-9]{1,59})(?<!-)\.?)?))(?::\d{2,5})?$
Domain name with an associated IP address or an IP address itself.
For example, "my.example.com", "example.com", or "37.139.17.48".
The maximum length is 256 characters.
A unique Base58 value identifying this object.
Token used to verify the domain of the target.
Read-only.
Date and time of the verification of the domain, in ISO 8601 UTC format.
For example, "2023-08-09T13:27:43.8208302"
Possible values: [file
, back_office
, existing_domain
, dns_txt
, dns
, dns_cname
, meta_tag
, whitelist
, email
, aws_route53
, cloudflare
, waved
]
Method used in the domain verification:
Error of the last verification of the domain.
Empty if no error occurred.
If true, the domain is verified.
Read-only.
Username used for basic authentication.
Password used for basic authentication.
Possible values: >= 1
and <= 65535
IP Port to send the requests to.
If not defined, uses the default ports for HTTPS and HTTP (if the verification method requires making HTTP requests).
source objectrequired
Possible values: <= 255 characters
Possible values: <= 256 characters
Date the next discovery scan scheduled to run.
{
"running_scans_count": 0,
"last_complete_scan": {
"id": "string",
"type": "regular",
"created_at": "2024-09-05T10:15:22.832Z",
"started_at": "2024-09-05T10:15:22.832Z",
"completed_at": "2024-09-05T10:15:22.832Z",
"status": "queued",
"domain_then": {
"hostname": "string",
"id": "string",
"verification_token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"verification_date": "2024-09-05T10:15:22.832Z",
"verification_method": "file",
"verification_last_error": "string",
"verified": true,
"basic_auth_username": "string",
"basic_auth_password": "string",
"port": 0,
"discovery_enabled": true,
"source": {
"id": "string",
"name": "string"
}
}
},
"next_scheduled_scan_at": "2024-09-05T10:15:22.832Z"
}
- application/json
- Schema
- Example (from schema)
Schema
{
"<field name>": [
"Errors related to field <field name>."
],
"non_field_errors": [
"Errors not related to any field specific field."
]
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Incorrect authentication credentials."
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Unexpected error while handling your request."
}