Streamlane automatically sends passenger, crew, and flight information to connected government systems, ensuring full compliance with API/PNR requirements.
Each message is validated, scheduled, and sent according to the configured push times (such as H48 or H0), and acknowledgments are tracked in real time.

How It Works:

1. Flight Created or Updated – Passenger and crew data entered or modified.
2. Pre-validation – GOVlink checks for missing or invalid data before the message is built.
3. Scheduling – Messages are queued for automatic dispatch based on state-specific push timings.
4. Transmission – GOVlink sends the message at the scheduled time (or when ATD is declared).
5. Acknowledgment – The receiving authority confirms receipt (ACK) or returns an error.

Push times (H48, H24, H0, Ad-hoc) indicate when a message is sent relative to the flight’s scheduled or actual departure time.

---

Transmission Statuses

Possible transmission statuses are as follows:

State XXX not connected

This status will be displayed only when the state concerned by the flight departure or arrival is not connected to the platform for the provider/organization (see State configuration)

Flight list:

Flight detail:

Skipped

Also transmission skipped. This status will be displayed either:

• when a state (airport of) is connected but the flight direction s not in scope for the state (see States configuration Provider details screen).
• when a state is not requiring a message for a flight empty of passengers. This can be different depending on the state configuration and message type.
• when a domestic flight is in scope for the state, the skipped status is displayed for the arrival as messages are only sent once, for the departure.

Flight list:

Flight detail:

Scheduled

This status corresponds to a message that is scheduled to be sent to the given state depending on the push times configured (e.g. H48, H24, and H0)

Flight list:

Flight detail:

Waiting for departure

(ATD configured providers only) this status corresponds to a message that is scheduled to be sent when the ATD is is set by the provider. (H0 push only)

Flight list:

Flight detail:

Transmitted

This status will appear when the message was generated and transmitted to the state for a defined push (e.g H48, H24, and H0) as displayed in the flight history. If the concerned transmission was not the last one planned (multiple pushes), the status will pass to the “scheduled” for the next transmission. If the concerned push is the last one planned, the status will be Transmitted to the state at push time. 

Flight list:

Flight detail:

Waiting for ack

This status will appear when a message was sent to a state and the acknowledgment from the state is not yet received by the platform. (for state sending ack messages only)

Flight list:

Flight detail:

REJECTED BY STATE

If the message sent does not respect the format expected by the state, the status will be rejected. This status is available only for states sending an acknowledgment message.

Flight list:

Flight detail:

GENERATION ERROR

This status is displayed either:

• when an internal issue occurs in the system and the message was not yet generated
• when a state (airport of) is connected and requires “PAXLST” Message format; and not all of the required document details have been complete (see States configuration Provider details screen for States requiring “PAXLST” messages )

Flight list:

Flight detail: