Annuaire des autorités compétentes — Convention Apostille de La Haye

Sources

1. Partner Portal · priority 70

   Regions: brussels, flemish, walloon

   Kind: varies-per-partner

   Primary actor: agent

   Agent does: Fetch the HCCH status table, look up the origin country, and check both party-status and entry-into-force date relative to the document's issue date. Report the binary routing decision (apostille route vs consular-legalisation route) to the customer in plain English.

   You do: Confirm the country of origin and the document's issue date.

   To resume: Agent records the outcome and proceeds to the correct route.

   Try this

   Notes: Probed 2026-05-12: HCCH status table returns HTTP 200 with full 129-party listing. Per spec §6.12.3 partner-portal class — partner declares its own success signals. OVERLAP: id is also expected from the apostille walk; shared id triggers deduplication at consolidation. Pre-accession case (Senegal pre-23-March-2023, per parent skill stub) is the critical edge — the agent MUST check the EIF date for the customer's country, not just party-status today.

2. Partner Portal · priority 60

   Regions: federal

   Kind: static-listing-page

   Primary actor: agent

   Agent does: Fetch the HCCH authorities list and resolve the user's document country of origin to the designated Competent Authority. Quote back the authority's name and contact link in plain language.

   You do: Provide the country in which the public document was issued.

   To resume: Agent presents the foreign authority's contact route and explains that the apostille is obtained in the issuing country, not in Belgium.

   Try this

   Notes: Probed 2026-05-12: HTTP 200, page lists 159+ contracting parties with per-country detail-page links matching the expected static-listing template. HCCH publishes this as authoritative — Article 6 designations are deposited with the depositary. No interactive search; agent fetches and resolves locally.

3. Federal authenticated portal · priority 50

   Regions: federal

   Kind: deeplink-info-page

   Primary actor: user

   Handoff: full-takeover

   Agent does: Provide the FPS Foreign Affairs page URL describing the apostille convention scope, the contracting-parties table, and the elegalisation portal for Belgian-side processing. Explain that for foreign documents the apostille is obtained in the issuing country, and Belgium's role is to accept the apostilled document at the commune or consular post.

   You do: Read the FPS Foreign Affairs page to confirm the apostille route applies to the specific document type and country of origin, then follow the per-country authority identified via the HCCH lookup.

   To resume: User returns with the apostilled document in hand; the agent resumes the parent skill (nationality, visa, marriage) and helps with translation and commune submission.

   The steps after authentication / handoff are described from documentation, not yet confirmed by a real Be Civic user. If reality differs, please tell us so we can fix the entry.

   Try this

   Notes: Probed 2026-05-12: HTTP 200, page confirms scope covers both Belgian-outbound and foreign-inbound documents; explicitly references elegalisation.diplomatie.be for the Belgian-side flow. Quoted: 'A legalisation allows a Belgian document to be used abroad or a foreign document to be used in Belgium.' Source class federal-auth-handoff is the right shape: agent points the user at the info page, user takes over reading and acting.

4. Federal anonymous form · priority 50

   Regions: brussels, flemish, walloon

   Kind: agent-walks-user-through-form

   Primary actor: agent

   Agent does: Cross-reference HCCH party-status with DFAT's canonical guidance page. If HCCH is unavailable, this DFAT page provides the same routing decision via prose.

   You do: Confirm the country of origin.

   To resume: Agent records and continues.

   Try this

   Notes: Probed 2026-05-12: HTTPS GET on diplomatie.belgium.be/fr/legalisation-de-documents returns HTTP 200. The page is a federal canonical informational surface — not strictly a form, but classified as federal-anonymous-form per §6.12.3 since it's a federal page with no auth and the agent walks the customer through reading it. Approximate fit (no better source_class for static federal informational pages in the V0 9-enum).

5. Fallback sources
6. Offline commune visitfallback only · priority 10

   Regions: federal

   Kind: commune-visit

   Primary actor: user

   Handoff: physical-presence

   Agent does: Explain in plain language that the apostille itself is issued by the foreign country's competent authority — not by Belgium. The Belgian FPS Foreign Affairs desk in Brussels only handles edge cases: contested apostilles, additional certifications for non-standard document formats, or legalisation routes outside the Hague Convention. Provide the address, the document list, and the expected outcome.

   You do: Travel to Brussels with the foreign document carrying its apostille (already affixed by the foreign authority) plus identity proof. The desk reviews acceptance; in the standard case no further Belgian action is required and the document goes directly to the commune.

   To resume: User reports back what FPS Foreign Affairs said. If no further action is required, the agent resumes the parent skill at the translation or commune submission step.

   The steps after authentication / handoff are described from documentation, not yet confirmed by a real Be Civic user. If reality differs, please tell us so we can fix the entry.

   Notes: Offline fallback per graceful-degradation rule. The standard Hague-Apostille flow does NOT route through the Belgian legalisation desk — the apostille is issued in the country of origin and produced directly to the Belgian commune. This offline channel is the safety net for contested or edge-case apostilles and for confused users who think Belgium issues apostilles for foreign documents. Address sourced from diplomatie.belgium.be page content.

7. Offline commune visitfallback only · priority 10

   Regions: brussels, flemish, walloon

   Kind: email

   Primary actor: user

   Handoff: physical-presence

   Agent does: If HCCH and DFAT are both unreachable, tell the customer to email or visit the SPF Affaires étrangères Legalisations desk with the country name, document type, and issue date to confirm the route.

   You do: Email or visit; receive an authoritative routing decision.

   To resume: Customer reports back which route applies.

   The steps after authentication / handoff are described from documentation, not yet confirmed by a real Be Civic user. If reality differs, please tell us so we can fix the entry.

   Notes: Offline fallback per graceful-degradation requirement and §6.12.4 physical-presence/offline invariant. Note this is the same DFAT counter as the dfat-counter-brussels-offline source — re-cited here under its precondition-check role.