Integration Environment

The SatVu integration environment provides a safe, simulated space to develop and test platform integrations without consuming production satellite capacity or incurring charges. It mirrors the core functionality of the production platform, allowing you to build confidence in your workflows before deploying to live operations.

Benefits of the integration environment

The integration environment offers several key advantages for development and testing:

• Risk-free testing - Experiment with all catalog and tasking APIs without affecting real satellite scheduling or consuming actual data credits
• Accelerated development - Test end-to-end order workflows quickly, with guaranteed fulfillment on the first satellite pass
• Generous credit allocation - Receive ample credits to support extensive integration testing without budget constraints
• Production-equivalent structure - All API endpoints, response formats, and delivery structures match production exactly, ensuring smooth transitions
• Full workflow validation - Test your integration against the complete order lifecycle, from submission through to data delivery

Getting access

Access to the integration environment is available to all SatVu customers. To request access, contact your SatVu account representative or the SatVu Support team (support@satellitevu.com). Once provisioned, you'll receive access to a dedicated integration contract configured specifically for testing.

info

When using the API, your client_id and client_secret remain the same across all contracts. To access the integration environment, simply provide the contract_id of your integration contract in your API requests.

How the integration environment works

The integration environment replicates the production platform's behavior while using simulated data and simplified satellite operations. Here's what to expect:

Image data

All imagery delivered through the integration environment is fully simulated and clearly marked as 'NotSat' data:

• Simulated content - Images do not represent real captures and are not necessarily representative of your order parameters, such as day/night conditions or specific thermal characteristics
• Cloud-free imagery - All images are delivered without cloud cover, ensuring consistent test data
• Production-equivalent delivery - Folder structures, file formats, metadata, and delivery mechanisms are identical to production, allowing you to validate your data processing pipelines
• NotSat watermark - All delivered images include a 'NotSat' watermark to clearly indicate the data is simulated

info

While the image content is simulated, the file formats (Cloud Optimised GeoTIFF), metadata (STAC-compliant), and delivery structure exactly match production data products.

Data delivered in the integration environment should not be used for analysis. It is intended solely to represent production file formats and delivery structures.

Feasibility checks

Feasibility checks are based on HotSat-2 satellite passes over your requested location. However, the checks do not account for:

• Satellite capacity constraints
• Planning horizons or scheduling constraints
• Real-world operational limitations

This simplified approach ensures that feasibility checks return quickly and allow you to test your integration logic without the complexity of production scheduling.

Order fulfillment

The integration environment is designed to provide fast, predictable fulfillment:

• Guaranteed fulfillment - All orders will successfully fulfill, regardless of operational constraints
• First-pass capture - Orders are fulfilled on the first satellite pass over the requested location, allowing you to observe the complete order lifecycle
• Full status progression - Orders progress through standard production statuses: staged > in progress > fulfilled

info

Orders placed with a start date more than 1 month in the future will not be fulfilled. Ensure your test orders have start dates within the next month.

Order status timeline

While orders in the integration environment follow the same status progression as production, the timelines differ significantly due to the simulated nature of the environment:

1. Staged - After submission, orders remain in the staged status. During this time, the full order modification and cancellation workflows can be tested
2. In progress - Approximately 10 minutes before the first satellite pass over the target location, the order automatically transitions to in progress
3. Fulfilled - The image processor generates a NotSat image and fulfills the order approximately 15 minutes after transitioning to in progress, moving it to the fulfilled status

This accelerated timeline differs from production, where status transitions are controlled by actual satellite scheduling, capture windows, and ground station availability. The simplified progression enables you to test order monitoring, webhook integrations, and data download workflows without waiting for real satellite operations.

Pricing and billing

Each integration contract is provisioned with an allocation of credits for testing purposes:

• Non-indicative pricing - Pricing displayed in the integration environment does not represent actual pricing for SatVu products
• No billing - Credits used in the integration environment are not billed to your account
• Generous allocation - You'll receive sufficient credits to support comprehensive testing scenarios

Key differences from production

While the integration environment closely mirrors production, be aware of these differences:

Aspect	Integration environment	Production environment
Image content	Fully simulated, not representative of order parameters	Real satellite captures matching order specifications
Cloud cover	Always cloud-free	Subject to actual weather conditions
Fulfillment	Guaranteed on first pass	Subject to satellite availability and operational priorities
Feasibility	Based on HotSat-2 passes only	Accounts for satellite capacity and operational factors
Credits and billing	Non-indicative pricing, not billed	Actual pricing and billing according to contract terms
Satellite capacity	Does not impact real satellite operations	Orders consume actual satellite tasking capacity

Best practices

To make the most of the integration environment:

• Test all workflows - Use the integration environment to validate your entire integration, from authentication through to data download and processing
• Validate error handling - While orders in the integration environment always succeed, you can test error handling by providing invalid parameters or simulating edge cases in your code
• Transition carefully - Before moving to production, review your integration to ensure you're handling real-world scenarios like partial cloud cover, scheduling delays, and fulfillment constraints
• Monitor webhooks - If you're using webhooks, test them thoroughly in the integration environment to ensure your endpoints correctly handle all order status transitions

Getting help

If you have questions about the integration environment or encounter issues during testing, please reach out to the SatVu support team through your usual channels. We're here to help ensure your integration is successful.