Skip to main content

Integration Testing

In order to test your integration with the Maritime Sentry API, Vantor offers a few endpoints to help you get started. These enable a rapid testing cycle where Vantor will exercise the full callback workflow, just much accelerated (within a few minutes) compared to real operations where the timeframe from tip submission through data delivery is measured in hours or days.

Submitting a Test Tip​

The test tip endpoint accepts the same payload as the live /submit-tips endpoint, letting you verify your tip format and exercise the full EO tipping callback sequence without placing real satellite orders.

See Test endpoint for verifying integration for the API reference.

Workflow​

  1. Your tip is validated and a tipIdentifier is returned synchronously — same as the live endpoint
  2. One valid tip is selected for further processing; any remaining valid tips receive a No_Orders_Possible
  3. A random number of satellites are assessed for geometric access to the target (respecting any vehicles constraint you specified)
    • If no satellites have access, a No_Orders_Possible is sent and the workflow ends
  4. A simulated order is generated for each satellite with access and an Order_Placed is sent for each
  5. One order is randomly selected as the successful collection and an Inventory_Collected is sent for an image strip from that satellite
  6. If the tip specified deliverFullStrip, the full strip tiles are staged in S3 and a Full_Strip_Available is sent
  7. The vessel detect products are staged in S3 and a Products_Available is sent

Notes​

  • Many outcomes are randomized; submitting the same tip twice may produce different results (different satellites, different access determinations)
  • Satellite access is not computed from real ephemeris; it is arbitrary
  • The delivered image strip is from the same satellite as the simulated order, with metadata adjusted to align with the order's time and geometry
  • Callbacks arrive within seconds of each other rather than hours, to keep testing fast

Triggering a Watchbox Data Delivery​

In operations, watchbox deliveries are triggered when new imagery is collected that overlaps the watchbox's defined geometry. For integration testing, you can simulate this by calling a dedicated endpoint that exercises the full watchbox delivery workflow against a real pre-existing image strip — without requiring an actual satellite collection.

See Initiate Test Watchbox Workflow for the API reference.

Workflow​

  1. A random pre-existing image strip is selected from the database
  2. A synthetic watchbox geometry is fabricated around the strip's footprint
  3. A Watchbox_Inventory_Collected is sent to all configured delivery channels (S3, REST callback URL, email)
  4. A sample detections ZIP is uploaded to the delivery S3 bucket
  5. If deliverFullStrip is enabled (explicitly or via configuration), a Full_Strip_Available is sent
  6. A Products_Available is sent with a delivery manifest pointing to the sample products

The endpoint returns 202 Accepted immediately. All callbacks arrive within a few minutes.

Notes​

  • The customer/mission must be configured with Vantor and must have the EO_Vessel_Detect product type enabled
  • The same strip may be selected across multiple calls
  • The synthetic watchbox geometry is not persisted and has no effect on live watchbox records
  • The detections ZIP is a real sample file with vessel metadata and chips, derived from the selected strip
  • Callbacks arrive within seconds of each other rather than hours, to keep testing fast