Troubleshooting

If you created a webhook subscription but are not receiving notifications, consider the following:

• Verify that the digital signature key you created includes the correct organization ID. You can verify the organization ID by locating it in the response for creating the digital signature key. If the key is configured with the wrong organization ID, send a request for a new digital signature key using the correct organization ID.
• Verify that your server and the endpoint URL for the webhook are working and are configured correctly.
• Verify that the notification scope of the subscription is configured to send notifications to the correct organization. You can retrieve the webhook details to verify that the organization is listed in the organizationId response field. If the organization is not in the notification scope, you must update the webhook subscription.
• Verify that the subscription status is ACTIVE. You can do this by retrieving the webhook details. If the webhook is not set to the ACTIVE status:
  • Verify that your subscription is configured with a health check URL. If it is not, update the subscription with a correct URL. You must also verify that the URL is working and is configured to accept GET and POST requests. For more information, see Health Check URL.
  • Verify that the webhook URL and health check URL contain hypertext transfer protocol secure (HTTPS). For example:

"webhookUrl": "https://MyWebhookServer.com:443/simulateClient""healthCheckUrl": "https://MyWebhookServer.com:443/simulateClientHealthCheck"

Message-Level Encryption Troubleshooting

If you receive the Key invalid or validity too long error, try generating a certificate with shorter validity:

# 90-day validityopenssl req -x509 -newkey rsa:2048 -keyout request_private.pem -out request_certificate.pem -days 90 -nodes -subj"/CN=RequestKey/O=YourOrg/C=US" && cat request_certificate.pem | grep -v "BEGIN CERTIFICATE" | grep -v "END CERTIFICATE" |tr -d '\n' && echo