Skip to main content
POST
Link Entities by Filters

Link Entities by Filters

Link all entities that match a given filter to a project — without needing to enumerate individual IDs. This is the most efficient way to associate large historical datasets or ongoing data streams to a project. The operation is idempotent: entities already linked are skipped, so it is safe to call repeatedly with the same filters.
New API: This endpoint is part of the new API architecture.

Request

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Path Parameters

string
required
The UUID of the project to link entities toExample: b7f2a1c3-4d5e-6f7a-8b9c-0d1e2f3a4b5c

Body Parameters

string
required
The type of entities to link. Determines which filter fields are valid.Available values: logistic_requests, logistic_recharges, logistic_packages, invoices, file_readings
object
Filter criteria for selecting entities. The valid fields depend on entity_type — see the tables below.Pass an empty object {} to link all entities of the given type to the project.

Filter Fields by Entity Type

Unknown filter keys return a 422 error. Only the fields listed above are accepted.

Response

integer
Number of new links created
integer
Number of entities that were already linked (skipped)

Example

Successful Response

Common Errors

404 Not Found

Cause: Project not found or doesn’t belong to your organization

422 Invalid Filters

Cause: An unknown filter key was passed for the given entity_type
Solution: Check the filter fields table for your entity_type above. Only the listed fields are accepted — extra keys are rejected.

Link Entities

Link specific entities by ID

Unlink Entities

Remove entity-project associations