Getting Started
The SourceVerify API delivers tamper-proof provenance and authenticity proofs for digital artifacts — text, image, video, audio, or document.
This guide takes you from zero to your first verification in under five minutes.
1. Get credentials
Sign in to your SourceVerify account and create an API key. The key is shown once — copy it into your secret store.
export SOURCEVERIFY_API_KEY="sv_live_..."
For user-context requests (a web app on behalf of a signed-in user), exchange the user's credentials for a JWT instead:
curl -X POST https://api.sourceverify.app/v1/auth/login \
-H 'Content-Type: application/json' \
-d '{"email":"you@example.com","password":"..."}'
2. Health check
Confirm reachability before sending real traffic.
curl https://api.sourceverify.app/health
# → {"status":"ok"}
3. Read the build metadata
curl https://api.sourceverify.app/v1/version
# → {"version":"0.1.0","gitSha":"abc1234","env":"production"}
4. Submit a verification
Submit an artifact (binary upload or S3 reference) for verification. The response includes the SHA-256 content hash, the IPFS CID of the verification record, and — once anchoring completes — the on-chain transaction hash.
curl -X POST https://api.sourceverify.app/v1/verifications \
-H "X-Api-Key: $SOURCEVERIFY_API_KEY" \
-H 'Content-Type: application/json' \
-d '{ "artifactRef": "s3://my-bucket/article.pdf" }'
Note: the verification endpoints are under active implementation. See the API Reference for the live contract.
Next steps
- Authentication — JWT vs API key, scopes, key rotation.
- Verifications — submission, polling, verdict semantics.
- Proof & Anchoring — the proof tuple, IPFS, on-chain layer.
- API Reference — full interactive endpoint reference.