Source type
Exact Online Source Configuration
Exact Online sources receive resource-change notifications for subscribed business data and protect the callback with a secret URL value.
Exact Online configuration
Create a Exact Online source, keep POST enabled, and provide the configured Webhook URL Secret values for provider signature. FastHook uses these settings to validate each Exact Online delivery before it enters the routing workflow.
Source TypeEXACT_ONLINE
Allowed methodsPOST
AuthenticationProvider signature
Credential fieldsWebhook URL Secret
{
"type": "EXACT_ONLINE",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "EXACT_ONLINE",
"webhook_signing_secret": "long-random-url-secret",
"query_parameter_name": "secret"
},
"allowed_http_methods": ["POST"]
}
}Exact Online request contract
Exact does not publish a general payload-signature contract. FastHook checks the callback URL secret and removes it from stored request metadata.
Exact Online headers
Preserve the source authentication values when sending Exact Online 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.
The Exact Online source does not require provider-specific signature headers. Use its configured source auth fields and inspect rejected requests if Exact Online does not match the saved credentials.
Exact Online setup
- Create an Exact Online source and choose a long random Webhook URL Secret.
- Append ?secret=YOUR_SECRET to the Source URL and use the complete value as the subscription callback URL.
- Create webhook subscriptions only for the Exact resource topics the workflow needs.
- Use the resource key and division to fetch the current record when the notification is only a change pointer.