Returns the fields, modes, and properties of a target object on a connection.
Pass the target object identifier to retrieve the fields available for mapping on that object. These are the destination fields you can reference when configuring field mappings in a model sync.
📘 To list available target objects and their identifiers, use
GET /api/connections/{id}/modelsync/targetobjects.
Fields returned here reflect the connection’s current cached state. If the
upstream object schema has changed, trigger a schema refresh with
POST /api/connections/{id}/schemas/refresh
before calling this endpoint.
Some connections support creating a new destination object as part of a
model sync — for example, a Facebook Ads custom audience or a LinkedIn Ads
contact list. In that case there is no existing target identifier to pass;
instead, describe the new target with the same properties returned in the
target_creation block of
GET /api/connections/{id}/modelsync/targetobjects,
and this endpoint will return the fields the new target will expose.
Exactly one of target or properties must be supplied. Each input is
sent as a separate properties[key]=value query parameter. For a Facebook
Ads connection that requires an account and a name:
The response shape is identical to the existing-target form. For backends
where the new target’s field set is fixed (most ads platforms), fields
contains those fields; for backends where the columns are user-defined
(e.g. a SQL database), fields will be empty and the caller defines the
columns at mapping time.
When properties is supplied, the refresh parameter is ignored — a
not-yet-created target has no cached schema to refresh.
Basic organization-scoped API key
Identifier of the target object (e.g. schema.table for a database destination, object name for a SaaS destination). Required unless properties is supplied.
Target-creation property values, supplied as properties[key]=value, matching the target_creation.properties returned by GET /api/connections/{id}/modelsync/targetobjects. When supplied, the response describes the not-yet-created target that would result from these inputs, in the same shape as for an existing target. Exactly one of target or properties must be supplied.