IATA Resolution 600a Air Waybill (AWB) 11-Digit MOD-7 Spec
Verify 11-digit IATA Air Waybill check digits and airline prefixes with deterministic MOD-7 arithmetic. This specification documents the exact field layout, checksum rules, and validation behavior so your integration matches IATA Resolution 600a & Resolution 722e without reading the source standard.
⚡ Live IATA Resolution 600a Air Waybill (AWB) 11-Digit MOD-7 Spec Interactive Workbench
Test real-time validation and schema parsing for IATA Resolution 600a Air Waybill (AWB) 11-Digit MOD-7 Spec directly in your browser. Runs in sub-5ms with zero setup.
{
"status": "Click RUN VALIDATION to execute on the Cloudflare edge..."
}
Air waybill validator — free, runs entirely in your browser.
Quick Summary: Verify 11-digit IATA Air Waybill check digits and airline prefixes with deterministic MOD-7 arithmetic. Validates strictly against IATA Resolution 600a & Resolution 722e with sub-5ms in-memory response times.
Specification & Structural Breakdown
Technical Summary: Validates strictly against IATA Resolution 600a & Resolution 722e. Payloads are parsed in memory and return clean, typed JSON in milliseconds with zero data logged.
An IATA Air Waybill consists of a 3-digit airline accounting prefix, a hyphen or space, a 7-digit serial number, and a 1-digit MOD-7 check digit.
| Part | Digits | Example | Function |
|---|---|---|---|
| Airline Prefix | 3 digits | 016 | Identifies airline (016 = United) |
| Serial Number | 7 digits | 1234567 | Unique cargo consignment sequence |
| Check Digit | 1 digit | 5 | Serial % 7 (1234567 % 7 = 5) |
Parsed JSON Response Model
The edge microservice transforms input payloads into strongly-typed hierarchical JSON envelopes with sub-5ms latency:
{
"awb": "016-12345675",
"airline": "United Airlines",
"checkDigitValid": true
}
Copy-Paste Integration Code (6 Languages)
Integrate IATA Resolution 600a Air Waybill (AWB) 11-Digit MOD-7 Spec directly into your production application with native, zero-dependency code snippets in cURL, Node.js, Python, Go, C#, and a ready-to-paste Claude prompt. Get a free API key → (no credit card required):
curl --request POST \
--url "https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate" \
--header "Content-Type: application/json" \
--header "x-api-key: YOUR_API_KEY" \
--data '{
"awb": "016-12345675"
}'const response = await fetch("https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate", {
method: "POST",
headers: {
"Content-Type": "application/json",
"x-api-key": process.env.API_KEY || "YOUR_API_KEY"
},
body: JSON.stringify({
"awb": "016-12345675"
})
});
const data = await response.json();
console.log(data);import requests
import json
url = "https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate"
headers = {
"Content-Type": "application/json",
"x-api-key": "YOUR_API_KEY"
}
payload = {
"awb": "016-12345675"
}
response = requests.post(url, json=payload, headers=headers)
print(response.json())package main
import (
"bytes"
"fmt"
"io"
"net/http"
"os"
)
func main() {
url := "https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate"
payload := []byte(`{"awb":"016-12345675"}`)
req, _ := http.NewRequest("POST", url, bytes.NewBuffer(payload))
req.Header.Add("Content-Type", "application/json")
req.Header.Add("x-api-key", os.Getenv("API_KEY"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main()
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", Environment.GetEnvironmentVariable("API_KEY") ?? "YOUR_API_KEY");
var json = @"{""awb"":""016-12345675""}";
var payload = new StringContent(json, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate", payload);
var content = await response.Content.ReadAsStringAsync();
Console.WriteLine(content);
}
}Integrate the StanzaAPI iata-validator micro-API.
Endpoint: POST https://api.stanzaapi.com/iata-validator/api/v1/iata/awb/validate
Auth header: x-api-key: YOUR_API_KEY
Content-Type: application/json
Request body:
{
"awb": "016-12345675"
}
Rules:
- Send the request with a 2-second timeout.
- Parse the standard envelope { success, data, meta: { latency_ms, version } }.
- On failure, read { success: false, error, code } and branch on the code.
- Do not retry 4xx responses; surface the error code to the caller.
- Treat invalid-but-well-formed payloads as HTTP 200 with data.valid === false.Frequently Asked Questions & Technical Notes
The check digit is 0. Valid check digits are always in the range 0 through 6.
Related IATA Air Cargo AWB & Aviation Validator API Formats
Explore sibling specifications and standards in the same developer cluster:
IATA 3-Digit Airline Accounting Prefix Directory & Resolver
Instant lookup of 500+ official 3-digit IATA airline prefixes to carrier metadata and designators.
View Format →IATA 13-Digit E-Ticket Validator & Resolution 722e Check Digit
Validate 13-digit passenger electronic ticket numbers and coupon structures across global GDS platforms with instant MOD-7 check digit verification.
View Format →IATA 3-Letter Airport Code & Metropolitan Area Standard
Validate and resolve 3-letter IATA airport and metropolitan destination codes.
View Format →Complementary Enterprise APIs
Seamlessly orchestrate data pipelines across adjacent financial, regulatory, and supply-chain protocols:
ISO 6346 Intermodal Container Validator →
Cross-validate air-sea intermodal transfer identifiers and check digits.
GS1 2027 Barcode & QR Decoder →
Decode GS1-128 logistic labels, SSCC handling units, and serial shipment containers.
ISO 20022 Financial Messaging →
Reconcile automated air freight billing and cargo settlement statements.