Skip to main content

Overview

The Inbox API uses bracket notation for encoding complex data types (objects and arrays) in query parameters. This guide covers the encoding rules and common patterns.

Objects

Objects are encoded using bracket notation with property names. Object value:
Encoded in URL:

Cursor example

Use the flat cursorId and cursorTimestamp parameters for pagination. The bracket notation form (cursor[id], cursor[timestamp]) is also supported but deprecated.

Arrays

Arrays can be encoded in three ways. All are supported by the API. Array value:

Option 1: repeated parameters (simplest)

Option 2: empty bracket notation

Explicitly denotes an array. Useful when there’s only one value:

Option 3: indexed bracket notation

Most explicit. Allows reordering and sparse arrays:

Thread filters

The GET /threads endpoint supports advanced filtering via the filters parameter using nested bracket notation.

By tags

By status

By assignee

By campaign

Sort order

Combined filters

Multiple filters combine with AND logic:

Filter parameter reference

URL encoding special characters

Values containing special characters must be URL-encoded: Most HTTP clients handle this automatically.

Helper function

A utility for encoding filter parameters:

Common mistakes

Wrong: Using incorrect filter key structure
Correct:

Pagination

Cursor-based pagination patterns

Managing threads

Thread filtering examples

List threads

Threads endpoint reference

API introduction

API overview and encoding rules