Skip to main content
フレッシュクレジットFreshCredit®INC
製品ソリューションプラン会社概要お問い合わせ
アプリを起動
文書化/認証 /

認証

OAuth 2.0 フロー、API キー管理、Webhook 署名、JWT 処理、運用環境のセキュリティのベスト プラクティス。

認証方法 /

API Key Authentication

Use API keys for server-to-server authentication. Include your key in the Authorization header with Bearer prefix.

// Request header
Authorization: Bearer fc_live_xxxxxxxxxxxxxxxx

// Generate HMAC signature
const crypto = require('crypto');
const signature = crypto
  .createHmac('sha256', API_SECRET)
  .update(timestamp + method + path + body)
  .digest('hex');

// Include signature header
X-FreshCredit-Signature: {signature}
X-FreshCredit-Timestamp: {unix_timestamp}

OAuth 2.0

For user-delegated access, use OAuth 2.0 authorization code flow. Users authorize your application to access their FreshCredit data.

// Step 1: Redirect user to authorization endpoint
https://app.freshcredit.com/oauth/authorize?
  response_type=code&
  client_id=your_client_id&
  redirect_uri=https://your-app.com/callback&
  scope=blockid:read blockscore:read&
  state=random_state_string

// Step 2: Exchange code for access token
POST https://api.freshcredit.com/v1/oauth/token
{
  "grant_type": "authorization_code",
  "code": "auth_code_from_callback",
  "client_id": "your_client_id",
  "client_secret": "your_client_secret",
  "redirect_uri": "https://your-app.com/callback"
}
OAuthスコープ /
blockid:readRead identity verification status and credentials
blockid:writeInitiate identity verification workflows
blockscore:readRead credit scores and model outputs
blockscore:writeCreate and update custom credit models
blockiq:readRead offer matching data and marketplace info
blockiq:writeCreate and manage offers
wallet:readRead user's self-custody wallet data
webhooksConfigure and manage webhook endpoints
Webhookセキュリティ /

Webhook Signature Verification

All webhooks include a signature header. Verify signatures to ensure requests originate from FreshCredit.

const crypto = require('crypto');

function verifyWebhookSignature(payload, signature, secret) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex');
  
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

// In your webhook handler
app.post('/webhooks/freshcredit', (req, res) => {
  const signature = req.headers['x-freshcredit-signature'];
  const payload = JSON.stringify(req.body);
  
  if (!verifyWebhookSignature(payload, signature, WEBHOOK_SECRET)) {
    return res.status(401).send('Invalid signature');
  }
  
  // Process webhook
  handleWebhook(req.body);
  res.status(200).send('OK');
});
セキュリティのベストプラクティス /

Store Credentials Securely

Never expose API secrets in client-side code. Use environment variables and secret management systems like AWS Secrets Manager or HashiCorp Vault.

Rotate Keys Regularly

Rotate API keys every 90 days. FreshCredit supports multiple active keys for zero-downtime rotation.

Use HTTPS Only

All API requests must use HTTPS. Unencrypted HTTP requests are rejected.

次のステップ

BlockID™を見るSDKをダウンロード
フレッシュクレジットFreshCredit®INC

現代の世界のための信用およびIDインフラ。

INC freshcredit.comLAB freshcredit.xyzORG freshcredit.orgDAO freshcredit.aiAPP freshcredit.app

Stay Updated

Get fraud prevention insights and product updates. Unsubscribe anytime.

製品
BlockID™ ワークフローBlockScore™ モデルBlockIQ™ オファーThe FreshCredit App™
会社概要
概要プランドキュメントお問い合わせ
エコシステム
FreshCredit® ラボFreshCredit® 組織FreshCredit® DAOThe FreshCredit App™
計算機
プロバイダーコスト計算機消費者コスト計算機インフラストラクチャコスト計算機経済的影響計算機
法務
プライバシーポリシー利用規約AML/KYCポリシーCookieポリシー
XInstagramRedditGitHubYouTubeFacebook

© 2026 FreshCredit®. All rights reserved.

FreshCredit® Incは銀行、信用組合、信用修復会社、または信用報告機関ではありません。