Get a brand's domain
const url = 'https://app.nebty.de/core/api/brands/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/domains/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/';const options = {method: 'GET', headers: {Authorization: '<Authorization>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://app.nebty.de/core/api/brands/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/domains/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/ \ --header 'Authorization: <Authorization>'Returns one domain associated with the brand, in the full form with scan history and evidence. It is the same record as a row of the non-compact domain list, with the same brand-specific risk score and verdict. Answers 404 if the id is not a UUID or the domain is not associated with this brand.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”UUID of a domain associated with this brand (as returned in the id field of the brand’s domain list).
UUID of the brand, as returned in the id field of the brand list.
Responses
Section titled “Responses”Serializer for Domain model.
object
How this domain was discovered/added to the system
VARIATION- Generated from VariationCERTSTREAM- CertStream APISUBDOMAIN_SCAN- Subdomain ScanMANUAL- Manual EntryAD_LIBRARY- Meta Ad Library
object
The single customer-facing verdict, resolved for the requesting brand.
Unlike risk_score/visual_match there is no shared DomainScan
column to fall back to: the merged verdict has only ever lived on the
pair (BrandDomainAssociation.refresh_merged_verdict), so a caller
with no brand in context — or a historical scan row, which carries no
pair-specific verdict of its own — gets “unknown” rather than another
brand’s answer.
When this brand last had the domain visually scanned.
The shared timestamp is whichever brand scanned the domain most recently, so on a shared hostname it is somebody else’s. NULL on the pair means this brand has not scanned it yet, which is exactly what the cooldown treats it as.
URL to the screenshot of the domain stored in Hetzner S3-compatible Object Storage
Whether this brand still has an unsent alert for the domain.
The shared flag means “somebody has one”, so after this brand’s alert was sent it would keep reporting true while another brand’s is pending.
A completeness of 0 means that the domain has no records set. The higher this number, the more likely the domain is actually used.
The domain’s scan timeline, most recent first.
On a domain that has only ever had single-brand history, the whole history is this brand’s own and renders untouched. Once branded rows exist, the domain has had a multi-brand period: the requesting brand then sees only its own rows, and NULL-brand rows are redacted because current association count can no longer prove which brand they belonged to.
object
Free text comment from the user.
User who submitted the feedback.
When the feedback was submitted.
Serializer for DomainScan model.
risk_score and visual_match are answers about a brand↔domain pair,
not about the domain (#954). When the caller puts a brand in the
serializer context — every brand-scoped endpoint does — both are rendered
from that brand’s association, so a domain two customers monitor shows each
of them the verdict computed against their own brand.
Without a brand in context the shared columns are rendered unchanged, which
is what the domain-global endpoints and the admin want. That column now
means “the worst score across every brand monitoring this domain” rather
than “the longest-monitored brand’s score” — see
DomainScan.get_risk_score.
verdict/verdict_reasoning/requires_human_review are the single
customer-facing verdict merged from the visual and content detectors
(BrandDomainAssociation.refresh_merged_verdict) and are what the
frontend should read going forward. visual_match is kept in the payload
as deprecated — do not remove it — because it still governs code paths
mid-migration; new consumers should read verdict instead.
object
The single customer-facing verdict, resolved for the requesting brand.
Unlike risk_score/visual_match there is no shared DomainScan
column to fall back to: the merged verdict has only ever lived on the
pair (BrandDomainAssociation.refresh_merged_verdict), so a caller
with no brand in context — or a historical scan row, which carries no
pair-specific verdict of its own — gets “unknown” rather than another
brand’s answer.
When this brand last had the domain visually scanned.
The shared timestamp is whichever brand scanned the domain most recently, so on a shared hostname it is somebody else’s. NULL on the pair means this brand has not scanned it yet, which is exactly what the cooldown treats it as.
URL to the screenshot of the domain stored in Hetzner S3-compatible Object Storage
Whether this brand still has an unsent alert for the domain.
The shared flag means “somebody has one”, so after this brand’s alert was sent it would keep reporting true while another brand’s is pending.
A completeness of 0 means that the domain has no records set. The higher this number, the more likely the domain is actually used.
The domain’s scan timeline, most recent first.
On a domain that has only ever had single-brand history, the whole history is this brand’s own and renders untouched. Once branded rows exist, the domain has had a multi-brand period: the requesting brand then sees only its own rows, and NULL-brand rows are redacted because current association count can no longer prove which brand they belonged to.
object
Free text comment from the user.
User who submitted the feedback.
When the feedback was submitted.
object
Takedown id; fetch the case at GET /core/api/takedowns/{id}/.
Current status of the running case.
REQUESTED- Requested (Pending Approval)OPEN- OpenIN_PROGRESS- In ProgressPENDING_RESPONSE- Pending ResponseCLOSED- ClosedFAILED- FailedREJECTED- Rejected
object
Takedown id; fetch the case at GET /core/api/takedowns/{id}/.
How the case ended: CLOSED (worked to a conclusion, see resolution) or FAILED (abandoned, no resolution).
CLOSED- ClosedFAILED- Failed
DOMAIN_SUSPENDED- Domain SuspendedCONTENT_REMOVED- Content RemovedSERVER_HOLD- Server HoldVOLUNTARY_TAKEDOWN- Voluntary TakedownUNRESOLVED- UnresolvedFALSE_POSITIVE- False Positive
Outcome of a CLOSED case. FALSE_POSITIVE means the analysts found no infringement. Null for FAILED, and for a CLOSED case that was closed without a resolution.
DOMAIN_SUSPENDED- Domain SuspendedCONTENT_REMOVED- Content RemovedSERVER_HOLD- Server HoldVOLUNTARY_TAKEDOWN- Voluntary TakedownUNRESOLVED- UnresolvedFALSE_POSITIVE- False Positive
When the case finished. For CLOSED this is the case’s closed_at; FAILED and undated legacy cases use a stable result timestamp.
Example
{ "source": "VARIATION", "latest_scan": { "user_feedback_type": "false_positive" }, "scans": [ { "user_feedback_type": "false_positive" } ], "open_takedown": { "status": "REQUESTED" }, "last_closed_takedown": { "status": "CLOSED", "resolution": "DOMAIN_SUSPENDED" }}The API key is missing, invalid, revoked or belongs to an inactive user.
object
Examplegenerated
{ "detail": "example"}The requested page or record does not exist or cannot be accessed.
object
Examplegenerated
{ "detail": "example"}Too many requests or failed authentication attempts. Try again later.
object
Examplegenerated
{ "detail": "example"}