Bluetooth GATT Characteristic Reference
HTTP Status Code (0x2AB8)
The HTTP Status Code characteristic contains the Status-Code from the Status-Line of the first line of the HTTP Response Message, followed by one octet indicating the Data Status Bit Field indicating the status of the data received.
Quick Summary
Payload length is 3 bytes. This page is generated from official GATT XML and presented as implementation-ready guidance.
At a Glance
Key reference details for BLE implementation, interoperability testing, and AI-assisted troubleshooting.
| Property | Value |
|---|---|
| Name | HTTP Status Code |
| UUID | 0x2AB8 |
| Type | org.bluetooth.characteristic.http_status_code |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.http_status_code.xml |
| Field Count | 2 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Status Code | Mandatory | uint16 | - | - | - |
| Data Status | Mandatory | uint8 | - | - | - |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Data Status | 0 | 1 | Headers Received | The response-header and entity-header fields were not received in the HTTP response or stored in the HTTP Headers characteristic. | The response-header and entity-header fields were received in the HTTP response and stored in the HTTP Headers characteristic for the Client to read. |
| Data Status | 1 | 1 | Headers Truncated | Any received response-header and entity-header fields did not exceed 512 octets in length. | The response-header and entity-header fields exceeded 512 octets in length and the first 512 octets were saved in the HTTP Headers characteristic. |
| Data Status | 2 | 1 | Body Received | The entity-body field was not received in the HTTP response or stored in the HTTP Entity Body characteristic. | The entity-body field was received in the HTTP response and stored in the HTTP Entity Body characteristic for the Client to read. |
| Data Status | 3 | 1 | Body Truncated | Any received entity-body field did not exceed 512 octets in length. | The entity-body field exceeded 512 octets in length and the first 512 octets were saved in the HTTP Headers characteristic |
Byte Layout and Decode
Payload length is 3 bytes.
function decodePayload(dataView, offset = 0) {
const status_code = dataView.getUint16(offset + 0, true);
const data_status = dataView.getUint8(offset + 2);
return { status_code, data_status };
}Use Cases and Integration Notes
BLE Telemetry
Map characteristic values into dashboards and alerts for device observability.
Firmware Regression
Compare decoded fields across builds to detect protocol or scaling changes.
App Integration
Build stable parsing paths that convert raw payloads into typed app models.
Implementation Checklist
- Validate payload length and mandatory fields before decode.
- Decode with Bluetooth-specified signedness, unit, and exponent handling.
- Convert units at presentation boundaries to avoid drift in business logic.
- Persist raw packets and decoded values for reproducible troubleshooting.
FAQ
What is HTTP Status Code in Bluetooth GATT?
HTTP Status Code is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.http_status_code and UUID 0x2AB8.
What UUID identifies HTTP Status Code?
The UUID for HTTP Status Code is 0x2AB8.
How should I parse HTTP Status Code?
Payload length is 3 bytes.
Where does this definition come from?
This page is generated from the Bluetooth SIG mirror XML in the oesmith/gatt-xml repository.
How does this page support BLE implementation?
The page combines structured tables, practical Q&A, and JSON-LD metadata to help teams validate integrations and troubleshoot consistently.