Source type

OpenAI Source Configuration

OpenAI sources receive API event webhooks such as response, batch, and fine-tuning lifecycle notifications using Standard Webhooks signatures.

OPENAIPOST, PUT, PATCH, DELETEWebhook Signing SecretDeveloper tools
OpenAI webhooks documentationAll source types
OpenAI sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.OpenAIProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLOPENAIProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

OpenAI configuration

Create a OpenAI source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each OpenAI delivery before it enters the routing workflow.

Source Type

OPENAI

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Signing Secret

OpenAI source config
{
  "type": "OPENAI",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "OPENAI",
      "webhook_signing_secret": "whsec_..."
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

OpenAI request contract

FastHook verifies webhook-signature over webhook-id + '.' + webhook-timestamp + '.' + raw body using the configured Standard Webhooks secret.

POSTPUTPATCHDELETE

OpenAI headers

Preserve webhook-id, webhook-timestamp, webhook-signature when sending OpenAI test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

webhook-id

Message id used in the Standard Webhooks signed payload.

webhook-timestamp

Unix timestamp used for replay protection and signature input.

webhook-signature

One or more Standard Webhooks signatures.

OpenAI setup

  1. Create an OpenAI webhook endpoint with the generated FastHook Source URL.
  2. Copy the OpenAI webhook signing secret into FastHook.
  3. Route by event type when response, batch, or fine-tuning events should reach different destinations.

OpenAI routing hints

  • OpenAI lifecycle callbacks can branch by payload type so response, batch, and fine-tuning notifications reach different operational workflows.
  • Use webhook-id for delivery-level deduplication and keep the API object identifier for later status lookups or support investigation.

Continue with OpenAI