Not Supported Yet
This page lists common expectations that are not part of the current Public API v2 surface.Versioned date paths
Use/api/v2, not date-versioned paths.
Query, assert, and schema path names
Use the underscore-prefixed route names.Record types not exposed today
These record types are not available as Public API v2 record routes today:commentuserteamemail_threademail_messagevoice_call- canonical junction record types such as
contact_account_roleandcontact_opportunity_role
record_reference targets inside other records. That does not mean they are readable or writable as top-level Public API v2 records.
Canonical junction endpoints
Create and manage relationship edges through parent-scoped relationship endpoints instead of canonical junction record endpoints.Generic attribute item reads
Public API v2 supports selected attribute sub-resources, such as contact emails, contact phone numbers, and account domains. It does not expose a generic item-levelGET surface for every array attribute.
Batched relationship writes
Public API v2 does not expose a single endpoint that writes multiple relationship names at once with partial-failure metadata. Use the parent-scoped relationship endpoints for one relationship at a time.Custom object limitations
Custom objects can be created, read, queried, updated, archived, connected through relationships, and inspected throughGET /api/v2/_schema/{record_type}. The unsupported case is using a generic /api/v2/custom_object/_schema endpoint to discover every custom object type at once.