Skip to main content
Solved

Google SecOps SOAR webhook rejects Canarytokens URL validation

  • Sep 10, 2026 10:19 AM UTC
  • 2 replies
  • 89 views

d_patel_dj
Forum|alt.badge.img+6

Hi all,

I am wondering whether this is a Canary issue or a Secops one but I am trying to send alerts from a free Canarytokens into a Google SecOps SOAR webhook.

What I have configured:

 

In SecOps SOAR, I created and enabled a webhook. The mandatory alert fields are mapped from a Canarytokens payload as follows:

  • TicketId → token
  • SourceSystemName → static value: Canarytokens
  • Name → token_type
  • DeviceVendor → static value: Thinkst
  • RuleGenerator → static value: Canarytokens
  • StartTime → time

This is what the payload looks like: 

{
  "channel": "DNS",
  "token_type": "adobe_pdf",
  "src_ip": "0.0.0.0",
  "token": "example-canary-token-id",
  "time": "2026-09-09 15:27:23 (UTC)",
  "memo": "Test",
  "additional_data": {
    "geo_info": {
      "country": "US",
      "city": "Example City",
      "org": "Example ISP"
    },
    "time_hm": "15:27",
    "time_ymd": "2026/09/09"
  },
  "public_domain": "canarytokens.org"
}

 

The Testing feature in the SecOps webhook returns:

{

  "status": 200,

  "statusText": "OK"

}

Problem

When I paste the SecOps webhook URL into Canarytokens during token creation, Canarytokens returns:

Invalid webhook supplied. Confirm you can POST to this URL.

I can successfully use the same Canarytokens token with a temporary ngrok endpoint that returns 200 OK, and ngrok captures the JSON shown above. This suggests Canarytokens can reach the endpoint and sends a valid POST body.

Question

Does anyone know why the SecOps webhook test succeeds with HTTP 200, but Canarytokens rejects the same webhook URL during its validation step?

 

Thanks in advance! 

 

Best answer by d_patel_dj

Thanks for the reply! 

Turns out the issue was the StartTime mapping format. 

What fixed it:

  1. Used the SecOps webhook URL with apiKey exactly as provided (and ensured path format was correct:
    .../webhooks/<webhook-id>:ingest?apiKey=...).
  2. In Data Mapping, mapped StartTime from Canary field time.
  3. Converted Canary time format from
    2026-09-09 15:27:23 (UTC)
    to ISO8601 format required by SecOps: 2026-09-09T15:27:23Z
  4. Expression used: | "time" | replace(" (UTC)","Z") | replace(" ","T")

Thanks for the help though! 

 

View original

2 replies

Eoved
Forum|alt.badge.img+10
  • Bronze 4
  • Sep 12, 2026 4:27 PM UTC

Hi,

A common mistake is providing the webhook URL without the required values.

ENDPOINT_URL: The  endpoint URL obtained when you create an HTTPS webhook 
API_KEY: The API key created for the webhook feed to authenticate with Google SecOps.
SECRET: The secret key generated when you create an HTTPS webhook feed.

You also need to make sure that your client application supports custom headers. If it does not, you can use a URL like the following:
ENDPOINT_URL?key=API_KEY&secret=>SECRET
 


d_patel_dj
Forum|alt.badge.img+6
  • Author
  • Bronze 2
  • Answer
  • Sep 14, 2026 10:14 AM UTC

Thanks for the reply! 

Turns out the issue was the StartTime mapping format. 

What fixed it:

  1. Used the SecOps webhook URL with apiKey exactly as provided (and ensured path format was correct:
    .../webhooks/<webhook-id>:ingest?apiKey=...).
  2. In Data Mapping, mapped StartTime from Canary field time.
  3. Converted Canary time format from
    2026-09-09 15:27:23 (UTC)
    to ISO8601 format required by SecOps: 2026-09-09T15:27:23Z
  4. Expression used: | "time" | replace(" (UTC)","Z") | replace(" ","T")

Thanks for the help though!