frappe-external-api-connector

Generate a reusable API client class using this Skill to handle GET and POST requests, authentication headers, timeouts, and HTTP error mapping. The generated code integrates with Frappe's configuration for secure credential storage and supports OAuth 2.0 token flows with caching.

Yes. This Skill implements OAuth 2.0 token flows with built-in caching, allowing secure token-based authentication with external services. Tokens are managed through Frappe's configuration system to keep credentials out of your codebase.

The generated ExternalAPIClient class maps common HTTP errors and implements timeout handling automatically. It provides structured error responses so your Frappe workflows can gracefully handle failures from payment gateways, shipping APIs, or other external data sources.

Store API keys and endpoint URLs in Frappe's frappe.conf configuration rather than hardcoding them. This Skill's generated client class retrieves credentials from configuration at runtime, keeping sensitive data out of code repositories.

Yes. The ExternalAPIClient class is designed as a reusable component for any REST API. You can instantiate it with different endpoints and credentials to connect Frappe to payment gateways, shipping carriers, weather services, or other external APIs simultaneously.

No. This Skill generates a standardized ExternalAPIClient with built-in HTTP error mapping and timeout handling. The same client works across different external services, reducing boilerplate and ensuring consistent error responses throughout your Frappe workflows.