ROUTETARGET: Route Target
The ROUTETARGET entity: A BGP extended community used to control route import/export between VRFs in MPLS L3VPN environments.
Default definition. This article describes the default
ROUTETARGET definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches ROUTETARGET.Entity properties
| Property | Value |
|---|---|
| Entity code | ROUTETARGET |
| Display name | Route Target |
| Plural | Route Targets |
| Level | 41900 |
Use cases
ROUTETARGET is a BGP extended community value used in MPLS L3VPN to control which routes are imported into and exported from VRFs. The format is typically ASN:NN (e.g., 65000:100) or IP:NN (e.g., 10.0.0.1:100). Route targets enable controlled route leaking between VRFs - for example, a shared services VRF might export its routes with RT 65000:999, and all tenant VRFs import that RT to reach shared services.
This entity is referenced by VRF import/export target fields, replacing the free-text RT fields on LOGICALCONNECTION.
Fields
Route Target Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Format: ASN:NN or IP:NN (e.g., 65000:100) |
description | text (multi-line) | Description |
Relationships
- Related lists:
VRF(formatobjectRef),VRF(formatobjectRef).
Creating a Route Target via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ROUTETARGET",
"level": 41900,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description"
} Listing Route Targets records
GET /v1/entities/ROUTETARGET/SUB