T3 Endpoint IDs¶

Every T3 API endpoint that lists or reports Metrc data has a T3 endpoint id. It is the one name every feature uses for an endpoint:

• Search takes t3EndpointIds and labels every result with its t3EndpointId.
• Metrc Pages gives each table's t3EndpointId.
• Tag lists store a t3EndpointId, and resolve and COA extraction take one.
• Saved reports record the t3EndpointId of the report they run.

The interactive docs show each endpoint's id at the end of its summary.

A collection's list endpoint and its object endpoint share an id: METRC_ACTIVE_PACKAGES names both /v2/packages/active and /v2/packages/active/{id}. Its /super endpoints have their own id, and each report has its own.

So a search result says where to load the full record:

PATHS = {"METRC_ACTIVE_PACKAGES": "/v2/packages/active", "METRC_ACTIVE_ITEMS": "/v2/items"}

hit = send_api_request(
    api_client,
    "/v2/search",
    params={"licenseNumber": license_number, "query": "1A4FF0100000022000000123"},
)["data"][0]

record = send_api_request(
    api_client,
    f"{PATHS[hit['t3EndpointId']]}/{hit['matchedEntry']['id']}",
    params={"licenseNumber": license_number},
)

The OpenAPI spec carries every id as x-t3-endpoint-id, so the full mapping can be built from it:

import requests

spec = requests.get("https://api.trackandtrace.tools/v2/spec/openapi.json").json()

paths = {
    operation["x-t3-endpoint-id"]: path
    for path, operations in spec["paths"].items()
    for operation in operations.values()
    if "x-t3-endpoint-id" in operation and "{" not in path
}

Collections¶

The collections search, tag lists or COA extraction accept. ✅ marks the features that accept the id. Every other endpoint's id is in the interactive docs.