Reads (coming soon) - Humanly Developer Docs

Not yet implemented. This page describes the planned MS7 (PLAT-42) conventions. Endpoints below are not available until that milestone ships.

Connect read routes (pull data from a vendor into your system) will follow shared conventions:

Pagination

Query param	Purpose
`cursor`	Opaque cursor from a previous response
`limit`	Page size (default and max TBD)

Responses will include pagination metadata in the Connect envelope (exact field names TBD in PLAT-42).

Filtering

Common filters (vendor-specific routes may add more):

Query param	Purpose
`updatedSince`	ISO-8601 timestamp — records changed after this time
`status`	Vendor-specific status filter where applicable

Response shape

Successful reads return vendor data passthrough in data, wrapped in the standard Connect envelope with meta.requestId. See also Pagination on the Platform tab.

Writes — idempotency and validation (planned)
Standardized vendor endpoints — available today