Delete entity override
This operation clears the override value from the specified field path on the entity.
Bearer authentication of the form Bearer <token>, where token is your auth token.
A Globally Unique Identifier (GUID) for your entity. This is a required field.
A human-readable entity description that’s helpful for debugging purposes and human traceability. If this field is empty, the Entity Manager API generates one for you.
Future time that expires an entity and updates the is_live flag. For entities that are constantly updating, the expiry time also updates. In some cases, this may differ from is_live. Example: Entities with tasks exported to an external system must remain active even after they expire. This field is required when publishing a prepopulated entity. The expiry time must be in the future, but less than 30 days from the current time.
Use noExpiry only when the entity contains information that should be available to other tasks or integrations beyond its immediate operational context. For example, use noExpiry for long-living geographical entities that maintain persistent relevance across multiple operations or tasks.
Human-readable descriptions of what the entity is currently doing.
Describes an entity’s specific characteristics and the operations that can be performed on the entity. For example, “simulated” informs the operator that the entity is from a simulation, and “deletable” informs the operator (and system) that the delete operation is valid against the entity.
The prioritization associated with an entity, such as if it’s a threat or a high-value target.
A message describing any transponder codes associated with Mode 1, 2, 3, 4, 5, S, C interrogations. These are related to ADS-B modes.
The relationships between this entity and other entities in the common operational picture (COP).
Symbology/iconography for the entity respecting an existing standard.