Skip to main content
Add a gate, then check the result on the server with gateCheck. This page is for backends that create proofs directly, or that automate Proofable as their own profile.

Choose a path

Create proofs for approved users

After a user approves your app once, your server can create proofs for them without a signature on every request.
This needs:
  • An active user approval for your appId and site origin. App link
  • X-Proofable-App from appId and a matching Origin on each request. In Node, appOrigin sets both.
If the approval is missing, send the user through Hosted Verify first. Creating proofs this way is different from publishing a listing, which bills hosted verification to your account.

Automate as your profile

An access key identifies your builder profile for automation. Pass it as apiKey on the server. It does not replace per-user approval for creating proofs for other people. Access keys

Billing

Published gates are the default billing source. Pass gateId to hosted checkout and gateCheck, and Proofable resolves the owner, usage, and payment from that gate. appId is public attribution for server flows and does not bill your account by itself. Pricing Next: API authentication
Last modified on October 5, 2026