France ADEME Financial Aid Records avatar

France ADEME Financial Aid Records

Pricing

from $33.50 / 1,000 funding records

Go to Apify Store
France ADEME Financial Aid Records

France ADEME Financial Aid Records

One structured fundingrecord per record from the official public source, logged-out. Public, robots-honoured.

Pricing

from $33.50 / 1,000 funding records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

🏦 France ADEME Financial Aid Records

One structured funding_record per record from the official public source, logged-out. Public, robots-honoured.

Difference: one funding_record per ADEME financial-aid award (beneficiary + SIRET, awarding body + SIRET, purpose, decision reference, amount in EUR, nature, convention/payment dates, NAF activity, department) from the official ADEME data-fair API. French text and EUR amounts are preserved verbatim.

Output is one ademe_financial_aid row per result; billing is pay-per-event, the value event being one funding record (a $0.02 start fee per run, then $0.05 per funding record). Source: data.ademe.fr.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

France ADEME Financial Aid Records sample output — a table of real funding record rows (beneficiary, beneficiary_siret, awarder_siret, reference) from run CVgAdBTZciaYgxa4R on build 0.1.10

Real rows from run CVgAdBTZciaYgxa4R on build 0.1.10 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

beneficiarybeneficiary_siretawarder_siretreferencenatureconvention_date
COMITE REGIONAL DU TOURISME DE NOUVELLE AQUITAINE828647842000163852903090045421NAD0963aide en numéraire2022-03-29
UNIVERSITE DE TECHNOLOGIE DE BELFORT-MONTBELIARD19900356700013385290309004542504D0083aide en numéraire2026-07-09
SO PROP814799805000273852903090045421PAD0113aide en numéraire2021-05-12
SYNDICAT MIXTE POUR LE SCHEMA DE COHERENCE TERRITORIALE DU GRAND DOUAI255902850000233852903090045424HFD0034aide en numéraire2024-09-11
DEPARTEMENT DE LA LOIRE-ATLANTIQUE224400028000113852903090045421PLD0069aide en numéraire2021-11-02
CLERMONT AUVERGNE METROPOLE246300701002313852903090045421RAD1519aide en numéraire2022-10-27
ADERA403280308000463852903090045424NAD0861aide en numéraire2025-10-22
CC DU VAL D AMBOISE20004306500016385290309004542266D0347aide en numéraire2022-10-26

The run finished with the status message: CAPPED: delivered 10 of 39612 available source rows (maxRecords=10) — a buyer bound, not an outage. billable=10 [requested_cap=10, delivered=10]

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. ademe_financial_aid
  • beneficiary (string/null) — e.g. COMITE REGIONAL DU TOURISME DE NOUVELLE AQUITAINE
  • beneficiary_siret (string/null) — e.g. 82864784200016
  • awarder (string/null) — e.g. ADEME
  • awarder_siret (string/null) — e.g. 38529030900454
  • purpose (string/null) — e.g. Programme d'actions dans le cadre de l'opération "En Nouvelle-Aquitaine sans ma
  • reference (string/null) — e.g. 21NAD0963
  • amount_eur (string/null) — e.g. 103050
  • nature (string/null) — e.g. aide en numéraire
  • convention_date (string/null) — e.g. 2022-03-29
  • payment_period_dates (string/null) — e.g. 2022-06-29_2024-05-30
  • payment_conditions (string/null) — e.g. Echelonné
  • eu_notification (string/null) — e.g. false
  • naf_activity (string/null) — e.g. Autres services de réservation et activités connexes
  • department (string/null) — e.g. Gironde
  • department_code (string/null) — e.g. 33
  • source (string/null) — e.g. france-ademe-financial-aid-records
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://data.ademe.fr/data-fair/api/v1/datasets/les-aides-financieres-de-l%27ade
  • observed_at (string/null) — e.g. 2026-09-17T17:22:06Z
  • terminal (string/integer/null) — null in every sample row
  • reported_total (string/integer/null) — null in every sample row
  • raw_seen (string/integer/null) — null in every sample row
  • duplicates (string/integer/null) — null in every sample row
  • unique_found (string/integer/null) — null in every sample row
  • delivered (string/integer/null) — null in every sample row
  • scope (string/integer/null) — null in every sample row
  • note (string/integer/null) — null in every sample row
  • license (string/integer/null) — null in every sample row
  • attribution (string/integer/null) — null in every sample row

What you get

One funding_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 10 × $0.05 funding_record = $0.52 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"maxRecords": 5
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05).

3. A full-size run

{
"maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $250.02 on the Free tier ($0.02 start + 5000 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run CVgAdBTZciaYgxa4R, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "ademe_financial_aid",
"beneficiary": "COMITE REGIONAL DU TOURISME DE NOUVELLE AQUITAINE",
"beneficiary_siret": "82864784200016",
"awarder": "ADEME",
"awarder_siret": "38529030900454",
"purpose": "Programme d'actions dans le cadre de l'opération \"En Nouvelle-Aquitaine sans ma voiture\"",
"reference": "21NAD0963",
"amount_eur": "103050",
"nature": "aide en numéraire",
"convention_date": "2022-03-29",
"payment_period_dates": "2022-06-29_2024-05-30",
"payment_conditions": "Echelonné",
"eu_notification": "false",
"naf_activity": "Autres services de réservation et activités connexes",
"department": "Gironde",
"department_code": "33",
"source": "france-ademe-financial-aid-records",
"release_date": null,
"source_url": "https://data.ademe.fr/data-fair/api/v1/datasets/les-aides-financieres-de-l%27ademe/lines",
"observed_at": "2026-09-17T17:22:06Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: CRAWL_DELAY=0.0.

Charging. Each funding record is charged at the moment it is pushed (funding_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

The ADEME data-fair lines endpoint is paged by its own cursor (next link), and the dataset total reconciled against delivery. French labels + EUR amounts are copied verbatim; geography is taken from the published SIRET department enrichment. Streaming, bounded to maxRecords.

Source

https://data.ademe.fr/data-fair/api/v1/datasets/les-aides-financieres-de-l'ademe/lines

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Funding Record (funding_record)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 8 funding records: $0.02 start + 8 × $0.05 = $0.42
  • 25 funding records: $0.02 start + 25 × $0.05 = $1.27
  • 5000 funding records: $0.02 start + 5000 × $0.05 = $250.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: CAPPED: delivered 10 of 39612 available source rows (maxRecords=10) — a buyer bound, not an outage. billable=10 [requested_cap=10, delivered=10]. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by data.ademe.fr. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.ademe.fr) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other public funding registries actors?
A: Same output shape and billing model; this one covers data.ademe.fr. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (CRAWL_DELAY=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • Brazil BNDES Financing Operations — One structured fundingrecord per record from the official public source, logged-out. Public, robots-honoured
  • EU FTS Beneficiary Records — EU Financial Transparency System beneficiaries: one funding record per beneficiary row from the Commission's annual FTS file — beneficiary, VAT/regis…
  • Poland EU-Funded Projects — One funding record per EU-co-financed project in Poland (2021-2027) from the official national project list — beneficiary, programme, value, EU co-fi…
  • USAspending Federal Award Watch (post-award) — POST-AWARD ONLY: awards that have already been made, as published by USAspending
  • World Bank Projects Funding Registry — One structured fundingrecord per record from the official public source, logged-out. Public, robots-honoured
  • 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.