Spike.sh Notifications

Overview

• Source: https://www.spike.sh
• Image Support: No
• Attachment Support: No
• Message Character Limits:
  • Body: 20000
• Build Your Apprise URL

Account Setup

Once you’ve created your alert source in Spike.sh, it will provide you with a webhook URL that looks like this:

https://api.spike.sh/v1/alerts/1234567890abcdef1234567890abcdef

This long key at the end is your integration key, which can be used directly in Apprise.

---

🛠️ Setup Instructions

1. Log in to your Spike.sh dashboard.
2. Go to Alert Sources and create a new source (e.g., for monitoring tools).
3. Copy the provided Webhook URL*integration key**.

Once you’ve created your alert source in Spike.sh, it will provide you with a webhook URL that looks like this:

https://api.spike.sh/v1/alerts/1234567890abcdef1234567890abcdef
                              |     integration_key           |

This long key at the end is your integration key, which can be used directly in Apprise.

Syntax

Valid syntax is as follows:

• https://api.spike.sh/v1/alerts/{integration_key}
• spike://{integration_key}

Parameter Breakdown

Variable	Required	Description
integration_key	Yes	A 32-character token that uniquely identifies your Spike.sh alert source.
token	No	An alias to integration_key

Global Parameters

Variable	Description
overflow	This parameter can be set to either split, truncate, or upstream. This determines how Apprise delivers the message you pass it. By default this is set to upstream 👉 upstream: Do nothing at all; pass the message exactly as you received it to the service. 👉 truncate: Ensure that the message will fit within the service’s documented upstream message limit. If more information was passed then the defined limit, the overhead information is truncated. 👉 split: similar to truncate except if the message doesn’t fit within the service’s documented upstream message limit, it is split into smaller chunks and they are all delivered sequentially there-after.
format	This parameter can be set to either text, html, or markdown. Some services support the ability to post content by several different means. The default of this varies (it can be one of the 3 mentioned at any time depending on which service you choose). You can optionally force this setting to stray from the defaults if you wish. If the service doesn’t support different types of transmission formats, then this field is ignored.
verify	External requests made to secure locations (such as through the use of https) will have certificates associated with them. By default, Apprise will verify that these certificates are valid; if they are not then no notification will be sent to the source. In some occasions, a user might not have a certificate authority to verify the key against or they trust the source; in this case you will want to set this flag to no. By default it is set to yes.
cto	This stands for Socket Connect Timeout. This is the number of seconds Requests will wait for your client to establish a connection to a remote machine (corresponding to the connect()) call on the socket. The default value is 4.0 seconds.
rto	This stands for Socket Read Timeout. This is the number of seconds the client will wait for the server to send a response. The default value is 4.0 seconds.
emojis	Enable Emoji support (such as providing :+1: would translate to 👍). By default this is set to no. Note: Depending on server side settings, the administrator has the power to disable emoji support at a global level; but default this is not the case.
tz	Identify the IANA Time Zone Database you wish to operate as. By default this is detected based on the configuration the server hosting Apprise is running on. You can set this to things like America/Toronto, or any other properly formated Timezone describing your area.

Examples

Using the simplified Apprise URL:

# Assuming our token is 1234567890abcdef1234567890abcdef

apprise -vv -t "Spike Alert" -b "Incident occurred" \
   spike://1234567890abcdef1234567890abcdef

Using the token as a URL parameter:

apprise -vv -t "Spike Alert" -b "Incident occurred" \
   spike://?token=1234567890abcdef1234567890abcdef

Using the full native webhook URL:

apprise -vv -t "Spike Alert" -b "Incident occurred" \
   https://api.spike.sh/v1/alerts/1234567890abcdef1234567890abcdef