Skip to content

Changelog

All notable changes to @makegov/tango-node will be documented in this file.

This project follows Semantic Versioning.

[Unreleased]

[1.5.0] - 2026-10-29

Added

  • fsc filter on listDibbsRfqs(), listDibbsRfps() and listDibbsAwards() (Tango API 5.13.0). Filters by Federal Supply Class, the first four digits of the 13-digit NSN (NSN 6515012345678 is FSC 6515). Each value must be exactly four digits, and several are OR'd with |, e.g. "6515|6530"; any other value makes the API return a 400. It combines with every other filter, nsn and part_number included.

Changed

  • The vendored API contract now tracks Tango API 5.13.0. Its new financial-assistance award endpoints are not yet in the SDK and are recorded as known gaps in both conformance baselines.

[1.4.1] - 2026-10-19

Changed

  • Dev-dependency security update: vitest and @vitest/coverage-v8 move to 4.1.12, which also brings @vitest/mocker to its patched release. The published package is unaffected; its only runtime dependency remains commander.

Fixed

  • rateLimitInfo.limitType now says which limit a 429 hit. It only read an X-RateLimit-Type header the API never sends, so it was always null. On a 429 it now reads the rate's name from the API's detail (Rate limit exceeded for daily. Please try again in 16 hours, 58 minutes.) and reports "daily" or "burst", matching tango-python's limit_type; a per-endpoint premium daily budget reports "daily". It is null when the detail names neither, and an X-RateLimit-Type header still wins if one is sent. TangoRateLimitError gains the same limitType, plus detail with the API's message.

[1.4.0] - 2026-10-19

Added

  • obligations_by_fiscal_year(fiscal_year, obligated) shape expand on contracts, IDVs, OTAs and OT IDVs (Tango API 5.11.0; parity with tango-python). Returns the award's obligations per federal fiscal year, oldest first, each rounded to cents. The new FiscalYearObligation model type and schema carry fiscal_year as an integer and obligated as a decimal, which the shaped response normalizes to a string like every money field. The API always sends null on IDVs and OT IDVs, whose transactions report a running lifetime total; the shaped contract and IDV methods read a null nested list as [], as they do for every nested list.
  • attachments(extraction_status) shape field on opportunities and notices (Tango API 5.11.0; parity with tango-python). Reports pending, extracting, completed, failed or unsupported for each attachment, so you can tell why extracted_text is missing. OpportunityAttachment gains the field, typed as an open string.
  • commercial_item_acquisition_procedures filter on listContracts() and listIdvs() (Tango API 5.10.0; parity with tango-python), and on listIdvAwards() and listIdvChildIdvs(), which share those options. Filters by the FPDS commercial item acquisition procedures code: A (commercial products/services), B (products or services pursuant to FAR 12.102(f)), C (services pursuant to FAR 12.102(g)), D (commercial procedures not used) or E (DoD Section 803 Commercial Solutions Opening). Codes are case-insensitive and pipe-separated for OR, e.g. "A|E"; an unknown or multi-character code matches nothing. The API does not offer it on OTAs or OT IDVs, so listOtas() and listOtidvs() do not type it.
  • PaginatedResponse.countType (parity with tango-python). "exact" or "approximate", read from the API's X-Results-CountType header on every list method (null when the API doesn't send it). Past 1,000 matches the contract, IDV, opportunity and notice lists may return a query-planner estimate as count, which can be well off; this is how a caller tells the two apart. It is taken from each response itself, so concurrent calls on one client can't see each other's value the way lastResponseHeaders can.
  • Attachment file and link counts on opportunities and notices (Tango API 5.9.0; parity with tango-python). Opportunities accept meta(files_count,links_count) beside meta(attachments_count), and notices accept file_count and link_count beside attachment_count. An attachment's type is file (a document; only a file has extracted text) or link (a URL the notice lists). The new fields count each, and the existing total still counts every attachment, links included. An attachment of any other type counts only in the total, so files plus links need not equal it. The new fields are null until a record has been counted, so read null as unknown, not zero. Opportunity gains a typed meta (the new OpportunityMeta), Notice gains the three counts, and docs/API_REFERENCE.md documents the rules. The SDK's default shapes are unchanged, so name the fields in shape.
  • Federal Register documents (Tango API 5.3.0; parity with tango-python). listFederalRegisterDocuments(options) and getFederalRegisterDocument(uuid, options) over /api/federal_register/, plus a FederalRegisterDocument model interface, a registered shape schema, and the FEDERAL_REGISTER_MINIMAL / FEDERAL_REGISTER_COMPREHENSIVE defaults. These are the rules, proposed rules, notices and presidential documents published in the Federal Register since 1994. All seventeen of the API's filters are typed options on ListFederalRegisterDocumentsOptions, including comments_open, cfr_title / cfr_part, rin, and both agency (a Tango organization, including its sub-agencies) and fr_agency (the Federal Register's own agency slug).

    getFederalRegisterDocument() takes the document's uuid, not its document_number, because a document number is not unique on its own: the Federal Register reused some before 2016. Look a document up by number with listFederalRegisterDocuments({ document_number }). full_text is available on the detail method only when named in shape, and neither default shape includes it, since it can run to several MB. ordering: "rank" requires a non-empty search. Documents published before 2008 are mostly typed Uncategorized Document, so a type filter undercounts that era.

  • Award fields on opportunities and notices (Tango API 5.5.0; parity with tango-python). ListOpportunitiesOptions types the awarded and awardee_uei filters, both of which search every opportunity rather than only active ones. Opportunity shapes accept awarded, award_count, award_date, award_amount, awardee, awardee_uei, solicitation_opportunity_id and an awards(...) expand (a list, with award_number, award_date, award_amount, awardee, awardee_uei, notice_id, opportunity_id); notice shapes accept award_date, award_amount, awardee and awardee_uei.
  • agency filter on listBudgetAccounts(), listExclusions() and listItDashboard() (Tango API 5.3.0; parity with tango-python). It takes a Tango agency name, abbreviation, code or organization key (e.g. EPA) and matches the whole organization, so a department includes its sub-agencies; OR several with |. On exclusions it scopes by the excluding agency. On IT Dashboard it is available at every plan.
  • cycle_name filter on listSbirTopics() (Tango API 5.3.1), an exact match on the DSIP solicitation cycle such as DOD_SBIR_2026_P1_CBZ. SBIR topic shapes accept cycle_name.
  • Budget account source_anomalies and account_category (Tango API 5.7.0). BudgetAccount gains account_category ("budgetary" or "credit_financing" today, typed as an open string) and source_anomalies, a list that is [] when the row is clean. Each entry is a new BudgetSourceAnomaly (with BudgetSourceAnomalySource and BudgetSourceAnomalyRow for its upstream rows), and every property on it is optional. action is "capped" when a served value was clamped to its bound and "flagged" when it is served as reported; code is an open string. ListBudgetAccountsOptions types the new account_category and account_category__in filters. There is no anomaly filter. The default ordering now puts accounts with a null enacted_ba last, which is documented on the options interface and in docs/API_REFERENCE.md.
  • Budget account data_through_period (Tango API 5.8.0). BudgetAccount gains data_through_period, the File A fiscal period (1–12) an account-year's figures run through, so the latest fiscal year is partial until it reaches 12; it is null when the row has no File A data. ListBudgetAccountsOptions types the data_through_period, data_through_period__gte, data_through_period__lte and data_through_period__isnull filters, sent verbatim under their dunder names.
  • Shapes accept the fields the API added through 5.9.0. The organization(...) expand on budget accounts, exclusions, SBIR topics and SBIR solicitations (with organization_id on the first two); account_category, data_through_period and source_anomalies on budget accounts; and holder_count and order_winner_count on vehicles. The SDK rejected these client-side before. Default shapes are unchanged.
  • matched_by on agency-filter diagnostics (Tango API 5.9.0; parity with tango-python). Each entry of PaginatedResponse.meta.resolved_filters[<filter name>] that resolved now says how its token matched: key (an organization UUID), code (a 3-digit CGAC or 4-digit FPDS code), name (the organization's name, including a department's everyday name, a spelling variant or a rename), alias (an abbreviation or the organization's own alias) or fuzzy (a looser text match, worth checking against the resolved name). An entry that did not resolve has no matched_by. meta is passed through as the API sends it, so no code change was needed to receive the field; it is now documented on the interface and in docs/API_REFERENCE.md and pinned by a test. agencyWarnings, unresolvedAgencyTokens and resolvedAgencies are unchanged.
  • GSA eBuy requests (Tango API 5.1.0). Four methods: listEbuyRequests(options) over /api/ebuy/requests/, getEbuyRequest(rfqId, options), getEbuyAttachmentUrl(rfqId, docSeqNum) and getEbuyAccess(). Every filter the API accepts is a typed option on ListEbuyRequestsOptions (search, rfq_id, reference_number, request_type, status, sin, schedule, buyer_agency, agency, contract_number, the issue_date_* and close_date_* bounds, ordering; agency needs Tango API 5.3.0), with new EbuyRequestRecord, EbuyAttachmentRecord and EbuyAccess types and registered EbuyRequest / EbuyAttachment shape schemas.

    Results are scoped to the GSA schedule contracts linked to the caller's account, and an account with none gets an empty list rather than an error; getEbuyAccess() reports enabled, a reason (tier_required or no_contract_grant) and the caller's own contracts. status is frozen at the last-seen state, so Open means "open the last time it was seen" — last_seen is the staleness signal.

    getEbuyAttachmentUrl() returns the short-lived presigned URL the download endpoint redirects to, without following it. An attachment that is an external link throws the new TangoEbuyAttachmentLinkError, a TangoValidationError whose url is the link target. The HTTP client gained getRedirectLocation() to support it.

    attachments(extracted_text) returns the text extracted from an attachment's document (Tango API 5.9.1). The field joins EbuyAttachmentRecord and the EbuyAttachment shape schema. It must be named: the default detail shape and attachments(*) do not carry it. The key is absent rather than null for a link, an empty scan, or a document not yet extracted.

  • Vehicle company counts (Tango API 5.8.0). Vehicle gains holder_count (distinct companies holding one of the vehicle's IDVs) and order_winner_count (distinct companies that have won a task order under it), and both join the VEHICLES_MINIMAL and VEHICLES_COMPREHENSIVE defaults next to awardee_count, so listVehicles() and getVehicle() return them without a custom shape. Neither is orderable or filterable.
  • Boards-of-contract-appeals decisions (Tango API 4.26.0). listContractAppeals(options) and getContractAppeal(uuid, options) over /api/contract_appeals/, with every filter the API accepts declared as a typed option on ListContractAppealsOptions (search, board, docket, appellant, judge, decision_type, the decision_date_after / _before pair, listed, document_id, ordering), the new ContractAppealRecord return type, and a registered ContractAppeal shape schema so the typed shape API resolves the resource's fields.

    These are Contract Disputes Act decisions from the CBCA (civilian) and the ASBCA (defense) — a dispute under an existing contract, not a challenge to an award. Bid protests remain the separate listProtests() resource, and the two do not overlap.

    Two properties are documented on the record type and in docs/API_REFERENCE.md. An unshaped list returns only a core subset of the decision, so every property on ContractAppealRecord is optional and anything past the subset has to be named in a shape. And decision_text is Enterprise-only, with the key absent rather than null below that tier — a caller checks for presence, not for a nullish value.

  • attachments(extracted_text) — SLED document bodies on the Small plan and above (Tango API 4.25.1; parity with tango-python). The leaf joins SledAttachmentPayload and the explicit shape schema, and the contract was re-vendored so it validates instead of being rejected client-side. Three properties are documented on the interface and in docs/API_REFERENCE.md: the leaf must be named (neither ShapeConfig default includes it, and attachments(*) does not carry it, because the API only resolves the body for a caller who asked); the key is absent rather than null when the text is not being served; and a contested document never returns text at any plan. Searching document text stays ungated on every plan and returns no fragment of it.
  • State, local and education (SLED) procurement support (Tango API 4.25.0; parity with tango-python). Six methods over the new /api/sled/ namespace: listSledOpportunities/getSledOpportunity, listSledOpportunityRevisions, getSledCoverage, listSledForecasts/getSledForecast, plus iterateSledOpportunities / iterateSledForecasts and their IterableListMethod entries. New model interfaces SledOpportunity, SledOpportunityRevision, SledForecast and the six nested payload types; explicit shape schemas for all of them; five ShapeConfig defaults. Every one of the API's 27 solicitation filters and 13 forecast filters is a typed option.

    Four behaviors are documented on the options interfaces because each misleads a caller who assumes federal semantics. Passing neither status nor active returns open solicitations only — that default is the API's, and the SDK deliberately does not synthesize a status param, since doing so would make active: false unreachable (pinned by a test). status is Tango-derived and refreshed every fifteen minutes; the portal's own word is served as source_status, is frozen at last capture, and is not a liveness filter. Category scheme tagging is mid-migration, so naics matches only the small tagged share and category_code is the escape hatch. And meta.attachment_count can be lower than attachments.length, because an auto-generated portal cover sheet is listed and flagged is_generated_summary but excluded from the count.

    SLED_REVISIONS_MINIMAL omits changes on purpose: the per-field before/after needs a Small plan, so naming it by default would 403 a Free caller.

  • Fourteen nested sub-resource routes now mapped in the conformance gate. agencies_contracts_awarding, agencies_contracts_funding, contracts_subawards, entities_contracts, entities_idvs, entities_lcats, entities_otas, entities_otidvs, entities_subawards, idvs_awards, idvs_idvs, idvs_lcats, otidvs_awards and vehicles_orders all have SDK methods and are published by the newer contract for the first time; unmapped, each was a hard conformance error. Mapping them turns those into the honest finding, which is that most of their options interfaces accept filters through an index signature rather than declaring them.

Changed

  • Re-vendored contracts/filter_shape_contract.json for Tango API 5.11.0 and regenerated the overlay.
  • Dev-dependency security update via npm audit fix: js-yaml, brace-expansion and source-map-js move to their patched releases. The published package is unaffected; its only runtime dependency remains commander.
  • Documented that recipient_uei on listContracts() (and uei on listIdvs(), listOtas() and listOtidvs()) accepts several UEIs joined by |, up to 500 (Tango API 5.11.0); the SDK already passed the value through unchanged.
  • Re-vendored the contract for Tango API 5.9.0 (51 resources) and regenerated the overlay: 385 fields across 28 containers, 76 nested schemas. contracts/observed_shape_types.json is re-vendored from tango-python as well, so the new fields carry the types the API returns (awards is a list, awarded a boolean, data_through_period an integer) instead of types guessed from their names.
  • Re-vendored contracts/filter_shape_contract.json (schema_version 2, 48 resources) and regenerated src/shapes/generatedOverlay.ts from it — 359 fields across 25 containers, 73 nested schemas.
  • Re-vendored the contract for Tango API 5.1.0 and regenerated the overlay, which now merges a model's expand when two resources embed it instead of letting the narrower copy win.
  • Wrapping eBuy maps ebuy/requests in the conformance gate and removes it from both coverage baselines.
  • Baselined 14 reverse-shape-coverage gaps in contracts/shape_coverage_baseline.json, matching tango-python. All 14 are the nested sub-resource routes above, which reuse the parent resource's model rather than carrying one of their own; none is SLED, and none is a regression — they became visible only with the re-vendored contract.

Deprecated

  • Vehicle.awardee_count is deprecated in favor of order_winner_count, which carries the same value. The API keeps serving it as an alias until its next major version.

Fixed

  • API errors now carry the server's reason (parity with tango-python). A 403 or other non-2xx response the SDK had no dedicated error class for threw TangoAPIError("API request failed with status 403"), so a caller refused for a G2X-only shape field or a plan-gated filter couldn't tell why without digging into responseData. The message now ends with the API's own explanation (API request failed with status 403: G2X shape fields are not allowed for your account.), and the parsed body stays on responseData. Non-JSON bodies, such as a proxy's 502 page, keep the old message.
  • attachments(name,doc_role,doc_role_alt) no longer throws ShapeValidationError on getOpportunity, listOpportunities, getNotice and listNotices; the API serves both fields on the Pro plan and above when they are named. New OpportunityAttachment and AttachmentDocRole types cover the six roles and are used on Opportunity and Notice.
  • SLED solicitations accept delisted_at and meta(jurisdiction_declared), which were rejected client-side. SledOpportunity and SledMetaPayload carry the new fields, and status_reason now documents delisted.
  • ProtestRecord types agency and protester as the strings the API returns, and gains title, docket_url, decision_url, organization, dockets and decisions. The never-served docket property is deprecated in favor of dockets.
  • getProtest takes the case's case_id UUID, which is all the route accepts; a case number returns 404. The parameter is renamed caseId and the docs say how to look a case up by number, and listProtests is documented as covering GAO, COFC and SBA OHA.

Documentation

  • docs/API_REFERENCE.md covers obligations_by_fiscal_year, commercial_item_acquisition_procedures, pipe-joined UEIs, attachments(extraction_status) and countType. docs/WEBHOOKS.md notes that alerts.federal_register.match and alerts.ebuy_request.match are alertable, with query_type: "federal_register" and "ebuy_request".
  • New Federal Register section in docs/API_REFERENCE.md with both methods and the full filter table, and both new constants in the docs/SHAPES.md preset table. README.md's method list gained both methods.
  • New GSA eBuy section in docs/API_REFERENCE.md covering all four methods, the full filter table, and the data caveats (the frozen status, the empty-list-not-error scoping, the short-lived attachment URL, the named-only attachments(extracted_text)). README.md's method and error lists gained the new methods and error.
  • New Contract Appeals section in docs/API_REFERENCE.md covering both methods, the full filter table, and the two properties that catch people out (the core-subset default and the tier-gated, absent-rather-than-null decision_text). README.md's method list gained both methods.
  • New State & Local (SLED) — Beta section in docs/API_REFERENCE.md covering all six methods, both defaults that surprise people, and the new ShapeConfig constants.
  • docs/WEBHOOKS.md troubleshooting gained the date-lapse rule and its one exception. An exclusion or a DIBBS solicitation reaching its date fires nothing, because open/closed is derived at query time — but alerts.sled_opportunity.match does fire on a closing, since SLED liveness is a stored column a fifteen-minute sweep writes.

[1.3.0] - 2026-08-14

Changed

  • Node.js 20 is now the minimum supported version (engines.node >= 20); the CI matrix moves from 18/20/22 to 20/22/24. Node 18 has been end-of-life since April 2025, and the security-patched test toolchain below requires 20+. Nothing in the published code changed — existing installs on Node 18 keep working, but they are no longer tested or supported.
  • Dev-dependency security upgrade clearing all six open Dependabot alerts (vitest 2.1.9 → 4.x, @vitest/coverage-v8 to match, tsx to the esbuild-0.28 line — the published package is unaffected, its only runtime dependency remains commander). One test-only fix for vitest 4's stricter mocks: constructable mocks now use regular-function implementations.

[1.2.0] - 2026-08-14

Added

  • DIBBS, exclusions, and SBIR/STTR endpoint support (parity with tango-python v1.3.0). Six endpoint families had no SDK support at all — no models, no methods. Added listDibbsRfqs/getDibbsRfq, listDibbsRfps/getDibbsRfp, listDibbsAwards/getDibbsAward, listExclusions/getExclusion, listSbirTopics/getSbirTopic, and listSbirSolicitations/getSbirSolicitation, with every filter param in the API contract exposed as a typed option, explicit shape schemas (including the nested organization/awardee/topic/document expands), ShapeConfig defaults, and async iterators (iterateDibbsRfqs, iterateDibbsRfps, iterateDibbsAwards, iterateExclusions, iterateSbirTopics, iterateSbirSolicitations, plus the matching IterableListMethod entries for the generic iterate()). New model interfaces: DibbsRfq, DibbsRfp, DibbsAward, Exclusion, SbirTopic, SbirSolicitation.

    Two API behaviors are worth knowing. is_open (DIBBS) and is_currently_excluded (exclusions) are derived at query time, so filter with the open / active options rather than shaping on those fields. And DIBBS total_contract_price is the order total repeated on every line item — never sum it across rows; deduplicate on award + delivery-order number first.

  • Full typed filter surface on listBudgetAccounts (parity with tango-python and the API contract). ListBudgetAccountsOptions now declares every budget/accounts filter param — the exact / __gte / __lte triplet for all 26 numeric lifecycle, ratio, and trend fields (requested_ba, enacted_ba, apportioned, obligated_total, outlayed_total, unobligated_balance, the contract/assistance breakdowns, the *_pct / *_capped ratios, YoY + 5-year-CAGR trends, and actual_vs_requested_contract), plus the __in / __icontains variants of the categorical filters (federal_account_symbol, fiscal_year, agency_code, bureau_name, bea_category, subfunction_code, account_title__icontains).
  • getGsaElibraryContract(uuid, options) for /api/gsa_elibrary_contracts/{uuid}/ (parity with tango-python), with the standard shape / flat / flatLists / joiner options and the GSA_ELIBRARY_CONTRACTS_MINIMAL default shape.
  • Typed filter options that previously worked only through the index-signature escape hatch: key on listContracts / listIdvs / listOtas / listOtidvs, cage on listEntities, id on listForecasts, opportunity_id on listOpportunities, previous_uii on listItDashboard, naics_code on listProtests (sent verbatim, not remapped to naics), and has_awards on listPsc. The filter-shape conformance gate now reports zero index-signature warnings.
  • Generated shape-coverage overlay (parity with tango-python v1.4.0): src/shapes/generatedOverlay.ts, machine-generated by the new scripts/generate-shape-overlay.ts from the vendored contract plus contracts/observed_shape_types.json (live-API type observations vendored from tango-python). SchemaRegistry merges the overlay over the curated explicit schemas, so the typed shape API now accepts every field and expand the API returns — including entity relationships(type, source), previously-unmapped models (Naics, PSC, MasSin, BudgetAccount, AssistanceListing, BusinessType), and all the code/description expands that were flattened to scalars. The reverse shape-coverage gate now reports zero gaps and contracts/shape_coverage_baseline.json is empty (416 → 0).
  • Agency-filter diagnostics on PaginatedResponse (parity with tango-python v1.5.0). Every list method now surfaces the API's meta payload, plus three parsed views: agencyWarnings (human-readable notes about dropped or loosely-matched agency tokens), unresolvedAgencyTokens (tokens that matched no organization, keyed by filter name), and resolvedAgencies (the organizations each token actually resolved to — the only way to catch a token fuzzy-matching an agency you did not intend). All three are total: absent or malformed meta yields empty values, never a throw. On the PaginatedResponse type, meta and the three parsed views are declared as optional properties — responses built by the client always populate them, but existing code that constructs the type without them keeps compiling.
  • Structured shape errors on TangoValidationError (parity with tango-python's .issues / .available_fields): new issues and availableFields getters expose the API's structured 400 payload — entries like {"path": "tradeoff_process", "reason": "unknown_field"} and the endpoint's valid field set — instead of leaving callers to parse responseData by hand.
  • Vendored the canonical API filter/shape contract at contracts/filter_shape_contract.json (API 4.22.0), so conformance checking is fully offline — no token, no sibling checkout.
  • New reverse shape-coverage gate scripts/check-shape-coverage.ts (npm script check-shape-coverage): walks every resource's shape tree in the vendored contract against the SDK's explicit schema registry and fails on any field or expand the SDK does not capture, unless recorded in contracts/shape_coverage_baseline.json as tracked backlog.
  • Accepted-gaps baselines: contracts/conformance_baseline.json (missing filters + unimplemented resources) and contracts/shape_coverage_baseline.json (known shape-coverage gaps). Baselined gaps report as warnings; anything new is an error.
  • Recorded integration test layer (parity with tango-python's VCR-cassette suite): a record/replay harness (tests/integration/harness.ts) around the SDK's injectable fetchImpl, with JSON cassettes in tests/cassettes/ recorded against the live API. Default runs replay offline — a missing cassette is a hard failure so drift is loud, while an absent cassettes directory (a fork without the corpus) skips the suite with a warning. TANGO_REFRESH_CASSETTES=true re-records serially against the live API; TANGO_USE_LIVE_API=true bypasses cassettes. Cassettes never store request headers, keep only an allowlisted response-header subset, and the recorder throws rather than serialize API-key material anywhere in an interaction (asserted by unit tests in tests/unit/integration-harness.test.ts).
  • Per-resource integration tests (tests/integration/*.test.ts, 44 tests / 44 cassettes) covering contracts (including cursor pagination and shaping), entities, IDVs, vehicles, opportunities, notices, grants, forecasts, agencies + organizations, protests, budget accounts (fiscal-year range round-trip), DIBBS, exclusions, SBIR, NAICS/PSC reference data, subawards, and edge cases (404, invalid ordering, empty result page).
  • Env-gated production smoke suite (tests/production/smoke.test.ts, the node port of tango-python's tests/production/): runs only with TANGO_LIVE_TESTS=true plus TANGO_API_KEY, asserting light live-API invariants (pagination shape, shaping, rate-limit header parsing). Excluded from default runs and CI by vitest.config.ts.

Changed

  • Both conformance baselines shrank with the new resources: dibbs/*, exclusions, and sbir/* left unimplemented_resources in contracts/conformance_baseline.json, and their unmapped_resource entries left contracts/shape_coverage_baseline.json (422 → 416 known gaps, then 416 → 0 with the generated overlay above).
  • scripts/check-filter-shape-conformance.ts now defaults to the vendored contract instead of a checked-out tango API repo (TANGO_CONTRACT_PATH or --manifest still point it at one), covers every resource in the 4.22.0 contract in its resource map, and treats an unimplemented resource as an error unless baselined.
  • Removed the dead legacy .eslintrc.cjs — the flat eslint.config.js has been the operative ESLint config since the flat-config migration, and the leftover file only invited divergent edits.

Fixed

  • The six new list methods (listDibbsRfqs, listDibbsRfps, listDibbsAwards, listExclusions, listSbirTopics, listSbirSolicitations) leaked a caller-supplied joiner to the server as a bare query param and ignored it when unflattening flat: true responses (always unflattening on the default .). joiner is now threaded the same way as listIdvs: sent only alongside flat=true, and used as the unflatten separator.
  • listBudgetAccounts: the fiscal_year_gte, fiscal_year_lte, and account_title options were sent verbatim, which the API silently ignores. They are kept as legacy aliases and now remapped to the forms the API understands (fiscal_year__gte, fiscal_year__lte, account_title__icontains); an explicitly passed dunder param wins over its alias.
  • Docs: removed the stale getIdvSummary / listIdvSummaryAwards sections from README.md and docs/API_REFERENCE.md — those methods were removed from the SDK in 1.1.0. Documented the full new surface (DIBBS/exclusions/SBIR, budget accounts and their filter surface, getGsaElibraryContract, the newly typed filters, PaginatedResponse meta diagnostics, structured TangoValidationError details), completed the ShapeConfig preset table in docs/SHAPES.md, and rewrote the maintainer half of docs/DEVELOPERS.md around the conformance gates and the cassette record/replay workflow (the old text still claimed the SDK had no cassette mechanism).

CI

  • package-lock.json is now committed, and the CI + publish workflows install with npm ci --ignore-scripts instead of npm install — installs are reproducible from the lockfile instead of re-resolving dependency ranges on every run.
  • The test job's Node 20 leg runs the suite once with --coverage (instead of a second full pass), the default npx vitest run now includes the integration suite replayed offline from the committed cassettes, and both setup-node steps cache the npm store off the committed lockfile. No coverage fail-under gate, matching tango-python.
  • The conformance job is now a hard gate that runs both conformance directions offline against the vendored contract on every PR — it no longer needs TANGO_API_REPO_ACCESS_TOKEN and no longer skips silently without it. When the token is configured, both checks additionally run as hard gates against the fresh contract at makegov/tango HEAD, with a re-vendor warning when the vendored copy has drifted.
  • The conformance job also regenerates src/shapes/generatedOverlay.ts and fails on any diff, so a contract or curated-schema change that alters generator output can't land without a regenerated overlay. scripts/generate-shape-overlay.ts honors the same TANGO_CONTRACT_PATH / --contract override as the two check scripts.

[1.1.0] - 2026-05-29

Changed (breaking)

  • Removed getIdvSummary and listIdvSummaryAwards. These called /api/idvs/{id}/summary/ and /api/idvs/{id}/summary/awards/, which have never existed in the Tango API (no OpenAPI backing), so no consumer could have been using them successfully. Use getIdv + listIdvAwards instead.

Fixed

  • Contract interface: removed dead fields (id, award_id, recipient_name, award_amount, awarding_agency, funding_agency) and added the real API fields from ContractListSerializer (key, piid, obligated, total_contract_value, base_and_exercised_options_value, awarding_office, funding_office, naics_code, psc_code, set_aside, solicitation_identifier, parent_award, legislative_mandates, subawards_summary, place_of_performance). All fields optional (the endpoint is shape-on-demand). The deprecated fields remain declared (marked @deprecated) for one minor cycle and will be removed in 2.0.0. New exported types: OrganizationOfficePayload, PlaceOfPerformance, SubawardsSummary, LegislativeMandates, ParentAwardReference, EntityBasic.
  • listContracts: no longer sends page=1 to the cursor-only /api/contracts/ endpoint. When no cursor is supplied, neither page nor cursor is sent and the API returns the first page by default. The stale code comment claiming page-based pagination support has been corrected.
  • Shape validation: registered the ContractOrIDVCompetition nested schema (alias of Competition) so nested selections like competition(extent_competed,number_of_offers_received) on contract / IDV shapes validate instead of raising a shape-validation error.

Added

  • Budget accounts surface (tango v4.6.8): listBudgetAccounts, getBudgetAccount, getBudgetAccountQuarters, getBudgetAccountRecipients. New exported BudgetAccount interface and ListBudgetAccountsOptions.
  • Singleton detail GETs: getContract, getContractSubawards, getContractTransactions, getForecast, getGrant, getNotice, getOpportunity, getSubaward.
  • getEntityBudgetFlows(uei) for /api/entities/{uei}/budget-flows/.
  • listVehicleOrders(uuid, options) for /api/vehicles/{uuid}/orders/ (parity with Python).
  • grantId filter on listGrants (camelCase alias mapped to the grant_id API param; grant_id also accepted directly).

CI

  • Added ci.yml PR + push-to-main gate (lint, typecheck, build, test on Node 18/20/22). The filter/shape conformance check is a separate job that skips cleanly until a TANGO_API_REPO_ACCESS_TOKEN secret for the private manifest repo is configured, at which point it becomes a hard gate.
  • Gave the webhooks real-HTTP-server round-trip tests an explicit 20s timeout (the default 5s was tight on the slower Node 18 CI runtime).

[1.0.0] - 2026-05-13

First stable release. tango-node is now at full feature parity with both the Tango API and tango-python for the surface that remains after the subject-based webhook removal (see "Removed" below). Every read method and every endpoint/alert/signing helper available on tango_python.TangoClient has an idiomatic camelCase counterpart on TangoClient, the SDK's docs are auto-published to docs.makegov.com/sdks/node/ via the composer pipeline (makegov/docs#15 / makegov/docs#16), and from 1.x on we'll only ship breaking changes on a major bump.

Changed (breaking)

  • createWebhookEndpoint({ name, ... }) — name is now required. Previously the SDK silently fell back to the callback URL's host when name was omitted, which masked the server's unique(user, name) constraint until the second duplicate endpoint. Raising client-side gives a clearer error and matches tango-python 1.0.0's behavior.
  • createWebhookAlert({ filters, ... }) — filters is now validated as a non-empty plain object. Previously {} and arrays passed the check; the error message claimed "non-empty object" but didn't enforce it. Matches the server-side validation.

Fixed

  • tests/unit/client.iterate.test.ts — corrected the comment above the first page assertion; previous text claimed the first call should NOT carry a page, but the assertion (correctly) expects page=1 since listContracts defaults to it.
  • docs/DEVELOPERS.md — listContracts({ offset: 25 }) example replaced with { page: 2 } and "manual offset tracking" → "manual page/cursor tracking" (the method has never accepted offset).
  • CHANGELOG.md — corrected "4 new unit test files" to "5"; the parenthesized list always contained 5 paths.
  • Lint cleanup ahead of the npm publish — 44 redundant as AnyRecord / as <T> type-assertion casts dropped across src/ (@typescript-eslint/no-unnecessary-type-assertion fires under the newer plugin minor that CI resolves). src/webhooks/receiver.ts: dropped the unused AddressInfo import, simplified Delivery.bodyJson: unknown | null → unknown (the latter already includes null), and restructured WebhookReceiver.run() to avoid const receiver = this (replaced with arrow-function closures over getUrl/getDeliveries/stop). No behavior change — tests still pass 220/220.
  • eslint.config.js — disabled the core no-undef rule for TS files. TypeScript itself does undefined-symbol checking with knowledge of TS-only types (AsyncDisposable, Disposable, etc.); the core rule double-fires and false-flags those. Matches the typescript-eslint upstream guidance.

Internal

  • Pinned devDependencies to exact versions (dropped ^ from package.json). The previous unpinned ranges + gitignored package-lock.json meant CI re-resolved deps on every run and could pick up minor versions with stricter behavior that local installs hadn't seen yet — that's how the lint mismatch above slipped past local checks.

Docs

  • README updated for the docs-review sweep:
    • Added TangoTimeoutError to the documented error class list (it has been exported from src/errors.ts since v0.4 but the README omitted it).
    • Replaced the "(Coming Soon!)" marker on the docs link with the live https://docs.makegov.com/sdks/node/ URL.
    • Rewrote the "Comprehensive API Coverage" feature bullet — the old enumeration listed fewer than half of the actually-implemented domains. New bullet points at the canonical "API Methods" section for the full surface.
  • New docs/CLIENT.md — TangoClient constructor reference, environment variables, full retry/backoff semantics (including Retry-After handling), error-handling patterns, fetchImpl injection, and staging/local targeting. Ported from docs.makegov.com/sdks/node/client.md ahead of the docs-site auto-pull cutover (makegov/docs#15 / makegov/docs#16).
  • docs/API_REFERENCE.md enriched with notes from the docs-site methods.md that hadn't been folded in yet: listContracts page/cursor mutual exclusion, getIdvSummary / listIdvSummaryAwards deprecation (server returns 404), listIdvLcats clarification, listOrganizations level semantics, createWebhookEndpoint snake_case canonical vs camelCase legacy aliases (name is required either way per the 1.0.0 change above), testWebhookEndpoint post-#2252 cleanup ({ endpoint: <id> } is canonical), and createWebhookAlert field-rename notes (name vs subscription_name, filters vs filter_definition, singular query_type, update-writable field list).

CI

  • New .github/workflows/docs-dispatch.yml — fires on push to main when docs/**, README.md, or CHANGELOG.md changes and dispatches external_updated at makegov/docs so the public docs site rebuilds with the latest SDK content. Required for the makegov/docs#15 auto-pull pipeline.

Parity closure — all previously-tracked gaps addressed

Every gap surfaced in the May 2026 parity audit is now closed:

Typed filter Options interfaces

  • listForecasts, listOpportunities, listNotices, listGrants — previously ListOptionsBase & Record<string, unknown> with zero typed filters; now ship full Options interfaces (ListForecastsOptions, ListOpportunitiesOptions, ListNoticesOptions, ListGrantsOptions) enumerating every filter kwarg from the Python signatures. ListNoticesOptions deliberately omits ordering (server rejects it).
  • ListContractsOptions expanded to enumerate all 27+ Python kwargs (award_date*, awarding_agency, funding_agency, obligated_gte/lte, pop_*, expiring_*, keyword/recipient_name/recipient_uei/set_aside_type/naics_code/psc_code aliases, sort+order→ordering, etc.).
  • ListEntitiesOptions expanded with the 12 Python kwargs (cage_code, naics, name, psc, purpose_of_registration_code, socioeconomic, state, total_awards_obligated_gte/lte, uei, zip_code).
  • ListVehiclesOptions expanded with all 21 filter kwargs (vehicle_type, type_of_idc, contract_type, who_can_use, total_obligated_min/max, etc.).
  • ListIdvsOptions expanded with the full IDV filter surface.
  • ListOtasOptions / ListOtidvsOptions expanded with the missing _gte/_lte ranges (award_date_gte/lte, fiscal_year_gte/lte, expiring_gte/lte, pop_start_date_gte/lte, pop_end_date_gte/lte).
  • ListAgenciesOptions added (was inline { page?, limit? }).

All Options interfaces keep a [key: string]: unknown index signature for forward-compatibility with new server-side filters that haven't been ported yet — typed fields give autocomplete and typo-protection on known filters; unknown fields still pass through.

ShapeConfig preset parity

Added: PROTESTS_MINIMAL, OTAS_MINIMAL, OTIDVS_MINIMAL, SUBAWARDS_MINIMAL, GSA_ELIBRARY_CONTRACTS_MINIMAL, ORGANIZATIONS_MINIMAL, VEHICLE_ORDERS_MINIMAL, ITDASHBOARD_INVESTMENTS_MINIMAL, ITDASHBOARD_INVESTMENTS_COMPREHENSIVE.

Updated to match Python field lists: ENTITIES_COMPREHENSIVE (now uses federal_obligations(*) expansion), VEHICLES_MINIMAL (extended to mirror Python's larger field list), VEHICLES_COMPREHENSIVE (dropped competition_details(*) per SDK v0.6.0; added program_acronym, is_synthetic_solicitation, metrics(*), organization expansion).

Explicit schemas

Added 11 schemas + registry entries: ORGANIZATION_OFFICE_SCHEMA, VEHICLE_METRICS_SCHEMA, ORGANIZATION_SCHEMA, OTA_SCHEMA, OTIDV_SCHEMA, SUBAWARD_SCHEMA, PROTEST_DOCKET_SCHEMA, PROTEST_SCHEMA, GSA_ELIBRARY_IDV_REF_SCHEMA, GSA_ELIBRARY_CONTRACT_SCHEMA, ITDASHBOARD_INVESTMENT_SCHEMA. Wired into the EXPLICIT_SCHEMAS registry under canonical model names.

Also extended VEHICLE_SCHEMA with the fields the new VEHICLES_* presets reference: is_synthetic_solicitation, program_acronym, organization (expandable to OrganizationOffice), metrics (expandable to VehicleMetrics), idv_count, total_obligated, latest_award_date, opportunity_id, description.

Typed return models

  • client.resolve(input) → Promise<ResolveResult> with typed ResolveCandidate[] (was Promise<{ candidates: AnyRecord[]; count: number }>).
  • client.validate(input) → Promise<ValidateResult> (was Promise<AnyRecord>).
  • client.getAgency(code) → Promise<AgencyRecord> (was Promise<AnyRecord>).
  • client.getProtest(caseNumber) → Promise<ProtestRecord> with typed docket, resolved_*, etc.

All new types exported from package root.

Observability — rateLimitInfo + lastResponseHeaders

Two new instance properties on TangoClient mirroring Python's rate_limit_info / last_response_headers:

await client.listContracts({ limit: 5 });
console.log(client.rateLimitInfo);
// { remaining: 98, limit: 100, resetIn: 60, retryAfter: null, limitType: "per_minute" }
console.log(client.lastResponseHeaders?.["x-request-id"]);

Both null until the first request completes; populated after every successful request. HttpClient parses X-RateLimit-{Remaining,Limit,Reset,Type} + Retry-After headers into a RateLimitInfo snapshot.

listContracts cursor pagination (non-breaking)

ListContractsOptions now accepts cursor alongside page. When cursor is supplied, the request omits page and uses keyset pagination (Python parity); otherwise falls back to page-based. PaginatedResponse gained a cursor field auto-extracted from next so callers can client.listContracts({ cursor: resp.cursor }) for the next page without parsing the URL themselves.

WebhookReceiver framework

New src/webhooks/receiver.ts. WebhookReceiver dataclass-style class with start(), stop(), url, deliveries, onDelivery callback, optional forwardTo mirror, history cap, signature verification (via existing verifySignature). Two run patterns shipped:

  • await using rx = await new WebhookReceiver(opts).run(); (modern, Symbol.asyncDispose).
  • await WebhookReceiver.withRunning(opts, async (rx) => { ... }); (portable callback scope).

Pure node:http + native fetch — no new dependencies.

Webhook simulator

New src/webhooks/simulate.ts. sign(payload, secret) returns a SignedRequest (body bytes, signature header value, content-type). deliver({ targetUrl, payload, secret, ... }) signs and POSTs via native fetch with AbortSignal.timeout(). Includes a stableStringify helper that matches Python's json.dumps(sort_keys=True, separators=(",", ":")) byte-for-byte so signatures are reproducible across languages.

Webhook CLI — tango-node webhooks

New bin/tango-node (entry in src/bin/tango-node.ts) backed by commander. Subcommands: listen, simulate, trigger, fetch-sample, list-event-types, endpoints {list, get, create, delete} — mirroring the Python tango webhooks CLI. New runtime dep: commander@^12.1.0.

Conformance gate

New scripts/check-filter-shape-conformance.ts + npm run check-conformance script. Walks src/client.ts with the TypeScript compiler AST, extracts each list* method's Options interface, and validates against the canonical manifest at tango/contracts/filter_shape_contract.json. JSON output + exit codes match the Python conformance script. Current state: 0 errors, 0 warnings — parity verified.

Test coverage

Net +74 tests across the new work (220 total now passing, up from 146 pre-audit):

  • ShapeConfig preset parity (config.shapes.parity)
  • Explicit schema parity (shapes.schema.parity, 12 tests)
  • WebhookReceiver lifecycle, signature paths, forwarding, history cap, withRunning + Symbol.asyncDispose (webhooks/receiver, 21 tests)
  • Webhook simulator stable-stringify, sign-verify round-trip, deliver against a real http.createServer, timeout (webhooks/simulate, 17 tests)
  • CLI subcommand wiring (webhooks/cli, 7 tests)
  • Conformance script (scripts/conformance, 5 tests)
  • Observability + cursor pagination + typed return models (client.observability, 11 tests)

Internal

  • tsx added as a devDependency to run the new conformance script.
  • HttpClient constructor body unchanged; just adds two readonly fields (lastResponseHeaders, rateLimitInfo) populated on every successful response.

Removed

  • Subject-based webhook subscriptions are gone. The Tango API is dropping the /api/webhooks/subscriptions/ surface for subject delivery (see makegov/tango#2267); tango-node mirrors that here. Removed methods: listWebhookSubscriptions, getWebhookSubscription, createWebhookSubscription, updateWebhookSubscription, deleteWebhookSubscription. Removed types: WebhookSubscription, WebhookSubscriptionCreateInput, WebhookSubscriptionUpdateInput, WebhookSubscriptionPayload, WebhookSubscriptionPayloadRecord, WebhookSubjectTypeDefinition, WebhookSampleSubject, ListWebhookSubscriptionsOptions. WebhookEventTypesResponse no longer carries subject_types / subject_type_definitions; WebhookEventType no longer carries default_subject_type; sample-payload responses no longer carry sample_subjects / sample_subscription_requests. Use createWebhookAlert (filter-based delivery via /api/webhooks/alerts/) — that's the only remaining subscription path.

SemVer-major (0.3.0 → 0.4.0).

Added

API parity — read methods

  • Lookups: listNaics, getNaics, listPsc, getPsc, listMasSins, getMasSin, listAssistanceListings, getAssistanceListing, listOrganizations, getOrganization, listOffices, getOffice, listDepartments (@deprecated JSDoc), getDepartment, getBusinessType.
  • Awards completeness: listOtas, getOta, listOtidvs, getOtidv, listOtidvAwards, listSubawards, listGsaElibraryContracts, listLcats (accepts { uei } or { idvKey }).
  • Other resources: listProtests, getProtest, listItDashboard, getItDashboard, listMetrics (parameterized over ownerType since the API exposes metrics only under owner-scoped paths).
  • Utility endpoints: resolve(input) (POST /api/resolve/ — returns { candidates, count }), validate(input) (POST /api/validate/).

API parity — typed wrappers for Python's get_*_metrics helpers

  • getEntityMetrics(uei, months, periodGrouping)
  • getNaicsMetrics(code, months, periodGrouping)
  • getPscMetrics(code, months, periodGrouping)

API parity — entity, IDV, and agency sub-resources

  • listEntityContracts, listEntityIdvs, listEntityOtas, listEntityOtidvs, listEntitySubawards, listEntityLcats
  • listIdvLcats(key, options?) — typed sibling of the generic listLcats({ idvKey })
  • listAgencyAwardingContracts, listAgencyFundingContracts

Webhook write API

  • Endpoints: createWebhookEndpoint (now name is first-class; defaults to URL host if omitted), updateWebhookEndpoint, deleteWebhookEndpoint. testWebhookEndpoint(endpointId) is the canonical method; testWebhookDelivery is kept as an auto-resolving variant (omit endpointId to let the API pick the sole endpoint).
  • Alerts (filter-subscription API): listWebhookAlerts, getWebhookAlert, createWebhookAlert, updateWebhookAlert, deleteWebhookAlert. WebhookAlertCreateInput now has an optional endpoint field — required for multi-endpoint accounts, optional for single-endpoint accounts (the API auto-resolves). Server support landed in makegov/tango#2256.

New typed input interfaces exported from the package root: WebhookEndpointCreateInput, WebhookEndpointUpdateInput, WebhookAlertCreateInput, WebhookAlert, plus options types for the new sub-resources.

Webhook signature helpers (parity with tango_python.webhooks.signing)

  • verifySignature(body, header, secret) — constant-time HMAC-SHA256 verification. Accepts "sha256=<hex>" and bare-hex forms. Returns boolean, never throws.
  • generateSignature(body, secret) — emits "sha256=<hex>" matching the dispatcher format.
  • parseSignatureHeader(header) — returns { algorithm, signature } | null for cleaner branching in receivers.

All exported from the package root; receivers don't need to instantiate TangoClient.

Async iterator pagination

For convenience, list methods now have async-iterator wrappers that handle next / cursor for you:

for await (const contract of client.iterateContracts({ awarding_agency: "9700" })) {
  console.log(contract.piid, contract.total_contract_value);
}

Typed iterators: iterateContracts, iterateEntities, iterateOpportunities, iterateNotices, iterateGrants, iterateForecasts, iterateIdvs, iterateVehicles. Iteration is sequential (no concurrent requests) to respect API rate limits.

Retry with exponential backoff

HttpClient now automatically retries failed requests:

  • Retries on 5xx, 408 (Request Timeout), 429 (Too Many Requests), network errors, and client-side timeouts.
  • Does not retry on other 4xx — those surface as the appropriate Tango* error immediately.
  • Exponential backoff: base retryBackoffMs (default 250ms), doubled per attempt, capped at 10s.
  • Honors Retry-After headers (delta-seconds and HTTP-date) on 429/503.

Constructor surface

  • retries (default 3) and retryBackoffMs (default 250) options on TangoClientOptions. Set retries: 0 to disable.
  • timeout accepted as a shorthand alias for timeoutMs (both in ms; timeoutMs wins if both are supplied).

Environment variable fallback

  • TANGO_BASE_URL env var is now read when baseUrl is not passed to the constructor — parity with TANGO_API_KEY.

Misc

  • searchOpportunityAttachments, getVersion, listApiKeys round out parity with the Python SDK's introspection / search surface.
  • Shape generator now accepts naics(code,description) / psc(code,description) as canonical expands on Contract, Opportunity, Notice, Forecast, and Vehicle (IDV already had them). Mirrors makegov/tango#2259. (refs makegov/tango#2265)

Changed

  • createWebhookEndpoint and related write methods accept the canonical Tango API payload shape in addition to the previous camelCase wrappers — see the new typed input interfaces.
  • testWebhookEndpoint / testWebhookDelivery now send the canonical { endpoint } body key instead of the deprecated { endpoint_id } (server still accepts both as aliases). Tracks makegov/tango#2252.
  • ListSubawardsOptions.ordering narrowed from string to the literal union "last_modified_date" | "-last_modified_date", matching the server-side enum (no other values are accepted; others 400). Tracks makegov/tango#2254.
  • Shape generator rewrites legacy naics_code(...) / psc_code(...) expand spellings to canonical naics(...) / psc(...) before validation, matching the server's _EXPAND_ALIASES map. Scalar naics_code / psc_code (no parens) is untouched and still returns the raw column value. (refs makegov/tango#2265, makegov/tango#2259)

Fixed

  • ShapeConfig.IDVS_COMPREHENSIVE no longer includes base_and_exercised_options_value, which is not a valid IDV shape field — the API was returning 400 Invalid shape on this preset. Now aligned with tango_python.IDVS_COMPREHENSIVE. Also reconciled recipient.cage_code → recipient.cage to match the Python preset exactly.
  • createWebhookAlert now plumbs an explicit endpoint UUID through to the API. Multi-endpoint accounts can now create alerts directly instead of relying on the server's single-endpoint auto-resolution. Tracks makegov/tango#2256.
  • Subaward schema matches the server's SubawardSerializer. The previous SUBAWARD_SCHEMA (ported from the broken Python schema) declared two fields the server has never exposed (id, amount) and was missing every real field — including piid, key, awarding_office / funding_office / place_of_performance / subaward_details / fsrs_details / highly_compensated_officers / usaspending_permalink, and the denormalized prime_awardee_* / recipient_* lookup columns. Shape strings that referenced any real field (e.g. shape: "piid") would fail client-side validation with unknown_field. SUBAWARD_SCHEMA is now derived directly from awards.serializers.subawards.SubawardSerializer and the resource's runtime available_fields. New nested schemas SubawardDetails, FsrsDetails, SubawardPlaceOfPerformance, and HighlyCompensatedOfficer are registered so the corresponding shape expansions validate end-to-end.

Internal

  • Live smoke harnesses at scripts/smoke-{reads,writes,extras,parity}.ts exercise every new method against a running Tango instance. All four require TANGO_API_KEY in the environment (hard-fail if unset — no fallback).
  • 5 new unit test files (tests/unit/{client.parity,client.iterate,client.baseurl,webhooks.signing,config.shapes}.test.ts) added; total suite is now 16 files / 111 tests / 82% line coverage.
  • ESM build (tsc -p tsconfig.json) clean.

[0.3.0] - 2026-02-09

Added

  • Vehicles endpoints: listVehicles, getVehicle, and listVehicleAwardees (supports shaping + flattening). (refs makegov/tango#1327)
  • IDV endpoints: listIdvs, getIdv, listIdvAwards, listIdvChildIdvs, listIdvTransactions, getIdvSummary, listIdvSummaryAwards. (refs makegov/tango#1327)
  • Webhooks v2 client support: event type discovery, subscription CRUD, endpoint management, test delivery, and sample payload helpers. (refs makegov/tango#1275)

Changed

  • HTTP client now supports PATCH/PUT/DELETE for non-GET endpoints.
  • joiner is now respected when unflattening flat=true responses on supported endpoints.

[0.1.0] - 2025-11-21

  • Initial Node.js port of the Tango Python SDK.
  • Basic project scaffolding for client, models, and shapes.
  • ESM + TypeScript build configuration.

[0.1.4] - 2025-11-21

  • Added tests and cleaned up formatting and structure of SDK.