LearnReferenceBlog
Protocol

String Formats

When building records, some string fields expect a specific format.

A user’s unique domain name.

username.host.com

  • Supports the following characters: a-z0-9.-.

  • Allows a maximum of 252 characters.

  • Unicode characters should be transformed using IDNA2008 encoding­.

A record’s 128-bit identifier.

63bc5149fa784b749a3d6d404dfcb3c9

  • Hex-encoded, all-lowercase, without any spaces.

  • Uniquely identifies a record from a given entity.

A precise point in time.

2024-02-19T15:20:51.3590000Z

  • Follows RFC 3339­ with no offset (UTC).

  • Always interpreted with millisecond precision.

SHA256 hash of a record.

d195f2608d34c61e7de8d82116806bf104ca47fdd16f58198ab37dec544b430b

SHA256 hash of a blob.

752f11f6d795a8ca8b501843aa4340493b63cdb867b3e464b386e3fce8230d3e

  • Hex-encoded, all-lowercase, without any spaces.

  • Uniquely identifies a blob globally.

Standard absolute URI.

http://baq.dev/docs/reference?theme=dark#usage

  • In the scheme://authority/path?query#fragment format.

  • Maximum length of 2000 unicode code points.

Queryable string field.

Any Value

  • Supports unicode.

  • Allows a maximum of 100 characters.

  • Can be queried through the /records­ endpoints.

© 2024 Quentez