Skip to main content
POST
Validate an automation

Authorizations

Authorization
string
header
required

An API key from Settings → API keys in the inDM app, sent as Authorization: Bearer indm_.... Keys belong to one workspace and carry a scope: read for GET routes and the validate dry run, full for everything. Keep keys on your server; never ship one to a browser or a mobile app.

Body

application/json

A proposed automation to check. Nothing is saved.

keyword
string
required

The one word a fan comments to trigger it. Case-insensitive.

Example:

"GUIDE"

dm_message
string
required

The direct message the fan receives.

Example:

"Here's the spring planting guide. Enjoy it."

goal
string

What you want to happen, in your own words.

Example:

"Send the spring guide to anyone who comments GUIDE"

button_label
string

The opt-in button's label. Up to 20 characters.

Example:

"Send me the guide"

public_reply
string

A public reply posted under the fan's comment.

The link the DM delivers.

Example:

"https://example.com/spring-guide"

language
string

The two-letter code of the language the copy is written in, such as en, es or ko.

Example:

"en"

Response

The check. ready is true when nothing would stop it working.

specification
object
required

The normalised automation, as inDM would build it.

ready
boolean
required

True when problems is empty, so nothing would stop it working.

Example:

true

problems
object[]
required

What would make it misfire, in the order found. Empty when ready is true.

Example:
notes
object[]
required

Facts about how it will behave once live.

Example: