Supabase Backend as a Service · レッスン

外部サービスとの統合

Supabaseバックエンドをサードパーティ製APIやサービスに接続し、アプリケーションの機能を拡張するためのパターンを学びます。

「外部サービスとの統合」はCoddyKit上の無料Supabase Backend as a Serviceレッスンです。これはレッスン1/3です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはSupabase Backend as a Service学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Supabase Backend as a Serviceコースには全3レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Why External Services?

Your app often needs to do more than just manage data in Supabase. Think about sending emails, processing payments, or integrating AI tools.

This is where integrating with external services comes in! It allows your Supabase backend to communicate with other APIs and platforms to extend your application's capabilities.

Common Integration Needs

Many common app features rely on external services:

Payment Gateways: Stripe, PayPal for transactions.
Email/SMS: SendGrid, Twilio for notifications.
AI/ML APIs: OpenAI, Google Cloud AI for advanced features.
Geo-location: Google Maps, Mapbox for mapping services.
Analytics: Mixpanel, Segment for user behavior tracking.

Supabase's Role: Edge Functions

While your client-side app can call external APIs directly, for secure and backend-driven integrations, Supabase Edge Functions are your best friend.

Edge Functions act as serverless backend logic, running close to your users. They can make HTTP requests to any external API without exposing sensitive information directly in your client-side code.

Making an API Call with Deno

Supabase Edge Functions are built on Deno, which uses the standard fetch API for making network requests, similar to browsers. This makes it straightforward to interact with external services.

The flow is: your client invokes an Edge Function, which then makes a request to the external API, processes the response, and sends it back to your client.

Code Demo: Fetching External Data

Here's a simple Edge Function that fetches a random 'todo' item from a public API (JSONPlaceholder). Notice how we use Deno.serve as the entry point for the function.

import { serve } from 'https://deno.land/std@0.177.0/http/server.ts'

Deno.serve(async (req) => {
  const { name } = await req.json()

  try {
    const response = await fetch('https://jsonplaceholder.typicode.com/todos/1')
    const data = await response.json()

    return new Response(JSON.stringify({
      message: `Hello ${name}! Here's a todo: ${data.title}`,
    }), {
      headers: { 'Content-Type': 'application/json' },
      status: 200,
    })
  } catch (error) {
    return new Response(JSON.stringify({
      error: error.message,
    }), {
      headers: { 'Content-Type': 'application/json' },
      status: 500,
    })
  }
})

Invoking the Edge Function

Once deployed, your client-side application can invoke this Edge Function using the Supabase client library. The function name here would be, for example, 'fetch-todo'.

The invoke method handles sending data to your function and receiving its response.

// Client-side JavaScript
async function getTodoFromEdgeFunction() {
  try {
    const { data, error } = await supabase.functions.invoke('fetch-todo', {
      body: { name: 'CoddyKit User' },
    })

    if (error) {
      console.error('Function error:', error)
    } else {
      console.log('Function response:', data)
    }
  } catch (err) {
    console.error('Invocation error:', err)
  }
}

// Call the function (e.g., on button click)
// getTodoFromEdgeFunction();

Securing API Keys with Supabase Secrets

Hardcoding API keys directly into your Edge Function code is a security risk. If your code is ever exposed, your keys are compromised.

Supabase provides Secrets to securely store environment variables for your Edge Functions. These are not part of your codebase and are injected at runtime.

Using Secrets in Edge Functions

First, you'd set a secret using the Supabase CLI: supabase secrets set MY_EXTERNAL_API_KEY=your_key_here. Then, in your Edge Function, you access it via Deno.env.get('MY_EXTERNAL_API_KEY').

This keeps your sensitive credentials safe and out of your version control.

import { serve } from 'https://deno.land/std@0.177.0/http/server.ts'

Deno.serve(async (req) => {
  // Access the secret environment variable
  const apiKey = Deno.env.get('MY_EXTERNAL_API_KEY') || 'NO_KEY_SET'

  // Example: Use the apiKey in a header for an external API call
  // const response = await fetch('https://api.example.com/data', {
  //   headers: { 'Authorization': `Bearer ${apiKey}` },
  // })

  return new Response(JSON.stringify({
    message: `API Key accessed: ${apiKey.substring(0, 5)}...`,
  }), {
    headers: { 'Content-Type': 'application/json' },
    status: 200,
  })
})

Handling Responses & Errors Robustly

When integrating external services, always prepare for success and failure. Parse the API's response correctly (often JSON) and handle potential errors.

Check HTTP Status: Not all 2xx responses are successes; some APIs use 4xx for business logic errors.
Try-Catch Blocks: Essential for network errors or issues parsing responses.
Meaningful Error Messages: Return clear error messages to the client without exposing internal API details.

Best Practices for Integrations

To ensure robust and scalable integrations:

Rate Limiting: Respect external API rate limits to avoid getting blocked.
Retries: Implement exponential backoff for transient network issues.
Timeouts: Set reasonable timeouts for external requests to prevent hanging.
Logging: Log requests and responses (especially errors) for debugging.
Idempotency: Design your functions to handle duplicate requests gracefully for operations like payments.

Quick Check on Integration

You're building an Edge Function to send an email using an external email API. You need to include your email service API key.

Recap: Integrating External Services

You've learned how to extend your Supabase application's capabilities by integrating with external APIs and services.

Edge Functions are ideal for secure backend-to-external-service communication.
Use fetch within Deno Edge Functions to make HTTP requests.
Always secure sensitive credentials like API keys using Supabase Secrets.
Implement robust error handling and follow best practices for reliable integrations.

This opens up a world of possibilities for building powerful and feature-rich applications!

よくある質問

「外部サービスとの統合」レッスンは無料ですか？

はい。「外部サービスとの統合」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Supabase Backend as a Serviceコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Supabase Backend as a Serviceコースには全3レッスンが含まれています。

「外部サービスとの統合」で何を学びますか？

Supabaseバックエンドをサードパーティ製APIやサービスに接続し、アプリケーションの機能を拡張するためのパターンを学びます。ブラウザで直接実行するハンズオンコードでSupabase Backend as a Serviceを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Supabase Backend as a Serviceを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSupabase Backend as a Serviceは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/3です。

「外部サービスとの統合」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このSupabase Backend as a Serviceレッスンでコードを書いて実行できますか？

はい。すべてのSupabase Backend as a Serviceレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Supabase Backend as a Serviceに戻る