Developer API

Not available yet. We're preparing an API so your own software can send documents to ClaimGate. You can't sign up for it yourself yet. Tell us you're interested and which documents and checks you need.

How it will work

• Your application identifies itself with a client certificate. Website sign-in with Microsoft is separate and isn't used for the API.
• Your business gets access to its own rules. A certificate never gives access to another company's documents or rules.
• When the API is ready, we'll send a set-up guide with the address, version, certificate steps, request format and examples.
• Keep your private key in your own systems. Never email passwords, private keys, tokens or confidential documents.

Handling results

• A gap in a document is a result. A failed request is not. Treat an unavailable service, expired access or unreadable file as "not checked".
• Send unresolved results to a person. Don't treat them as approved.
• If a request is interrupted, don't start a new attempt for every retry. The check may already have run.

Before you build

• Agree with us the document format, the fields you need, your rules version and your limits.
• Test with made-up or approved test documents first.
• The API helps your team check documents. Your organisation still makes the final decision.