APIFuseAPIFuse
  • Providers
  • Changelog
  • Playground
  • Dashboard
  • APIFuse Docs
    • Getting started
    • Authentication and Connections
    • Playground
    • OpenAPI and schemas
    • MCP endpoint
    • Developer MCP guide
    • Schema bundles
    • Next.js App Router integration
    • FastAPI integration
    • Error Handling
    • FAQ
    • Resources
APIFuseAPIFuse

Authentication and Connections

Understand API-key-only operations and operations that also require an APIFuse Connection.

Authentication and Connections

Every APIFuse gateway call uses your APIFuse API key. Some operations can run with only that key. Others also need a Connection because the provider requires account-specific authorization.

Authentication modes

ModeWhat you provideCommon use
noneAPIFuse API keyPublic data or search operations
credentialsAPIFuse API key and Connection IDOperations that use a connected provider account

API-key-only operation

curl -X POST https://api.apifuse.com/v1/kakaomap/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"Seoul Station"}'

Operation with a Connection

When an operation requires a Connection, include its af_con_<22-char> identifier:

curl -X POST https://api.apifuse.com/v1/catchtable/my-status \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-ApiFuse-Connection-Id: af_con_1234567890123456789012" \
  -H "Content-Type: application/json" \
  -d '{}'

Create and manage Connections in the APIFuse platform before calling protected operations.

On this page

Authentication and ConnectionsAuthentication modesAPI-key-only operationOperation with a Connection
APIFuseAPIFuse
  • Providers
  • Changelog
  • Playground
  • Dashboard
  • APIFuse Docs
    • Getting started
    • Authentication and Connections
    • Playground
    • OpenAPI and schemas
    • MCP endpoint
    • Developer MCP guide
    • Schema bundles
    • Next.js App Router integration
    • FastAPI integration
    • Error Handling
    • FAQ
    • Resources
Providers
  • API Reference
    • Amazon Japan
    • Baemin Provider
    • Buyee
    • CatchTable Restaurant Search and Reservations
    • Charan Commerce
    • Daangn public listings
    • Daiso Product and Store Data
    • Danawa price comparison
    • Demaecan
    • Ekitan
    • Goodchoice Domestic Lodging
    • Google Flights
    • Han River Water Level
    • Hot Pepper Gourmet provider
    • Hyundai Card
    • Jalan
    • Japan National Diet Minutes
    • Japan Disaster Alerts
    • Japan EDINET Filings
    • Japan e-Gov Law
    • Japan e-Stat
    • Japan GSI Geocoding
    • Japan e-Gov Open Data
    • Japan Post ZIP
    • Japan Public Holidays
    • JMA Weather
    • KakaoMap Place Search and Directions
    • Kakao T Taxi Dispatch
    • Korea Address Search
    • AirKorea Real-time Air Pollution
    • Korea Apartment Rent Prices
    • Korea Apartment Sale Prices
    • Korea Bid Notices
    • Korea Building Register
    • Korea Business Verify
    • Korea Camping
    • Korea DART Corporate Finance
    • DART Corporate Info
    • Korea Culture Events
    • Korea Disaster Alert
    • Korea Emergency Hospital
    • Korea ETF
    • Korea EV Charger
    • Korea Fuel Price
    • Korea Holiday
    • Korea Hospital Info
    • Korea Land Price
    • Korea MFDS Drug Safety
    • Korea MFDS Food Safety
    • Korea Household Waste Disposal Guide
    • Korea National Law Search and Lookup
    • Korea NEIS School Meals
    • Carrier List and Delivery Tracking
    • Korea Pharmacy
    • Korea Population
    • Korea Stock Index
    • Korea Stock Price
    • Korea Train Schedule
    • Korea Weather Forecast Data
    • Korea Weather Forecast
    • Korea Welfare Service
    • K-Startup
    • LH Housing Notices
    • Market Kurly product data
    • Mercari
    • Modu Parking
    • Naver Blog Search
    • Naver Flight API
    • Naver Map
    • Naver News Search
    • NOL Stays
    • Ohouse Store and Contents
    • Rakuten Ichiba
    • Rakuten Travel
    • SEC EDGAR Filings
    • Seoul Bike
    • Seoul Live Crowd Density
    • Seoul Subway Arrivals
    • Shinhan Bank
    • Shinhan Card
    • Skiplagged
    • SUUMO
    • Swing Taxi
    • Tabelog
    • TableCheck
    • Weverse Provider
    • Yahoo! Shopping (Japan)
    • Yogiyo
    • ZOZOTOWN
APIFuseAPIFuse

Authentication and Connections

Understand API-key-only operations and operations that also require an APIFuse Connection.

Authentication and Connections

Every APIFuse gateway call uses your APIFuse API key. Some operations can run with only that key. Others also need a Connection because the provider requires account-specific authorization.

Authentication modes

ModeWhat you provideCommon use
noneAPIFuse API keyPublic data or search operations
credentialsAPIFuse API key and Connection IDOperations that use a connected provider account

API-key-only operation

curl -X POST https://api.apifuse.com/v1/kakaomap/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"Seoul Station"}'

Operation with a Connection

When an operation requires a Connection, include its af_con_<22-char> identifier:

curl -X POST https://api.apifuse.com/v1/catchtable/my-status \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-ApiFuse-Connection-Id: af_con_1234567890123456789012" \
  -H "Content-Type: application/json" \
  -d '{}'

Create and manage Connections in the APIFuse platform before calling protected operations.

On this page

Authentication and ConnectionsAuthentication modesAPI-key-only operationOperation with a Connection