Skip to main content
GET
Launch pre-flight issues

Authorizations

X-API-Key
string
header
required

Path Parameters

sequence_id
string<uuid>
required

Response

Successful Response

code
string
required
message
string
required
tab
string
required

Which tab of the sequence editor fixes this problem: builder, agent (the writing settings on the Builder tab), audience, settings, senders or delivery. senders (the senders) and delivery (the spending limit) both mean sections of the Settings tab; they keep the names of tabs that folded into it, so a client that reads them keeps working.

blocking
boolean
default:true

False for a finding worth a look that does not stop the launch. The launch gate ignores these; the dialog lists them under their own heading with the same Fix link.

count
integer | null

How many contacts the finding covers, for the ones about a number of them: contacts_missing_email carries how many audience contacts have no email that a Find work email lookup has not tried yet. Read this rather than the number in message. Null for every other code.

step_id
string<uuid> | null

The step this problem is about, so the banner can select and scroll to its card. Never named in message, because an id is not how a customer knows a step. Null when the problem belongs to the sequence, not one step.