api-gateway

Proxy native third-party API calls through a managed OAuth gateway.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/papachong/RHClaw --skill api-gateway-papachong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/papachong/RHClaw/tree/main/RHClaw-Desktop/src-tauri/skills/api-gateway
Command: npx skills add https://github.com/papachong/RHClaw --skill api-gateway-papachong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a secure, managed proxy to call native third-party APIs without requiring direct user-managed OAuth handling, reducing integration complexity and credential handling for client applications.

Core Features & Use Cases

  • Managed OAuth Connections: Centralizes OAuth flows and tokens so apps only need the MATON_API_KEY to authenticate to Maton while users explicitly authorize each third-party service.
  • Passthrough API Proxy: Call native endpoints for services like Slack, Google Workspace, GitHub, Notion, Stripe, and more using a single base URL and service prefix.
  • Connection Management: Create, list, inspect, and delete service connections; optionally target a specific connection via Maton-Connection header.
  • Use Case: Send Slack messages, query Google Sheets, create GitHub issues, or list Stripe customers from one unified gateway while keeping per-service OAuth scopes isolated.

Quick Start

Make a native Slack API call by POSTing a JSON message to https://gateway.maton.ai/slack/api/chat.postMessage and include Authorization: Bearer YOUR_MATON_API_KEY in the request headers.

Frequently Asked Questions about api-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely call third-party APIs like Slack and Google Workspace without managing OAuth tokens directly?

You can securely call third-party APIs by using a managed OAuth gateway that centralizes token handling. By sending requests with a single API key, the proxy injects valid user tokens to authenticate native endpoints for services like Slack and Google Workspace.

What is the best way to integrate multiple third-party services using a single API proxy?

The best way to integrate multiple services is through a passthrough API proxy that uses a single base URL with service prefixes. This approach lets you send Slack messages or query Notion data without handling individual service authentication flows.

How do I send a Slack message using a managed OAuth gateway?

To send a Slack message, POST a JSON payload to the gateway's Slack endpoint and include your API key in the Authorization header. The proxy validates the request and injects the necessary OAuth token to execute the native chat.postMessage call.

Do I need a specific API key to authenticate proxied requests to GitHub and Notion?

Yes, you need a valid MATON_API_KEY placed in the Authorization header to authenticate proxied requests. Users must explicitly authorize each third-party service, while the gateway manages the actual OAuth tokens for GitHub and Notion.

Can I target a specific user connection when making API calls through the proxy?

Yes, you can target a specific user connection by including the Maton-Connection header in your request. This allows you to select an exact authorized connection for services with multiple accounts, ensuring the API call uses the correct user context.

How does error handling and rate limiting work for native API calls made through an API gateway?

The API gateway uses passthrough error handling and rate limiting for native API calls. This means errors and rate limits from the third-party service are passed directly back to your application, preserving the original response codes and headers.