> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fyatu.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Get Webhook Configuration
> Retrieve your current webhook configuration — endpoint URL, enabled events, and signing secret status. GET /webhooks.
# Get Webhook Configuration
Returns the current webhook configuration for your app, including the webhook URL and whether a webhook secret is configured.
## Request
```bash theme={null}
curl -X GET https://api.fyatu.com/api/v3/webhooks \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
```
## Response
Whether the request was successful
The configured webhook URL, or null if not set
Whether a webhook secret is configured
Whether webhooks are fully configured (URL is set)
```json 200 theme={null}
{
"success": true,
"status": 200,
"message": "Webhook configuration retrieved",
"data": {
"webhookUrl": "https://example.com/webhooks/fyatu",
"hasWebhookSecret": true,
"isConfigured": true
},
"meta": {
"requestId": "req_abc123xyz789",
"timestamp": "2026-01-15T10:30:00+00:00"
}
}
```
```json 200 (Not Configured) theme={null}
{
"success": true,
"status": 200,
"message": "Webhook configuration retrieved",
"data": {
"webhookUrl": null,
"hasWebhookSecret": false,
"isConfigured": false
},
"meta": {
"requestId": "req_def456uvw123",
"timestamp": "2026-01-15T10:30:00+00:00"
}
}
```
## Use Cases
* Check if webhooks are configured before testing
* Verify webhook URL in your integration dashboard
* Debug webhook delivery issues
## OpenAPI
````yaml v3/openapi.json GET /webhooks
openapi: 3.1.0
info:
title: FYATU API v3
description: >-
FYATU API v3 with JWT authentication for Collections, Payouts, and Card
Issuing.
version: 3.0.0
contact:
name: FYATU Support
url: https://fyatu.com
email: support@fyatu.com
servers:
- url: https://api.fyatu.com/api/v3
description: Production
security: []
tags:
- name: Authentication
description: JWT token management endpoints
- name: Account
description: Business account, wallet, and address management
- name: Collections
description: Accept payments from customers via checkout sessions
- name: Refunds
description: Issue refunds for completed collections
- name: Payouts
description: Send money to Fyatu account holders
- name: Cardholders
description: Cardholder management for card issuing programs
- name: Cards
description: Issue, fund, freeze, and manage virtual cards
- name: Webhooks
description: Webhook configuration and management
paths:
/webhooks:
get:
tags:
- Webhooks
summary: Get Webhook Configuration
description: >-
Retrieve the current webhook configuration for your app, including the
webhook URL, secret, and enabled events.
operationId: getWebhook
responses:
'200':
description: Webhook configuration retrieved successfully
content:
application/json:
schema:
$ref: '#/components/schemas/WebhookConfigResponse'
example:
success: true
status: 200
message: Webhook configuration retrieved
data:
webhookUrl: https://example.com/webhooks/fyatu
hasWebhookSecret: true
isConfigured: true
appType: ISSUING
createdAt: '2026-01-15T10:30:00+00:00'
updatedAt: '2026-01-15T10:30:00+00:00'
meta:
requestId: req_abc123xyz789
timestamp: '2026-01-15T10:30:00+00:00'
'401':
$ref: '#/components/responses/Unauthorized'
security:
- BearerAuth: []
components:
schemas:
WebhookConfigResponse:
type: object
properties:
success:
type: boolean
example: true
status:
type: integer
example: 200
message:
type: string
data:
$ref: '#/components/schemas/WebhookConfig'
meta:
$ref: '#/components/schemas/Meta'
WebhookConfig:
type: object
properties:
webhookUrl:
type: string
format: uri
description: The HTTPS URL where webhook events will be sent
hasWebhookSecret:
type: boolean
description: Whether a webhook secret is configured
isConfigured:
type: boolean
description: Whether a webhook URL is configured
appType:
type: string
enum:
- ISSUING
- COLLECTION
description: App type determines available events
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
Meta:
type: object
properties:
requestId:
type: string
description: Unique request ID for tracking
example: req_abc123def456
timestamp:
type: string
format: date-time
description: ISO 8601 timestamp of the response
ErrorResponse:
type: object
properties:
success:
type: boolean
example: false
status:
type: integer
example: 401
message:
type: string
example: Invalid credentials
error:
$ref: '#/components/schemas/Error'
meta:
$ref: '#/components/schemas/Meta'
Error:
type: object
properties:
code:
type: string
description: Error code for programmatic handling
example: AUTH_INVALID_CREDENTIALS
details:
type: array
items:
$ref: '#/components/schemas/ValidationError'
description: Validation error details (for VALIDATION_ERROR)
ValidationError:
type: object
properties:
field:
type: string
description: Field that failed validation
example: appId
message:
type: string
description: Validation error message
example: AppId is required
responses:
Unauthorized:
description: Authentication required or token invalid
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
success: false
status: 401
message: Unable to identify business
error:
code: AUTH_TOKEN_INVALID
meta:
requestId: req_abc123
timestamp: '2026-01-05T10:30:00+00:00'
securitySchemes:
BearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: JWT access token obtained from /auth/token
````