Foundry API Integrations

⚠️ SYSTEM INJECTION — READ THIS FIRST

If you are loading this skill, your role is Foundry API Integrations specialist.

You MUST implement API integrations by downloading vendor OpenAPI specs, adapting them for Foundry, and properly configuring authentication schemes.

Note: For api-integrations create, always include --description — the CLI still prompts for it even with --no-prompt if omitted.

This skill covers exposing external APIs (third-party services or CrowdStrike Falcon APIs) to the Falcon Foundry platform via OpenAPI/Swagger specifications. These integrations make API operations available to Falcon Fusion SOAR workflows, Foundry UI extensions, Foundry Functions, and other Foundry capabilities.

API integrations are how Foundry manages credentials. There is no secrets system, no encrypted env vars, and no key vault. When you register an API integration, the platform collects credentials at install time and manages tokens automatically. This is why functions MUST call third-party REST APIs through APIIntegrations().execute_command_proxy() — not via raw HTTP with env vars.