DomainSource

Confirm or update a sender

post/domains/{domainId}/sources/{sourceId}

Request

  • Base URL: https://api.palisade.email
  • URL: https://api.palisade.email/domains/{domainId}/sources/{sourceId}
  • Auth: one of:
    • HTTP bearer
    • HTTP basic

Path parameters

domainIdstring uuid required
sourceIdstring uuid required

Headers

Palisade-Version'2025-04-30' | 'unstable' required

Request body

confirmation_status'confirmed' | 'discarded' | 'requires_confirmation' required

Response

Success

idstring uuid required
is_knownboolean required
source_idstring nullable required

The catalogue source this sender was matched to, or null when it is not one Palisade recognises. Lets a caller line a sender up with the SPF include or DKIM key it belongs to.

spf_valuestring nullable required

The SPF mechanism discovery observed for this sender, when it saw one.

source_namestring nullable required
source_homepagestring nullable required
sending_domainstring nullable required
dkim_selectorsstring[] required
confirmation_status'confirmed' | 'discarded' | 'requires_confirmation' required
confirmed_atstring date-time nullable required
last_seen_atstring nullable required

The last day (YYYY-MM-DD) this sender was seen sending for the domain, across all recorded history rather than a recent window, so a sender silent for a year still reports the day it went quiet. Null when no sending has been recorded for it yet. Reported from daily aggregates that can trail live reporting by a few days, so treat it as a date rather than a timestamp. Only counts sending observed since the domain was added to Palisade.

last_spf_aligned_atstring nullable required

The last day (YYYY-MM-DD) mail from this sender passed aligned SPF for the domain. Distinct from last_seen_at: a sender that still sends but no longer passes SPF has an SPF problem, not a disused include. Null when it has never passed aligned SPF in recorded history.

Example response

{
  "last_seen_at": "2025-09-14",
  "last_spf_aligned_at": "2025-09-14"
}

Changes

No recorded changes to this operation across all 1 revision of this API.