Java SDK

com.github.ekoindia:eps-sdk-java is a client for every EPS API built on the JDK's own java.net.http. One generic call(slug, params) covers all of them: the endpoint catalog, each endpoint's params and which of them are required are packaged from the same surface these docs are built from, so the client validates your input before it signs and sends anything.

Install

com.github.ekoindia:eps-sdk-java

Your first call

Read the two keys from the environment, pick an environment, and call an endpoint by its slug:

import in.eko.eps.EpsClient;
import java.util.Map;

EpsClient client = EpsClient.builder()
    .developerKey(System.getenv("EPS_DEVELOPER_KEY"))
    .accessKey(System.getenv("EPS_ACCESS_KEY"))
    .initiatorId("9962981729")
    .environment("sandbox")
    .build();

Map<String, Object> result = client.call("pan-lite", Map.of(
        "pan_number", "ABCDE1234F",
        "name", "Rajesh Kumar",
        "dob", "1994-08-29"
    ));
System.out.println(result);

initiatorId and userCode are near-constant per developer, so set them once on the builder. They are injected into every call as the wire params initiator_id and user_code — pass either in the params map to override it for a single call.

Client options

The client is built through a fluent builder; every option below is a builder method.

API surface

The SDK is deliberately small. There is no method per endpoint — call() takes the slug, and the packaged surface supplies the method, path, and validation rules.

Authentication

You never compute a signature yourself. On every request the client derives secret-key = base64(HMAC-SHA256(timestamp, base64(accessKey))) and sends it with secret-key-timestamp and developer_key. EpsClient.sign is public only so you can reproduce a signature while debugging a 403.

File uploads

A single type: "file" param flips the whole request to multipart/form-data. You still pass every parameter flat; on the wire the SDK packs them the way the API expects — one form field named form-data holding all the non-file params as a single JSON object, plus one part per upload. A null param is dropped (a form field has no null encoding), while a null nested inside a map value is preserved.

File params accept:

• A String path, a java.nio.file.Path, or a java.io.File
• An EpsClient.EpsFile(name, content) for an in-memory upload

Errors and timeouts

Every failure is an unchecked exception, so nothing forces a try/catch you do not want. A non-2xx response throws EpsHttpException — the decoded envelope is on body.

Environments

Switch with .environment(...); there is no base-URL override.

Java-specific notes

• Upload parts are sent as application/octet-stream; the MIME type is not sniffed.
• Gson is configured with serializeNulls() — required for wire conformance, since every other SDK keeps explicit nulls.

Every endpoint

call() accepts every slug in the EPS catalog. Each endpoint's reference page shows its parameters, response fields and a ready-to-paste Java snippet.