api-gateway

Proxy third-party API requests through a managed OAuth gateway.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/adiytharpansa/openclawuserland --skill api-gateway-adiytharpansa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/adiytharpansa/openclawuserland/tree/main/skills/api-gateway
Command: npx skills add https://github.com/adiytharpansa/openclawuserland --skill api-gateway-adiytharpansa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide a unified, secure proxy for calling native third-party APIs without requiring each client to implement or manage OAuth flows, token storage, or per-service routing. The gateway injects user-authorized OAuth tokens and scopes for the target service so callers can invoke native endpoints directly while preserving connection-level access controls. Maton hosts the gateway and requires a MATON_API_KEY for authentication to the Maton control plane and proxy.

Core Features & Use Cases

  • Managed OAuth: Centralized OAuth connection handling so applications don't implement per-provider auth flows.
  • Direct Native API Calls: Call any proxied provider endpoint (Slack, Google Workspace, GitHub, Notion, Airtable, Stripe, etc.) using the provider's native path and parameters.
  • Connection Management: Create, list, inspect, and delete user connections via the Maton control API and optionally select a specific connection with the Maton-Connection header.
  • Use Case: Post a Slack message, read Gmail messages, query BigQuery, or call the Stripe API through the same authenticated gateway while scoped to the user's authorized accounts.

Quick Start

Use the api-gateway to call a native Slack API endpoint (chat.postMessage) through Maton and include your MATON_API_KEY in the Authorization header.

Frequently Asked Questions about api-gateway

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

FAQPage Schema
How do I call native third-party APIs without managing OAuth flows myself?

You can call native third-party APIs without managing OAuth by proxying requests through a managed OAuth gateway. The gateway injects user-authorized OAuth tokens automatically, letting you invoke endpoints directly while preserving connection-level access controls.

Can I use a single proxy gateway to access Google Workspace, Slack, and Notion APIs?

Yes, a single managed OAuth gateway supports accessing Google Workspace, Slack, Notion, and similar services. It routes requests to each provider's native endpoints while handling per-service authentication through injected user-authorized OAuth tokens.

How do I select a specific user connection when proxying API requests?

You select a specific user connection when proxying API requests by including the Maton-Connection header in your request. This explicitly directs the gateway to use the desired authenticated connection for the target service.

Do I need a specific API key to authenticate requests through the OAuth gateway?

Yes, you need a valid MATON_API_KEY to authenticate requests through the OAuth gateway. This key authorizes your access to the Maton control plane and proxy required for routing native API calls.

What's the best way to manage OAuth connections for multiple integrated services?

The best way to manage OAuth connections for multiple services is using a centralized control API. You can create, list, inspect, and delete user connections through the gateway's control plane, avoiding per-provider auth implementations.

Does the managed OAuth gateway support posting messages and reading files across different platforms?

Yes, the managed OAuth gateway supports posting messages and reading files across different platforms. You can call native endpoints for tasks like posting Slack messages or reading Gmail files through the same authenticated, scoped gateway.