Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Technical & Operational API Details

Authentication, upload times and other key technical details of the API.

Key Technical & Operational Details

  • Authentication: Access is secured via user-specific HTTP Bearer Tokens.
  • Upload Times: When uploading plots, processing time depends on the size and complexity of the shapes. While most are ready in minutes, please allow up to 24 hours for large datasets.
  • Real-time Access: Once your plots are stored on the platform, retrieving their risk results is instantaneous.
  • Bulk Processing: Our Bulk Upload API allows you to monitor the status of large data transfers and provides clear, self-explanatory error messages if a geometry fails validation.
  • Concurrency: Our API handles multiple requests simultaneously. The only exception is when uploading plots for the same supplier, which requires sequential calls to ensure data integrity.
  • Integration with ERPs:  Satelligence is fully compatible with any ERP system, including SAP, for data exchange. This is because we accept data via standard HTTP API uploads, specifically GeoJSON files for plot locations and associated metadata. Any ERP system can be configured to export the required fields and then push this data to Satelligence. This integration can be achieved using the Bulk Upload API directly, or through an intermediary layer such as middleware, an ETL tool, SAP PI/PO or CPI, or a custom integration job.

Tips for Large-Scale Integration

  • Handling Large Batches: If your upload contains thousands of plots, we recommend using the "Proceed with Errors" logic as your default secondary step to ensure high availability of your data.
  • Sequential vs. Parallel: To maintain a clean database, remember that while you can run many different uploads at once, any uploads involving the same Supplier ID must be sent one after the other (sequentially).
  • Error Logs: Always store the error messages returned by the API in your own logs. Since our messages are "self-explanatory" (e.g., "Plot is outside the specified country"), they can be passed directly to your data providers to help them fix the source files.