aid: diligent accessModel: pricing: unknown onboarding: self-serve trial: false try_now: false public: false label: Self-serve signup confidence: medium source: - authentication generated: '2026-07-22' method: derived image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/diligent.png name: Diligent description: >- Diligent (Diligent AI, godiligent.ai) builds autonomous AI agents for financial-crime compliance, automating the reasoning-heavy KYC/AML workflows that banks and fintechs run at scale. Its API exposes Customer Due Diligence (CDD) and business/merchant verification, name screening against sanctions and PEP providers with AI-powered alert remediation, ongoing monitoring with alerting, company identification and registry document retrieval, a blocked-company list, and an experimental instant website screening endpoint. The platform is API-first (X-API-KEY auth, production and sandbox environments, idempotency, and signed webhooks) and is used by fintechs and banks including Scalapay, Flywire, Allica Bank, Tamara, Teya, Vivid and Alma. Diligent is SOC 2 Type II certified, ISO 27001 certified, and GDPR compliant. It is backed by Speedinvest, Y Combinator and Shapers, and operates out of London and Berlin. url: https://raw.githubusercontent.com/api-evangelist/diligent/refs/heads/main/apis.yml x-type: company x-source: vc-portfolio x-backed-by: - speedinvest - ycombinator x-tier: enriched x-tier-reason: public-api-found specificationVersion: '0.20' created: '2026-07-17' modified: '2026-07-18' tags: - Company - Compliance - RegTech - KYC - AML - Financial Crime - Due Diligence - Screening - Sanctions - Monitoring - Artificial Intelligence - Fintech - Webhooks apis: - aid: diligent:diligent-cdd-api name: Diligent CDD API description: Customer Due Diligence humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - CDD properties: - type: OpenAPI url: openapi/diligent-cdd-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api - aid: diligent:diligent-company-api name: Diligent Company API description: Company Information humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - Company properties: - type: OpenAPI url: openapi/diligent-company-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api - aid: diligent:diligent-instant-screening-experimental-api name: Diligent Instant Screening (experimental) API description: Instant Website Screening API humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - Instant Screening (experimental) properties: - type: OpenAPI url: openapi/diligent-instant-screening-experimental-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api - aid: diligent:diligent-monitorings-api name: Diligent Monitorings API description: Website monitoring and alerts for changes and risks humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - Monitorings properties: - type: OpenAPI url: openapi/diligent-monitorings-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api - aid: diligent:diligent-name-screening-api name: Diligent Name Screening API description: Name screening remediation humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - Name Screening properties: - type: OpenAPI url: openapi/diligent-name-screening-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api - aid: diligent:diligent-webhooks-api name: Diligent Webhooks API description: >- ## How to Secure Webhook Deliveries To ensure that webhook payloads are securely transmitted and verified. This guide explains how to configure and validate webhook deliveries using a shared secret. ### How It Works When setting up a webhook, a secret is configured on both the sender (our system) and the receiver (your endpoint). Each webhook payload is signed using this secret, allowing the receiver to verify its authenticity. #### Step 1: Configuring Your Webhook Secret 1. When creating a webhook in our system, specify a unique secret key. This secret should be a strong, randomly generated string. 2. Store this secret securely on your server; it should never be exposed publicly. #### Step 2: Receiving Webhook Payloads When your server receives a webhook event, the request will include an `X-Signature` header containing a HMAC signature of the payload. Example header: ``` X-Signature: sha256=abcdef1234567890... ``` #### Step 3: Validating the Webhook Signature To verify the webhook payload: 1. Retrieve the `X-Signature` value from the request headers. 2. Compute the HMAC SHA-256 signature of the request payload using your webhook secret. 3. Compare the computed signature with the one in the `X-Signature` header. 4. If they match, the webhook is valid. #### (Python) ```python import hashlib import hmac import json def verify_webhook_signature(secret, payload, signature): computed_signature = hmac.new(secret.encode(), payload.encode(), hashlib.sha256).hexdigest() expected_signature = f"sha256={computed_signature}" return hmac.compare_digest(expected_signature, signature) # Example usage: secret = "your_webhook_secret" payload = json.dumps({"event": "example"}) received_signature = "sha256=abcdef1234567890..." if verify_webhook_signature(secret, payload, received_signature): print("Valid webhook received!") else: print("Invalid webhook signature!") ``` #### (JavaScript) ```javascript const crypto = require('crypto'); function verifyWebhookSignature (secret, payload, signature) { const computedSignature = `sha256=${crypto.createHmac('sha256', secret) .update(payload) .digest('hex')}`; return crypto.timingSafeEqual(Buffer.from(computedSignature), Buffer.from(signature)); } // Example usage: const secret = "your_webhook_secret"; const payload = JSON.stringify({ event: "example" }); const receivedSignature = "sha256=abcdef1234567890..."; if (verifyWebhookSignature(secret, payload, receivedSignature)) { console.log("Valid webhook received!"); } else { console.log("Invalid webhook signature!"); } ``` #### Security Considerations - Always use HTTPS to prevent interception of webhook payloads. - Reject webhook requests that fail signature validation. - Rotate secrets periodically to enhance security. By following this guide, you ensure that webhook deliveries are secure and trusted. humanURL: https://docs.godiligent.ai/guides/introduction baseURL: https://api.godiligent.ai tags: - Webhooks properties: - type: OpenAPI url: openapi/diligent-webhooks-api-openapi.yml - type: Documentation url: https://docs.godiligent.ai/guides/introduction - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Documentation url: https://docs.godiligent.ai/guides/name-screening/remediation-api common: - type: TrustCenter url: security/diligent-trust-center.yml - type: DomainSecurity url: security/diligent-domain-security.yml - type: Authentication url: authentication/diligent-authentication.yml - type: Website url: https://www.godiligent.ai - type: DeveloperPortal url: https://docs.godiligent.ai - type: Documentation url: https://docs.godiligent.ai - type: APIReference url: https://docs.godiligent.ai/guides/introduction - type: GettingStarted url: https://docs.godiligent.ai/guides/introduction - type: Login url: https://app.godiligent.ai/ - type: Support url: https://docs.godiligent.ai/support - type: Blog url: https://www.godiligent.ai/news - type: TermsOfService url: https://www.godiligent.ai/terms-and-conditions - type: PrivacyPolicy url: https://www.godiligent.ai/privacy-policy - type: StatusPage url: https://status.godiligent.ai/ - type: Compliance url: https://www.godiligent.ai/security - type: LinkedIn url: https://www.linkedin.com/company/godiligentai - type: Twitter url: https://x.com/goDiligent - type: Postman url: https://raw.githubusercontent.com/paylaneio/api/refs/heads/master/postman_collection.json - type: LLMsTxt url: llms/diligent-llms.txt - type: MCPServer url: mcp/diligent-mcp.yml name: Diligent MCP (candidate) description: Candidate MCP tool list derived from the Diligent OpenAPI operations; no official hosted server published. - type: Conformance url: conformance/diligent-conformance.yml - type: ErrorCatalog url: errors/diligent-problem-types.yml - type: Lifecycle url: lifecycle/diligent-lifecycle.yml - type: Conventions url: conventions/diligent-conventions.yml - type: Idempotency url: conventions/diligent-conventions.yml - type: DataModel url: data-model/diligent-data-model.yml - type: Sandbox url: sandbox/diligent-sandbox.yml - type: Webhooks url: asyncapi/diligent-webhooks.yml - type: AgentSkill url: skills/_index.yml maintainers: - FN: Kin Lane email: kin@apievangelist.com - FN: APIs.json email: info@apis.io x-enrichment: date: '2026-07-19' status: backfilled pass: local-v1 note: backfilled from .gitignore signal + verified work evidence