AdminConsole
API Client Studio

From one-off requests to reusable clients.

Download eight source-grounded language packages covering all 162 normalized operations. Every package preserves exact source fingerprints, authentication placement, generation choices, and fixture-first tests—without embedding credentials or claiming unverified support.

Choose a language Read the catalog JSON
Languages8TypeScript through Ruby
Operations each162Exact normalized contracts
Total bindings1,296Generation-aware identities
Fixture calls0Offline by default
One contract, eight idioms

Explore locally. Qualify live deliberately.

The same canonical operation registry drives every package. Fixture execution builds the exact request locally, applies required-input validation, and returns deterministic evidence without reaching Mappls. A package is an integration accelerator—not an entitlement, compatibility statement, native SDK replacement, or production approval.

fixture-first.mjs
import { MapplsContractClient } from "./src/mappls-contract-client.mjs";

const client = new MapplsContractClient();
const result = await client.execute("search-text-v1", {
  query: { query: "Connaught Place" }
});

console.log(result.fixture, result.request.url);
Checksummed downloads

Choose your runtime.

Every ZIP contains the same 162-operation registry, a manifest, credential template, source, native fixture test, and exact verification command.

Node.js 22+

TypeScript

Bounded live adapter
Bindings
162
Verification
runtime executed
Files
8
Tests
1 native fixture
node --test tests/fixture.test.mjs
Python 3.11+

Python

Bounded live adapter
Bindings
162
Verification
runtime executed
Files
6
Tests
1 native fixture
python3 -m unittest tests/test_fixture.py
Java 17+

Java

Fixture adapter
Bindings
162
Verification
runtime executed
Files
8
Tests
1 native fixture
sh scripts/test.sh
Kotlin/JVM 1.9+

Kotlin

Fixture adapter
Bindings
162
Verification
source and manifest verified
Files
8
Tests
1 native fixture
sh scripts/test.sh
.NET 8+

C#

Fixture adapter
Bindings
162
Verification
source and manifest verified
Files
8
Tests
1 native fixture
dotnet test
Go 1.22+

Go

Fixture adapter
Bindings
162
Verification
source and manifest verified
Files
8
Tests
1 native fixture
go test ./...
PHP 8.2+

PHP

Fixture adapter
Bindings
162
Verification
source and manifest verified
Files
6
Tests
1 native fixture
php tests/fixture_test.php
Ruby 3.1+

Ruby

Bounded live adapter
Bindings
162
Verification
runtime executed
Files
6
Tests
1 native fixture
ruby tests/fixture_test.rb
Readiness is not a single badge

Two independent proof axes.

Transport capability and packaging verification answer different questions. Read both before selecting a package.

Transport

Fixture + bounded live

TypeScript, Python, and Ruby include an opt-in live HTTP adapter with fixed source-declared hosts, environment-only credentials, required-input checks, a 10-second timeout, a 1 MiB response bound, and guarded state-changing retries.

Transport

Fixture adapter

Java, Kotlin, C#, Go, and PHP stop at exact request construction. Your application owns live HTTP transport, policy, observability, retries, and qualification.

Packaging

Runtime executed

TypeScript, Python, Java, and Ruby fixture tests ran in the packaging environment. This proves the bundled fixture path at the recorded source snapshot—not live behavior.

Packaging

Source + manifest verified

Kotlin, C#, Go, and PHP were deterministically assembled and structurally inspected because those toolchains were unavailable in the packaging environment. Run the included native test in your CI.

Package anatomy

Every decision travels with the code.

  1. 01
    Exact operation registry

    All paths, methods, source fingerprints, preferred and alternate generations, state models, and journey roles.

  2. 02
    Credential-empty manifest

    Environment variable names and placement rules only. No token, secret, customer payload, or workstation path.

  3. 03
    Fixture-first adapter

    Deterministic request construction and response evidence with zero provider calls.

  4. 04
    Native verification

    A language-native fixture test and exact command to run after extraction.

  5. 05
    Explicit authority

    No inferred entitlement, compatibility, retry safety, live behavior, support status, or release approval.

Authority boundary

Generated HTTP clients complement native SDKs.

Generated contract clients make source-backed HTTP integration reusable; they do not replace native SDKs, prove provider support or entitlement, make state-changing operations retry-safe, or grant production approval.

Compare native SDKsPlan live conformance