API TraderAPI QuantAPI Developer

The loan books of the finance companies behind General Motors, Ford, Toyota, Honda, Caterpillar, Deere, PACCAR and CNH, from the 10-Q and 10-K each finance arm files with the SEC in its own name because its bonds are registered there.

The parent folds its finance arm into one segment line. The arm's own filing itemises the book: receivables 30 and 60 days past due, write-offs and recoveries, the provision, how much new lending it bought in the quarter, and the vehicles and equipment it owns on lease. That is where a carmaker's or an equipment maker's credit cycle shows first, in public, alongside the parent's own quarterly report.

Each arm maps to its listed parent, so a request for GM returns GM Financial's book.

Available Data Points:

• Period Date: The period the value describes — what the number is about (the valid clock).
• Published At: When the value first became knowable — when the publisher released it (the knowledge clock). Filter on this for anything where look-ahead bias would matter.
• Value: The numeric value, where the series has one.
• Value Text: The textual value, for categorical series such as a trial's status or phase.
• Unit: Unit of the value, e.g. vehicles, percent, USD.
• Value Type: number, percent, currency, count or text.
• Frequency: How often the publisher releases the series.
• Market: The market the reading describes — an ISO-3166 alpha-2 code (DE), a sub-national one (US-CA), a supranational aggregate (EA, EU) or GLOBAL.
• Series Slug: Which series the reading belongs to. Unique within a publisher, not globally.
• Series Name: Human-readable name of the series.
• Source Slug: Publisher/feed identifier, e.g. kba_registrations.
• Source Name: Human-readable name of the publisher or feed.
• Publisher: Who publishes the underlying data.
• Entity Ref: The publisher's own identifier for what the reading is about — a manufacturer name, a securitisation trust, a reactor unit, a country code. Kept so any value can be traced back to the row it was parsed from.

Coverage

Eight arms, quarterly, published with each arm's 10-Q or 10-K. Series appear only where the arm tags them in XBRL: John Deere Capital publishes lease figures but no credit figures that can be read without guessing.

Delinquency comes from each arm's own past-due table and covers the part of the book that table itemises - GM Financial's retail book, Ford Credit's consumer book, Cat Financial's customer and purchased receivables - which every row states in its text.

What to look for

Compare an arm with its own history, not with the others. Each measures its buckets over a different part of its book, and Ford Credit, Cat Financial and CNH start the first bucket at 31 days rather than 30.

Delinquency leads charge-offs by two to three quarters. A rising delinquency_rate_60_plus is the early warning; net_charge_offs confirms it.

Flows are served per fiscal quarter. Where an arm reports only year-to-date figures ORTEX takes the difference between filings, and says so in the row's text; do not difference them again.

Two dates on every reading, and the difference is the edge

periodDate is what the number is about. publishedAt is when it first became knowable. The gap between them is the whole point of alternative data — and it is also the trap. A Form 10-D describing July is filed in mid-August, so a backtest that treats the period as the knowledge date reads a document six weeks before it existed.

from_date and to_date filter on periodDate, because that is the axis you plot against. Join on publishedAt when you are joining against returns.

Filtering: one market or all of them

Called with no filters, the endpoint returns every series in the dataset, for every market ORTEX covers it in. Each row names its own market, seriesSlug and sourceSlug, so a single request is enough to chart the whole dataset.

Narrow it with any combination of market (one market), series (one measure) and source (one publisher). Filter values that are each valid but select nothing together return 400 invalidSelection rather than a misleading empty result.

Raw readings here; comparable ones next door

This endpoint serves the publisher's numbers. Raw values are frequently not comparable — receivables of $10.9bn against $4.9bn say nothing without each book's size, and a 5.3% charge-off rate means something different on a subprime book than a prime one. The Alt Data signals endpoint serves the same series as percentiles and z-scores against a stated comparison set, which is the form a screen or a backtest wants.

Why a company you expect may be missing

Three reasons, and none of them is a bug:

• The dataset is a window, not a census: Several of these publishers release a rolling window rather than a complete history.
• The filer is not the listed company: Registers name a marque, a charter or a trust. ORTEX maps those to the listed parent where the link is defensible and leaves them unmapped where it is not — a wrong mapping silently attributes another company's data to your ticker.
• The population is genuinely narrow: Not every listed company appears in every register, and no amount of mapping changes that.

How much history there is

Several of these publishers overwrite their own pages and keep no archive. Where that is so, the series begins on the day ORTEX started capturing it and lengthens from there — nobody, including the publisher, can supply the days before that. Everything ORTEX has ever fetched is archived on capture, so the series only ever grows.

Try it out! You can test the API with the trial key TEST. Simply include it in your request headers; either here, or add the header "Ortex-Api-Key": "TEST" to your http request.

Trial key restrictions: Trial keys may be limited to a specific date range and set of regions. Requests outside the allowed regions or entirely outside the allowed date range are rejected; a date window that partially overlaps the allowed range is trimmed to it, reported in meta.restriction.

Get full access! Get a key at app.ortex.com/apis