---
title: "Get the DKIM selector index"
method: GET
path: "/sources/dkim-index"
tags: ["Source"]
---

# Get the DKIM selector index

`GET /sources/dkim-index`

## Request

- Base URL: `https://api.palisade.email`
- URL: `https://api.palisade.email/sources/dkim-index`
- Auth: one of:
  - none
  - HTTP bearer
  - HTTP basic

The compact index used to name the DKIM keys already published for a domain. A key is matched either by `selectors`, the selector conventions a source publishes under, or by `base_domains`, the zones its CNAME targets sit in — the latter being the only signal that identifies a per-customer selector such as HubSpot's `hs1-<portalId>`. Only sources carrying at least one of the two appear. Authentication is optional, as on the list endpoint.

## Response `200`

Success

- object
  - `data` object[], required
    - `id` string, uuid, required
    - `name` string, required
    - `logo_url` string, nullable, required
    - `homepage` string, nullable, required: The source's home page. Free text on the record rather than a validated URL - a handful of sources carry a bare hostname such as `samanage.com` - so treat it as a hostname that may or may not carry a scheme.
    - `selectors` string[], required: DKIM selectors this source is known to publish under. Matched against the selector of a key already in DNS; they are per-source conventions, not values to publish on a customer's behalf.
    - `base_domains` string[], required: Domains this source signs from. A DKIM CNAME whose target sits under one of these belongs to this source, which is the only signal that identifies a per-customer selector such as HubSpot's `hs1-<portal>`.
  - `page_info` object, required
    - `count` number, required
    - `page` number, required
    - `per_page` number, required

---

[API](https://skmtc.dev/palisade/apis/palisade-api.md) · [All operations](https://skmtc.dev/palisade/apis/palisade-api/llms.txt) · [OpenAPI document](https://skmtc.dev/palisade/apis/palisade-api/revisions/37b4ae5a7766?raw)