2.5k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill api-gateway-1- _meta.json279 B
- LICENSE.txt1.0 KB
- SKILL.md27.5 KB
Overview
This skill provides a passthrough API gateway that connects to 100+ third-party services (Google Workspace, Microsoft 365, Slack, Notion, Airtable, HubSpot, and more) using managed OAuth. Use it to make native API calls to external services without handling individual OAuth flows or token refresh. The gateway injects the correct OAuth token for each authorized connection and routes requests to the provider's native endpoints.
How this skill works
You call the gateway URL prefixed with the target app name (e.g., /slack/... or /google-mail/...) and include your Maton API key in the Authorization header. The gateway looks up an authorized connection for that app, injects the provider OAuth token, and forwards the request to the native API endpoint. Connection listing, creation, and deletion are handled via a separate control endpoint so you can manage which accounts the gateway may use.
When to use it
- When you need to call native provider APIs without embedding individual OAuth logic in your app.
- When integrating multiple third-party services and you want a consistent proxy and auth model.
- When you need to switch between multiple authorized accounts for the same app.
- When scripting or automating provider API calls from servers, CI, or short-lived scripts.
- When you want centralized connection management and scoped access per user or team.
Best practices
- Store MATON_API_KEY in a secure environment variable and never commit it to source control.
- Always include Content-Type and other provider-specific headers required by the native API.
- Specify Maton-Connection header to select a specific authorized account when multiple exist.
- Use the control API to list and validate active connections before making gateway calls.
- Limit requested OAuth scopes when creating connections and revoke unused connections promptly.
Example use cases
- Send Slack messages using the native chat.postMessage endpoint without managing Slack tokens.
- Read and write Google Drive files via the Gmail/Drive native endpoints with a connected Google account.
- Query Airtable records or create new rows without storing Airtable API keys locally.
- Trigger HubSpot contact updates using the HubSpot native API through an authorized connection.
- Call GitHub REST endpoints across multiple organizations by selecting the desired connection ID.
FAQ
No. The MATON_API_KEY authenticates to the gateway service but does not itself authorize access to provider accounts. Each provider requires explicit OAuth authorization via Maton's connect flow.
How do I target a specific connection when multiple accounts exist?
Add the Maton-Connection header with the connection ID to your gateway request. If omitted, the gateway uses the default (oldest) active connection for that app.