Skip to main content
Use the sections below to diagnose and fix the most common issues you may encounter when integrating with KeyPort.
Your request is being rejected because the product API key is missing, malformed, or no longer valid.Check the following:
  • Confirm you are sending the full product API key, not a truncated or partial value
  • Confirm the Authorization header is formatted correctly: Authorization: Bearer <your-key>
  • If you recently rotated the key, the old key is invalidated immediately — make sure you are using the new one
The license key you are validating cannot be found under the product associated with your API key.Check the following:
  • Confirm the license belongs to the product behind the API key you are using
  • Confirm you are not mixing product environments or querying against stale test data
The request is being blocked or limited because of the IP address it came from.Check the following:
  • Review the IP settings configured on your product
  • Check the per-license IP history in the dashboard to see what IPs have been recorded
  • Check whether the org or platform has a blacklist entry that applies to this request
  • If you expected a new IP to be auto-registered, compare that expectation against the live IP rules applied at validate time — auto-registration behavior depends on your product configuration
The validation response is not including your custom payload even though you have configured one.Check the following:
  • Confirm the custom response module is enabled on the product
  • Confirm the template or any merged per-license override is not empty
Your endpoint is not receiving webhook deliveries.Check the following:
  • Confirm the endpoint is enabled in the dashboard
  • Confirm the endpoint is subscribed to the specific event you are expecting
  • Confirm your organization is on a plan that supports webhooks
  • Open the delivery history in the dashboard to inspect the delivery state and any retry attempts