info@ismena.com
Ismena websiteIsmena websiteIsmena websiteIsmena website
  • Home
  • About us
  • Technologies
    • Cloud Services
      • Google Cloud Platform
        • Networking
        • Compute
        • Storage
        • SAP on GCP
        • Google Maps
        • Data Center Modernization
    • Infrastructure
      • iSolution Services
      • Unified Communication
      • Network Security
      • Access Security & Control
      • Computing Platforms
      • Structured Cabling Infrastructure
      • Datacenter Infrastructure
      • Networking Infrastructure
      • Retail Analytics
      • Cloud Infrastructure
    • Integration
      • Apigee
      • IBM
      • Custom Connectors
    • Security
      • Security Consulting Services
      • Security Solutions
    • Data & AI
      • BigQuery, Looker
      • Gemini
    • Collaboration Tools
      • Google Workspace For Enterprise
    • ERP-CRM
      • Odoo
      • Salesforce
      • SAP on GCP
    • DevOps
      • GCP
      • SonarSource
    • Managed Service Provider
      • Managed Service Provider
    • App Development
      • App Development
    • Open Banking
      • Open banking
    • Chrome Devices
  • Unplugged Podcast
  • Blog
    • Success Stories
    • News
    • Articles
  • Careers
  • Contact Us

Technologies

Integration

Custom Connectors

Explore All Connectors

SpaceX Connector

SpaceX Connector

Connector Details

Type

Virtual machines, Single VM , BYOL

Runs on

Google Compute Engine

Last Update

24 October, 2024

Category

Overview

Documentation

Pricing

Support

Overview

The SpaceX Connector facilitates seamless integration with the SpaceX API v4, providing access to real-time and historical data on SpaceX launches, rockets, cores, capsules, crew, Starlink satellites, launchpads, landing pads, ships, company information, historical events, payloads, and the Tesla Roadster. This connector acts as a proxy to streamline data retrieval, supporting actions for fetching all resources, specific resource details by ID, and advanced querying with pagination and filtering.

Integration Overview

This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the SpaceX Connector. The SpaceX API is publicly accessible and requires no authentication, making it ideal for integration into GCP workflows for data analysis, visualization, or application development.

Supported Integration Action Points

  • getAllLaunches: Retrieves a list of all SpaceX launches.
  • getLaunchById: Retrieves details of a specific launch by ID.
  • queryLaunches: Queries launches with custom filters and pagination.
  • getPastLaunches: Retrieves a list of past SpaceX launches.
  • getUpcomingLaunches: Retrieves a list of upcoming SpaceX launches.
  • getLatestLaunch: Retrieves the most recent SpaceX launch.
  • getNextLaunch: Retrieves the next scheduled SpaceX launch.
  • getAllRockets: Retrieves a list of all SpaceX rockets.
  • getRocketById: Retrieves details of a specific rocket by ID.
  • queryRockets: Queries rockets with custom filters and pagination.
  • getAllCores: Retrieves a list of all SpaceX booster cores.
  • getCoreById: Retrieves details of a specific core by ID.
  • queryCores: Queries cores with custom filters and pagination.
  • getAllCapsules: Retrieves a list of all SpaceX capsules.
  • getCapsuleById: Retrieves details of a specific capsule by ID.
  • queryCapsules: Queries capsules with custom filters and pagination.
  • getAllCrew: Retrieves a list of all SpaceX crew members.
  • getCrewById: Retrieves details of a specific crew member by ID.
  • queryCrew: Queries crew members with custom filters and pagination.
  • getAllStarlink: Retrieves a list of all Starlink satellites.
  • queryStarlink: Queries Starlink satellites with custom filters and pagination.
  • getAllLaunchpads: Retrieves a list of all SpaceX launchpads.
  • getLaunchpadById: Retrieves details of a specific launchpad by ID.
  • queryLaunchpads: Queries launchpads with custom filters and pagination.
  • getAllLandpads: Retrieves a list of all SpaceX landing pads.
  • getLandpadById: Retrieves details of a specific landing pad by ID.
  • queryLandpads: Queries landing pads with custom filters and pagination.
  • getAllShips: Retrieves a list of all SpaceX ships.
  • getShipById: Retrieves details of a specific ship by ID.
  • queryShips: Queries ships with custom filters and pagination.
  • getCompanyInfo: Retrieves information about SpaceX as a company.
  • getAllHistory: Retrieves a list of historical SpaceX events.
  • getHistoryById: Retrieves details of a specific historical event by ID.
  • queryHistory: Queries historical events with custom filters and pagination.
  • getAllPayloads: Retrieves a list of all SpaceX payloads.
  • getPayloadById: Retrieves details of a specific payload by ID.
  • queryPayloads: Queries payloads with custom filters and pagination.
  • getRoadster: Retrieves data about Elon Musk’s Tesla Roadster in space.

Detailed Integration Documentation

All Launches Retrieval

Action getAllLaunches
Purpose Retrieves a comprehensive list of all SpaceX launches, including past and upcoming missions. This serves as the primary entry point for accessing launch data.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the base URL via CONNECTOR_ENV_SPACEX_BASE_URL environment variable (e.g., https://api.spacexdata.com/v4).
Output
  • Successful: Returns a JSON array of launch objects with:
    • id: Launch ID (string, e.g., "5eb87d46ffd86e000604b388").
    • name: Launch name (string, e.g., "CRS-20").
    • date_utc: Launch date in UTC (string, e.g., "2020-03-07T04:50:31.000Z").
    • success: Launch success status (boolean, e.g., true).
    • details: Launch description (string, nullable, e.g., "SpaceX's 20th and final Crew Resupply Mission...").
    • rocket: Rocket ID (string, e.g., "5e9d0d95eda69973a809d1ec").
    • launchpad: Launchpad ID (string, e.g., "5e9e4502f509094188566f88").
    • links: Object with media links (e.g., patch, reddit, flickr, presskit, webcast, wikipedia).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Configure the connector with the base URL.
  • Execute the getAllLaunches action.
  • Process the response to display launch data in a dashboard or store in a GCP BigQuery table.

Launch by ID Retrieval

Action getLaunchById
Purpose Retrieves details of a specific SpaceX launch by its ID. This helps users obtain targeted launch data for analysis or display.
Parameters
  • Required:
    • id: Launch ID (string, e.g., "5eb87d46ffd86e000604b388").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllLaunches for a single launch.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getLaunchById action with id=5eb87d46ffd86e000604b388.
  • Review the response to obtain launch details.
  • Use the data for detailed reporting or visualization.

Query Launches

Action queryLaunches
Purpose Queries SpaceX launches with custom filters and pagination, enabling flexible data retrieval for specific needs.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"success": true}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 25, "page": 1, "sort": {"date_utc": "desc"}}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with:
    • docs: Array of launch objects (same fields as getAllLaunches).
    • totalDocs: Total number of matching documents (integer).
    • limit: Number of documents per page (integer).
    • totalPages: Total pages (integer).
    • page: Current page (integer).
    • hasPrevPage: Previous page availability (boolean).
    • hasNextPage: Next page availability (boolean).
    • prevPage: Previous page number (integer, nullable).
    • nextPage: Next page number (integer, nullable).
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryLaunches action with query={"success": true} and options={"limit": 10, "page": 1}.
  • Process the paginated response for data analysis.
  • Store results in a GCP Cloud Storage bucket.

Past Launches Retrieval

Action getPastLaunches
Purpose Retrieves a list of past SpaceX launches, useful for historical analysis.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of launch objects (same fields as getAllLaunches).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getPastLaunches action.
  • Analyze past launch data for trends or reporting.
  • Store results in a GCP Dataflow pipeline.

Upcoming Launches Retrieval

Action getUpcomingLaunches
Purpose Retrieves a list of upcoming SpaceX launches, useful for planning or notifications.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of launch objects (same fields as getAllLaunches).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getUpcomingLaunches action.
  • Use the data to populate a notification system or calendar.
  • Trigger alerts via GCP Cloud Functions.

Latest Launch Retrieval

Action getLatestLaunch
Purpose Retrieves the most recent SpaceX launch, useful for displaying current mission status.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllLaunches for the latest launch.
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getLatestLaunch action.
  • Display the latest launch details on a dashboard.
  • Store data in a GCP Firestore database.

Next Launch Retrieval

Action getNextLaunch
Purpose Retrieves the next scheduled SpaceX launch, useful for upcoming mission tracking.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllLaunches for the next launch.
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getNextLaunch action.
  • Use the data for scheduling notifications or updates.
  • Integrate with GCP Pub/Sub for real-time alerts.

All Rockets Retrieval

Action getAllRockets
Purpose Retrieves a list of all SpaceX rockets, useful for cataloging vehicle data.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of rocket objects with:
    • id: Rocket ID (string, e.g., "5e9d0d95eda69973a809d1ec").
    • name: Rocket name (string, e.g., "Falcon 9").
    • description: Rocket description (string, e.g., "Falcon 9 is a two-stage rocket...").
    • wikipedia: Wikipedia URL (string, nullable, e.g., "https://en.wikipedia.org/wiki/Falcon_9").
    • flickr_images: Array of image URLs (array, e.g., ["https://farm5.staticflickr.com/4615/40143096241_11128929df_b.jpg"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllRockets action.
  • Display rocket data in a catalog or application.
  • Store in a GCP BigQuery table for analysis.

Rocket by ID Retrieval

Action getRocketById
Purpose Retrieves details of a specific SpaceX rocket by its ID.
Parameters
  • Required:
    • id: Rocket ID (string, e.g., "5e9d0d95eda69973a809d1ec").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllRockets for a single rocket.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getRocketById action with id=5e9d0d95eda69973a809d1ec.
  • Use the data for detailed rocket analysis or display.
  • Store in a GCP Cloud SQL database.

Query Rockets

Action queryRockets
Purpose Queries SpaceX rockets with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"name": "Falcon 9"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryRockets action with query={"name": "Falcon 9"} and options={"limit": 5}.
  • Process the response for filtered rocket data.
  • Store in a GCP Datastore.

All Cores Retrieval

Action getAllCores
Purpose Retrieves a list of all SpaceX booster cores.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of core objects with:
    • id: Core ID (string, e.g., "5e9e28a7f3591817f23b2660").
    • serial: Core serial number (string, e.g., "B1051").
    • status: Core status (string, e.g., "active").
    • last_update: Status update (string, nullable, e.g., "Landed successfully...").
    • launches: Array of launch IDs (array, e.g., ["5eb87d46ffd86e000604b388"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllCores action.
  • Analyze core data for reuse statistics.
  • Store in a GCP BigQuery table.

Core by ID Retrieval

Action getCoreById
Purpose Retrieves details of a specific SpaceX booster core by its ID.
Parameters
  • Required:
    • id: Core ID (string, e.g., "5e9e28a7f3591817f23b2660").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllCores for a single core.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getCoreById action with id=5e9e28a7f3591817f23b2660.
  • Use the data for core-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Cores

Action queryCores
Purpose Queries SpaceX booster cores with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"status": "active"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryCores action with query={"status": "active"} and options={"limit": 5}.
  • Process the response for filtered core data.
  • Store in a GCP Datastore.

All Capsules Retrieval

Action getAllCapsules
Purpose Retrieves a list of all SpaceX capsules.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of capsule objects with:
    • id: Capsule ID (string, e.g., "5e9e2c5cf3591885d43b2667").
    • serial: Capsule serial number (string, e.g., "C201").
    • status: Capsule status (string, e.g., "active").
    • type: Capsule type (string, e.g., "Dragon 2").
    • last_update: Status update (string, nullable, e.g., "Currently docked...").
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllCapsules action.
  • Analyze capsule data for mission planning.
  • Store in a GCP BigQuery table.

Capsule by ID Retrieval

Action getCapsuleById
Purpose Retrieves details of a specific SpaceX capsule by its ID.
Parameters
  • Required:
    • id: Capsule ID (string, e.g., "5e9e2c5cf3591885d43b2667").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllCapsules for a single capsule.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getCapsuleById action with id=5e9e2c5cf3591885d43b2667.
  • Use the data for capsule-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Capsules

Action queryCapsules
Purpose Queries SpaceX capsules with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"type": "Dragon 2"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryCapsules action with query={"type": "Dragon 2"} and options={"limit": 5}.
  • Process the response for filtered capsule data.
  • Store in a GCP Datastore.

All Crew Retrieval

Action getAllCrew
Purpose Retrieves a list of all SpaceX crew members.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of crew objects with:
    • id: Crew member ID (string, e.g., "5ebf1b7323f9e00e7c6460d").
    • name: Crew member name (string, e.g., "Robert Behnken").
    • status: Crew status (string, e.g., "active").
    • image: Image URL (string, nullable, e.g., "https://imgur.com/0smMgmh.png").
    • launches: Array of launch IDs (array, e.g., ["5eb87d46ffd86e000604b388"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllCrew action.
  • Display crew data in a personnel dashboard.
  • Store in a GCP BigQuery table.

Crew by ID Retrieval

Action getCrewById
Purpose Retrieves details of a specific SpaceX crew member by their ID.
Parameters
  • Required:
    • id: Crew member ID (string, e.g., "5ebf1b7323f9e00e7c6460d").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllCrew for a single crew member.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getCrewById action with id=5ebf1b7323f9e00e7c6460d.
  • Use the data for crew member profiles.
  • Store in a GCP Cloud SQL database.

Query Crew

Action queryCrew
Purpose Queries SpaceX crew members with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"status": "active"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryCrew action with query={"status": "active"} and options={"limit": 5}.
  • Process the response for filtered crew data.
  • Store in a GCP Datastore.

All Starlink Retrieval

Action getAllStarlink
Purpose Retrieves a list of all Starlink satellites.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of Starlink objects with:
    • id: Satellite ID (string, e.g., "5eed770f096e590191d4e9b9").
    • version: Satellite version (string, e.g., "v1.0").
    • height_km: Orbital height (number, nullable, e.g., 550).
    • longitude: Orbital longitude (number, nullable, e.g., -80.1234).
    • launch: Launch ID (string, nullable, e.g., "5eb87d46ffd86e000604b388").
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllStarlink action.
  • Analyze satellite data for orbital tracking.
  • Store in a GCP BigQuery table.

Query Starlink

Action queryStarlink
Purpose Queries Starlink satellites with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"version": "v1.0"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryStarlink action with query={"version": "v1.0"} and options={"limit": 5}.
  • Process the response for filtered satellite data.
  • Store in a GCP Datastore.

All Launchpads Retrieval

Action getAllLaunchpads
Purpose Retrieves a list of all SpaceX launchpads.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of launchpad objects with:
    • id: Launchpad ID (string, e.g., "5e9e4502f509094188566f88").
    • name: Launchpad name (string, e.g., "LC-39A").
    • full_name: Full name (string, e.g., "Launch Complex 39A").
    • status: Launchpad status (string, e.g., "active").
    • launches: Array of launch IDs (array, e.g., ["5eb87d46ffd86e000604b388"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllLaunchpads action.
  • Display launchpad data in a facilities dashboard.
  • Store in a GCP BigQuery table.

Launchpad by ID Retrieval

Action getLaunchpadById
Purpose Retrieves details of a specific SpaceX launchpad by its ID.
Parameters
  • Required:
    • id: Launchpad ID (string, e.g., "5e9e4502f509094188566f88").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllLaunchpads for a single launchpad.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getLaunchpadById action with id=5e9e4502f509094188566f88.
  • Use the data for launchpad-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Launchpads

Action queryLaunchpads
Purpose Queries SpaceX launchpads with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"status": "active"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryLaunchpads action with query={"status": "active"} and options={"limit": 5}.
  • Process the response for filtered launchpad data.
  • Store in a GCP Datastore.

All Landing Pads Retrieval

Action getAllLandpads
Purpose Retrieves a list of all SpaceX landing pads.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of landing pad objects with:
    • id: Landing pad ID (string, e.g., "5e9e3032383ecb6bb234e7ca").
    • name: Landing pad name (string, e.g., "LZ-1").
    • full_name: Full name (string, e.g., "Landing Zone 1").
    • status: Landing pad status (string, e.g., "active").
    • type: Landing pad type (string, e.g., "RTLS").
    • launches: Array of launch IDs (array, e.g., ["5eb87d46ffd86e000604b388"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllLandpads action.
  • Analyze landing pad data for recovery operations.
  • Store in a GCP BigQuery table.

Landing Pad by ID Retrieval

Action getLandpadById
Purpose Retrieves details of a specific SpaceX landing pad by its ID.
Parameters
  • Required:
    • id: Landing pad ID (string, e.g., "5e9e3032383ecb6bb234e7ca").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllLandpads for a single landing pad.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getLandpadById action with id=5e9e3032383ecb6bb234e7ca.
  • Use the data for landing pad-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Landing Pads

Action queryLandpads
Purpose Queries SpaceX landing pads with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"type": "RTLS"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryLandpads action with query={"type": "RTLS"} and options={"limit": 5}.
  • Process the response for filtered landing pad data.
  • Store in a GCP Datastore.

All Ships Retrieval

Action getAllShips
Purpose Retrieves a list of all SpaceX ships.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of ship objects with:
    • id: Ship ID (string, e.g., "5ea6ed2e080df40006f3c0e9").
    • name: Ship name (string, e.g., "GO Navigator").
    • type: Ship type (string, e.g., "Recovery Ship").
    • status: Ship status (string, e.g., "active").
    • launches: Array of launch IDs (array, e.g., ["5eb87d46ffd86e000604b388"]).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllShips action.
  • Analyze ship data for recovery operations.
  • Store in a GCP BigQuery table.

Ship by ID Retrieval

Action getShipById
Purpose Retrieves details of a specific SpaceX ship by its ID.
Parameters
  • Required:
    • id: Ship ID (string, e.g., "5ea6ed2e080df40006f3c0e9").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllShips for a single ship.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getShipById action with id=5ea6ed2e080df40006f3c0e9.
  • Use the data for ship-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Ships

Action queryShips
Purpose Queries SpaceX ships with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"type": "Recovery Ship"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryShips action with query={"type": "Recovery Ship"} and options={"limit": 5}.
  • Process the response for filtered ship data.
  • Store in a GCP Datastore.

Company Information Retrieval

Action getCompanyInfo
Purpose Retrieves information about SpaceX as a company, useful for organizational data.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with:
    • id: Company ID (string, e.g., "5e9d0d95eda69973a809d1ec").
    • name: Company name (string, e.g., "SpaceX").
    • founder: Founder name (string, e.g., "Elon Musk").
    • founded: Founding year (integer, e.g., 2002).
    • headquarters: Object with address, city, state (e.g., {"address": "1 Rocket Road", "city": "Hawthorne", "state": "California"}).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getCompanyInfo action.
  • Display company data in an about page or report.
  • Store in a GCP Firestore database.

All Historical Events Retrieval

Action getAllHistory
Purpose Retrieves a list of historical SpaceX events, useful for historical analysis.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of history objects with:
    • id: Event ID (string, e.g., "5eb87d46ffd86e000604b389").
    • title: Event title (string, e.g., "Falcon 1 Makes History").
    • event_date_utc: Event date in UTC (string, e.g., "2008-09-28T00:00:00.000Z").
    • details: Event description (string, e.g., "Falcon 1 becomes the first...").
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllHistory action.
  • Analyze historical events for research or reporting.
  • Store in a GCP BigQuery table.

Historical Event by ID Retrieval

Action getHistoryById
Purpose Retrieves details of a specific SpaceX historical event by its ID.
Parameters
  • Required:
    • id: Event ID (string, e.g., "5eb87d46ffd86e000604b389").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllHistory for a single event.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getHistoryById action with id=5eb87d46ffd86e000604b389.
  • Use the data for event-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Historical Events

Action queryHistory
Purpose Queries SpaceX historical events with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"title": "Falcon"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryHistory action with query={"title": "Falcon"} and options={"limit": 5}.
  • Process the response for filtered historical data.
  • Store in a GCP Datastore.

All Payloads Retrieval

Action getAllPayloads
Purpose Retrieves a list of all SpaceX payloads.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON array of payload objects with:
    • id: Payload ID (string, e.g., "5eb0e4c7b6c3bb0006eeb1e5").
    • name: Payload name (string, e.g., "Starlink-1").
    • type: Payload type (string, e.g., "Satellite").
    • orbit: Orbit type (string, e.g., "LEO").
    • launch: Launch ID (string, nullable, e.g., "5eb87d46ffd86e000604b388").
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getAllPayloads action.
  • Analyze payload data for mission planning.
  • Store in a GCP BigQuery table.

Payload by ID Retrieval

Action getPayloadById
Purpose Retrieves details of a specific SpaceX payload by its ID.
Parameters
  • Required:
    • id: Payload ID (string, e.g., "5eb0e4c7b6c3bb0006eeb1e5").
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as getAllPayloads for a single payload.
  • Failure: Returns error details (e.g., error-type: invalid-id).
Workflow Example
  • Execute the getPayloadById action with id=5eb0e4c7b6c3bb0006eeb1e5.
  • Use the data for payload-specific analysis.
  • Store in a GCP Cloud SQL database.

Query Payloads

Action queryPayloads
Purpose Queries SpaceX payloads with custom filters and pagination.
Parameters
  • Required:
    • query: Query object for filtering (object, e.g., {"type": "Satellite"}).
    • options: Options for pagination and sorting (object, e.g., {"limit": 10, "page": 1}).
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with the same fields as queryLaunches.
  • Failure: Returns error details (e.g., error-type: invalid-query).
Workflow Example
  • Execute the queryPayloads action with query={"type": "Satellite"} and options={"limit": 5}.
  • Process the response for filtered payload data.
  • Store in a GCP Datastore.

Roadster Retrieval

Action getRoadster
Purpose Retrieves data about Elon Musk's Tesla Roadster in space, useful for unique data points.
Parameters
  • Required:
    • None
  • Optional:
    • None
Configuration
  • Ensure the connector is configured with the correct base URL.
Output
  • Successful: Returns a JSON object with:
    • id: Roadster ID (string, e.g., "5eb75f0842fea42237d7f3f4").
    • name: Roadster name (string, e.g., "Elon Musk's Tesla Roadster").
    • norad_id: NORAD ID (integer, e.g., 43205).
    • orbit_type: Orbit type (string, e.g., "heliocentric").
    • apoapsis_au: Apoapsis in AU (number, e.g., 1.664).
    • periapsis_au: Periapsis in AU (number, e.g., 0.986).
  • Failure: Returns error details (e.g., error-type: server-error).
Workflow Example
  • Execute the getRoadster action.
  • Display Roadster data in an educational application.
  • Store in a GCP Firestore database.

Workflow Creation with the Connector

Example Workflow: Launch Tracking and Analysis

Retrieve All Launches

  • Use the getAllLaunches action to fetch a list of all SpaceX launches.
  • Identify key launches for further analysis (e.g., successful launches).

Query Specific Launches

  • Execute the queryLaunches action with query={“success”: true} and options={“limit”: 10, “page”: 1, “sort”: {“date_utc”: “desc”}} to fetch recent successful launches.
  • Process the response to extract launch details for a dashboard.

Fetch Latest and Next Launches

  • Use the getLatestLaunch and getNextLaunch actions to retrieve the most recent and upcoming launches.
  • Use the data to populate a real-time mission tracking system.

Analyze Rocket and Core Data

  • Execute the getAllRockets and getAllCores actions to fetch rocket and core data.
  • Use the queryRockets and queryCores actions with filters (e.g., query={“name”: “Falcon 9”} or query={“status”: “active”}) for detailed analysis.
  • Store results in a GCP BigQuery table for analytics.

Track Starlink Satellites

  • Execute the getAllStarlink action to fetch all Starlink satellite data.
  • Use the queryStarlink action with query={“version”: “v1.0”} to filter specific satellites.
  • Integrate with a GCP Dataflow pipeline for orbital tracking.

Enhance UI with Company and Historical Data

  • Execute the getCompanyInfo and getAllHistory actions to fetch SpaceX company and historical event data.
  • Integrate the data into a GCP-hosted web application for enhanced user experience.

Pricing

Request a Quote

Support

For Technical support please contact us on

custom-connectors-support@isolutions.sa

iSolution logo - white - transparent 250 px

iSolution logo - white - transparent 250 px

A tech solution company dedicated to providing innovation thus empowering businesses to thrive in the digital age.

  • Home
  • About us
  • Blog
  • Careers
  • Success Stories
  • News
  • Articles
  • Contact Us
  • Terms and conditions
  • Privacy Policy
© Copyright 2024 iSolution | All Rights Reserved
  • Home
  • About us
  • Technologies
    • Cloud Services
      • Google Cloud Platform
        • Networking
        • Compute
        • Storage
        • SAP on GCP
        • Google Maps
        • Data Center Modernization
    • Infrastructure
      • iSolution Services
      • Unified Communication
      • Network Security
      • Access Security & Control
      • Computing Platforms
      • Structured Cabling Infrastructure
      • Datacenter Infrastructure
      • Networking Infrastructure
      • Retail Analytics
      • Cloud Infrastructure
    • Integration
      • Apigee
      • IBM
      • Custom Connectors
    • Security
      • Security Consulting Services
      • Security Solutions
    • Data & AI
      • BigQuery, Looker
      • Gemini
    • Collaboration Tools
      • Google Workspace For Enterprise
    • ERP-CRM
      • Odoo
      • Salesforce
      • SAP on GCP
    • DevOps
      • GCP
      • SonarSource
    • Managed Service Provider
      • Managed Service Provider
    • App Development
      • App Development
    • Open Banking
      • Open banking
    • Chrome Devices
  • Unplugged Podcast
  • Blog
    • Success Stories
    • News
    • Articles
  • Careers
  • Contact Us
Ismena website

Register To Palo Alto & iSolution Event

Register to IBM x iSolution Event

Register to Gemini in Action Workshop

[forminator_form id=”14485″]

Registration To Amman Unplugged Event

[forminator_form id=”14419″]

Register to Gemini in Action Workshop

[forminator_form id=”14298″]

Tech and Culture Riyadh

[forminator_form id=”13094″]