api-integration
/api-integration
Prowadzi dewelopera przez konfigurację integracji z API Meta od zera: dobór API, przewodniki, uwierzytelnianie, uprawnienia i przykłady kodu dla WhatsApp, Instagram, Messenger, Pages czy Ads.
- Autor
- facebook ↗
- Repozytorium
- agentic-tools ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi dewelopera przez konfigurację integracji z API Meta od zera: dobór API, przewodniki, uwierzytelnianie, uprawnienia i przykłady kodu dla WhatsApp, Instagram, Messenger, Pages czy Ads.
Oryginalny opis (EN)
Guide a developer through setting up a Meta API integration from scratch — discovers the right APIs, fetches setup guides, authentication requirements, permissions, and code examples. Use when the user wants to build with a specific Meta product (WhatsApp, Instagram, Messenger, Pages, Ads, etc.).
Jak działa
- Prerequisites — MCP connection (read first)
- Workflow
- Tips
Podgląd SKILL.md
---
name: api-integration
description: "Guide a developer through setting up a Meta API integration from scratch — discovers the right APIs, fetches setup guides, authentication requirements, permissions, and code examples. Use when the user wants to build with a specific Meta product (WhatsApp, Instagram, Messenger, Pages, Ads, etc.)."
allowed-tools: mcp__devtools__devtools_discovery, mcp__devtools__devtools_app, mcp__devtools__devtools_app_review, mcp__devtools__devtools_app_list, mcp__devtools__devtools_skill_invocation
license: MIT
metadata:
mcp:
devtools:
type: streamable-http
url: "https://mcp.facebook.com/devtools"
---
# API Integration
Help a developer go from "I want to integrate with X" to having everything they need to start writing code.
## Prerequisites — MCP connection (read first)
This skill needs the Meta Social Technologies MCP server `devtools` (`https://mcp.facebook.com/devtools`, streamable-http). Plugin installs bundle it; skills-only installs such as `npx skills add` do not ([setup](https://github.com/facebook/agentic-tools#install-via-vercel-skillssh)).
**If the `mcp__devtools__*` tools are not available, STOP.** Do not invent tool output, including the step 1 tracking call. Ask the user to add the server and complete its OAuth flow (never ask for an access token), then continue.
## Workflow
1. **Start tracking.** Before any other work, call `devtools_skill_invocation` with action `start` and `skill_name` `api-integration`. Pass `skill_name` `api-integration` on every `devtools_*` tool call in the following steps.
2. **Identify the integration.** Ask the user what they want to build if not clear. Common integrations:
- WhatsApp Business API (send/receive messages, templates, media)
- Instagram Graph API (publish content, read insights, manage comments)
- Messenger Platform (chatbots, send API, webhooks)
- Pages API (post content, read insights, manage pages)
- Marketing API (create campaigns, manage ads, read analytics)
- Login with Facebook / Login with Instagram
- Facebook Login for Business
3. **Research the integration.** Run multiple searches to build a complete picture. Do NOT stop at one search — layer queries to cover all aspects:
**Search 1 — Overview and getting started:**
- `devtools_discovery` → `search_docs` with the product name + "getting started" or "overview"
- e.g., "WhatsApp Business API getting started"
**Search 2 — Authentication and access tokens:**
- `devtools_discovery` → `search_docs` for authentication requirements
- e.g., "WhatsApp Business API access token authentication"
**Search 3 — Required permissions and app review:**
- `devtools_discovery` → `search_docs` for permissions
- e.g., "WhatsApp Business API permissions"
- Also check the app if an app_id is provided: `devtools_app_review` → `requirements` and `privileges`
**Search 4 — Core API endpoints:**
- `devtools_discovery` → `search_docs` for the specific operations the user needs
- e.g., "WhatsApp send message API" or "Instagram publish media API"
**Search 5 — Webhooks (if applicable):**
- `devtools_discovery` → `search_docs` for webhook setup
- e.g., "WhatsApp webhooks setup"
**Search 6 — Rate limits and quotas:**
- `devtools_discovery` → `search_docs` for product-specific rate limits and throughput tiers
- e.g., "WhatsApp Business API rate limits messaging tiers" or "Instagram API rate limits"
**Search 7 — Code examples and SDKs:**
- `devtools_discovery` → `search_docs` for SDK, client library, or code samples
- Try product-specific queries first: "WhatsApp Business Platform Node.js" or "Instagram Graph API Python"
- If no SDK results, search for "Graph API client library" or the product's quickstart guide
- Fall back to constructing examples from the endpoint documentation in Search 4
Run searches 1-5 in parallel for speed. Run 6-7 after if needed. Use `max_results` of 10 and pagination via `offset` to get comprehensive results. Refine queries if initial results are too broad or miss key topics.
4. **Check app readiness** (if the user has an app):
- If they referred to the app by **name** (or aren't sure of the ID), resolve it to an `app_id` first via `devtools_app_list` (action `list`); if ambiguous, show the candidates (name, ID, viewer role) and ask them to pick
- `devtools_app` → `basic_settings` to confirm app type and status
- `devtools_app_review` → `privileges` to see what's already approved
- `devtools_app_review` → `requirements` to see what's needed
5. **Synthesize an integration guide.** Extract the key information from search results — do NOT dump raw results. Organize findings into an actionable document:
### Guide Format
**Overview**
- What the API does and what the user can build with it
- Link to the official product documentation
**Prerequisites**
- Meta Developer account
- App type required (Business, Consumer, etc.)
- Any product-specific prerequisites (e.g., WhatsApp Business Account, Facebook Page)
**Authentication**
- Token type needed (User, Page, System User, etc.)
- How to generate tokens
- Token permissions/scopes required
- Token expiration and refresh flow
**Required Permissions**
- List each permission needed and what it grants
- Which permissions need App Review vs. are auto-approved
- If app_id provided: which are already granted vs. still needed
**Setup Steps**
- Step-by-step from zero to first API call
- Include webhook setup if the integration requires it
**Key API Endpoints**
- Each endpoint with: method, URL pattern, key parameters, example response
- Focused on what the user asked for, not an exhaustive list
**Code Example**
- A working starter example in the user's preferred language
- Include authentication, a basic API call, and error handling
- Use the official SDK if one exists, raw HTTP (curl/fetch) if not
- Include webhook handler code if the integration is webhook-based
**Rate Limits and Quotas**
- Product-specific rate limits and throughput tiers (e.g., WhatsApp messaging tiers: 1K/10K/100K/unlimited)
- Per-endpoint rate limits if applicable
- Suggest `/api-health` for ongoing monitoring
**Common Pitfalls**
- Product-specific gotchas the docs call out
- Permission mistakes, token type confusion, webhook verification issues
6. **Offer next steps:**
- `/app-review-prep` if permissions need App Review
- `/webhook-setup` if the integration uses webhooks
- `/api-health` to monitor usage once live
7. **End tracking.** After completing all preceding steps, call `devtools_skill_invocation` with action `end` and `skill_name` `api-integration`.
## Tips
- Always search multiple times with different queries. A single search rarely covers authentication + permissions + endpoints + examples.
- Prefer the user's stated language/framework for code examples. Default to Node.js/JavaScript if not specified.
- If the user has an app_id, cross-reference their current permissions against what the integration requires — this saves them time.
- Some integrations (WhatsApp, Instagram) require a Business-type app. Call this out early if the user's app is the wrong type.
- Webhook-based integrations (Messenger, WhatsApp) won't work without a callback URL. Suggest `/webhook-setup` proactively.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · facebook/agentic-tools | 100 | MIT |
| mhmdelgazzar/agentex | 100 | MIT |
| AutumnsGrove/Lattice | 100 | AGPL-3.0 |
| srstomp/pokayokay | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| seb1n/awesome-ai-agent-skills | 100 | MIT |
| shurikentrade/shuriken-skills | 100 | MIT |
| LambdaTest/agent-skills | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 93f5fc888a72 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100meta-click-to-message-ads
Planuje i ocenia reklamy Meta otwierające czat w WhatsAppie, Messengerze lub Instagramie, oceniając koszt kwalifikowanej rozmowy i sprzedaży. - 100meta-ad-scraper
Pobiera reklamy konkurencji z biblioteki reklam Meta (Facebook, Instagram, Messenger, Threads, WhatsApp) według firmy, strony lub słowa kluczowego, zwracając kreacje, szacunki wydatków i zasięgu. - 100whatsapp-meta-api
Podaje endpointy i wzorce Cloud API WhatsApp oraz sprawdza integracje pod kątem bezpieczeństwa i zgodności z Meta. - 100chatmaxima-api
Pisze kod integracji z REST API ChatMaxima v2: wysyłanie wiadomości, szablonów WhatsApp, webhooki i synchronizacja kontaktów. - 100whatsapp-bot-builder
Buduje boty WhatsApp na WhatsApp Business API (Cloud API): szablony wiadomości, obsługa wiadomości przychodzących, interaktywne listy i przyciski oraz przetwarzanie mediów. - 100api-documentation-writer
Prowadzi pisanie dokumentacji API: specyfikacje OpenAPI, referencje endpointów, przewodniki uwierzytelniania i przykłady kodu, także przy tworzeniu portali dla deweloperów.