API Getting Started

Paid plan

Authenticate and make your first case search request using the SooperKanoon API.

60-second version

SooperKanoon offers a JSON API for case search, advanced search, and latest cases.
Sign up for API access - your GUID API key is emailed to you after registration.
Read full endpoint reference at API Documentation - this guide gets you started only.

In one sentence

Use the SooperKanoon API at /api with your GUID key to programmatically search cases and fetch judgment data - see API Documentation for complete endpoint details.

Before you start

The API returns JSON responses. Base paths mirror the website (/cases/search/…, /cases/advsearch/…, /latest.json). You need an API-enabled SooperKanoon account; your GUID authentication key is sent to your email at signup. API usage may be metered against your account balance (amount_remaining appears in responses). Do not duplicate the full API reference here - use the official docs page for parameters, samples, and schemas.

Steps

Ensure you have a SooperKanoon account with API access (sign up at Pricing if needed).
Locate your GUID in the welcome/API email sent at registration.
Open API Documentation and read the Authentication section.
Send the GUID in every request header:

`` HTTP-GUID: your-api-key ``

Try a simple case search (append .json to the URL):

`` GET /cases/search/name:transfer-of-property.json ``

Parse the JSON response - fields include totalno, jids (case URLs), and amount_remaining.
Fetch a single case by requesting a URL from the jids array (also with .json and your GUID header).
Explore Advanced Search and Get Latest Cases sections in API Documentation for additional endpoints.
Optional: use the Run in Postman button on the documentation page to fork the official collection.

What you'll see

Successful responses return JSON with result counts, pagination info, and arrays of case endpoint paths. Authenticated responses include remaining account credit. Errors typically mean a missing/invalid GUID or malformed URL - check the doc examples for correct name:, court:, and year: path segments (spaces as dashes, no special characters).

Common mistakes

Omitting .json at the end of URLs - the API requires the trailing .json suffix documented on API Documentation.
Sending the GUID as a query parameter instead of the HTTP-GUID header - follow the authentication section exactly.
Duplicating website search syntax incorrectly - replace spaces with dashes and strip special characters as shown in doc examples.
Building integrations from this help article alone - always refer to /api/documentation for the authoritative, up-to-date reference.

Tips

Start with /cases/search/name:your-phrase.json before advanced multi-field queries.
Monitor amount_remaining in responses to track API credit usage.
For latest judgments, use GET /latest.json - details in the Get Latest Cases section of the API docs.
Keep your GUID secret - treat it like a password; rotate by contacting [email protected] if compromised.