Types overview - Bitrix24 JS SDK

Every type under packages/jssdk/src/types/ is re-exported from @bitrix24/b24jssdk. Only a subset has a dedicated page today; the rest are either documented as part of the class/manager that uses them, or tracked as a follow-up. This table is the map.

Dedicated pages

Module	Covers	Page
`types/common.ts`	scalar aliases, `Fields`, `MultiField`, `UserFieldType`, `DataType`	Common types
`types/payloads.ts`	`PayloadTime`, `GetPayload`, `ListPayload`, `BatchPayload`, `SuccessPayload`, `Payload`	Payload types
`types/b24.ts`	`TypeB24`, `ApiVersion`	TypeB24
`core/result.ts`	`IResult` (implemented by `Result` / `AjaxResult`)	IResult

Surfaced through another page

These modules do not have their own type page — their types are documented on the page for the class or feature that consumes them.

Module	Surfaced via
`types/http.ts`	Core HTTP
`types/limiters.ts`	Limiters
`types/logger.ts`	Logging
`types/b24-helper.ts`	Helper
`types/pull.ts`	Pull
`types/slider.ts`	Frame slider

Follow-up (per-domain pages)

Per-domain type modules do not yet have a dedicated page. They are tracked as follow-up work in issue #125 and are out of scope for v1.2.0 (which prioritises common + payloads).

Module	Status
`types/auth.ts`	Follow-up (partially surfaced via Frame auth)
`types/placement/index.ts`, `types/placement/uf.ts`	Follow-up (Frame placement documents the `PlacementManager` API, but the `IPlacementUF` field shape is not yet covered)
`types/user.ts`	Follow-up
`types/handler.ts`	Follow-up
`types/crm/index.ts`, `types/crm/entity-type.ts`, `types/crm/item-delivery.ts`, `types/crm/item-payment.ts`, `types/crm/productrow.ts`	Follow-up
`types/catalog/index.ts`	Follow-up
`types/bizproc/index.ts`, `types/bizproc/activity/index.ts`	Follow-up
`types/event/index.ts`	Follow-up