MurmurHash

Overview

MurmurHash implements MurmurHash3 in two forms. `variant=32` (the default) is MurmurHash3_x86_32; `variant=128` is MurmurHash3_x86_128, transcribed from Austin Appleby's reference code. Any `variant` other than `32` produces the 128-bit hash.

The `text` you POST is hashed one byte per character, taking the low eight bits of each JavaScript character code. For ASCII text this is identical to hashing the UTF-8 bytes, so results match standard MurmurHash3 implementations. For characters outside ASCII it is not: an accented letter or emoji contributes only the low byte of its code, so hashes of non-ASCII text will not match a library that hashes UTF-8. Encode such input, for example as hex or Base64, before comparing across systems.

`seed` is parsed as an integer and defaults to 0. The same text and seed always give the same hash, and changing the seed gives an unrelated value.

For the 32-bit variant, `hash` is the result as an unsigned integer from 0 to 4,294,967,295, and `hashHex` is the same value as eight hex digits, zero-padded. For the 128-bit variant both `hash` and `hashHex` contain the same 32-character hex string, because the value is too large to return as a JSON number. It is the four 32-bit state words in order, each written in little-endian byte order. `variant` is returned as `murmur3_32` or `murmur3_128`, and `seed` echoes the seed used. There is no plan-based difference in the output.

Live Test MurmurHash API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

1
2
3
4
5
6
7
8

curl -X POST https://api.apiverve.com/v1/murmurhash \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "hello world",
  "seed": 0,
  "variant": "32"
}'

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

const res = await fetch('https://api.apiverve.com/v1/murmurhash', {
  method: 'POST',
  headers: {
    'x-api-key': 'your_api_key_here',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "text": "hello world",
  "seed": 0,
  "variant": "32"
}),
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

import requests

res = requests.post(
    "https://api.apiverve.com/v1/murmurhash",
    headers={"x-api-key": "your_api_key_here"},
    json={
    "text": "hello world",
    "seed": 0,
    "variant": "32"
},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

package main

import (
	"fmt"
	"io"
	"net/http"
	"strings"
)

func main() {
	body := strings.NewReader(`{
  "text": "hello world",
  "seed": 0,
  "variant": "32"
}`)
	req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/murmurhash", body)
	req.Header.Set("Content-Type", "application/json")
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

Parameters

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

1
2
3
4
5
6
7
8
9
10

{
  "status": "ok",
  "error": null,
  "data": {
    "hash": 1586663183,
    "hashHex": "5e928f0f",
    "variant": "murmur3_32",
    "seed": 0
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Use cases

Hash Tables

Generate keys for hash-based data structures

Data Partitioning

Consistently distribute data across shards

Bloom Filters

Fast hashing for probabilistic data structures

Deduplication

Quickly identify duplicate records

Other ways to use MurmurHash

Set up MurmurHash on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Related

More in Data Processing: