Registry entry

Portugal Passport Request at the Rio de Janeiro Consulate (Requerimento de Passaporte)

The in-person-appointment application form ("Requerimento de Passaporte") a Portuguese citizen resident in the Rio de Janeiro consular district files with the Consulado-Geral de Portugal no Rio de Janeiro — a post of the Ministério dos Negócios Estrangeiros (MNE) — to request issuance or renewal of a Passaporte Eletrónico Português (PEP) at a scheduled consular counter appointment. Portugal's domestic passport process has no citizen-facing downloadable application form (it is an in-person biometric-enrolment appointment); this consulate-hosted intake form is a genuine, distinct, passport-specific application, unlike this registry's already-published `pt/mne/requerimento-cartao-cidadao-passaporte-consular` (a different consular post's Cartão de Cidadão-centric form that carries only a conditional passport sub-option). This document is scoped to this one consular post's own published PDF: it is a flat, single-page, self-documenting form with no fillable AcroForm layer at all (0 Widget annotations), distinct in both structure and technical shape from the São Paulo consulate's AcroForm-based sibling — see VERIFICATION.md. Several fields (CPF, CEP, Bairro) reflect this form's Brazil-specific localization and would not appear on an equivalent form published by a consulate in another country. GovSchema is independent and is not affiliated with, endorsed by, or operated by the Government of Portugal, the Ministério dos Negócios Estrangeiros, or the Consulado-Geral de Portugal no Rio de Janeiro.

Registry entry

pt/mne/requerimento-passaporte-consular

Jurisdiction
Portugal · national
Version
1.0.0
Verification
draft
Authority
Ministério dos Negócios Estrangeiros — Consulado-Geral de Portugal no Rio de Janeiro

Authoritative source Requerimento de Passaporte (Consulado-Geral de Portugal no Rio de Janeiro)

Machine access

Schema document
registry/pt/mne/requerimento-passaporte-consular/1.0.0/schema.jsonapplication/schema+json
Verification record
registry/pt/mne/requerimento-passaporte-consular/1.0.0/VERIFICATION.mdtext/markdown
Registry catalog
registry/index.jsonone record per schema id

Field reference

25 fields across 7 steps, read from the published schema.json, with names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.

Applicant identification

  • fullName string required

    The applicant's full name, as recorded in the Portuguese civil registry.

    classification: pii
  • identityCardNumber string optional

    The number of the applicant's current Cartão de Cidadão or Bilhete de Identidade, when already held (relevant for a renewal or for an applicant who already holds one). The form's own '(caso possua)' (if you have one) qualifier confirms this is conditional, not universally applicable — e.g. a first-time applicant born abroad without a prior PT identity title.

    classification: pii
  • identityCardValidityDate date optional

    The expiry/validity date of the Cartão de Cidadão or Bilhete de Identidade identified above, printed immediately beside that field.

  • hasValidPortuguesePassport boolean required

    Whether the applicant currently holds a still-valid Portuguese passport. The form's own instruction conditions a document requirement on this answer: 'caso sim, apresentar o passaporte válido no dia do atendimento' (if yes, present the valid passport on the day of the appointment) — see the `previousValidPassport` entry in `documents[]`.

    enum: true | false
  • dateOfBirth date required

    The applicant's date of birth.

    classification: sensitive-pii
  • cpf string optional

    The applicant's Brazilian Cadastro de Pessoas Físicas (CPF) taxpayer number — a data point specific to this consulate's Brazil-resident applicant base.

    classification: sensitive-pii

Filiação (parentage)

  • fatherName string required

    The applicant's father's full name — filiação (parentage) data that Portugal's passport and Lei n.º 7/2007 identity record always carry.

    classification: pii
  • motherName string required

    The applicant's mother's full name — filiação (parentage) data that Portugal's passport and Lei n.º 7/2007 identity record always carry.

    classification: pii

Local de nascimento (place of birth)

  • civilParishOfBirth string optional

    The civil parish (freguesia) of birth, applicable when the applicant was born in Portugal. Printed under the section header 'Nascidos em Portugal:' (born in Portugal), an alternative to the separate 'Nascidos no Brasil ou outro país' (born in Brazil or another country) fields below; the form carries no checkbox or radio control selecting between the two sub-blocks, so this schema does not assert a structural `requiredWhen` dependency between them.

    classification: pii
  • municipalityOfBirth string optional

    The municipality (concelho) of birth, applicable when the applicant was born in Portugal.

    classification: pii
  • birthCityState string optional

    The city and state of birth, applicable when the applicant was born in Brazil or another country outside Portugal.

    classification: pii
  • birthCountry string optional

    The country of birth, applicable when the applicant was born outside Portugal.

    classification: pii

Endereço de residência (residential address)

  • residentialAddress string optional

    The applicant's residential street address. Unlike the São Paulo sibling form, this form does not split the street address into separate street/number/apartment fields — it is one printed line.

    classification: pii
  • residentialNeighborhood string optional

    The neighborhood (bairro) of the applicant's residential address — a Brazilian address-format field.

    classification: pii
  • residentialPostalCode string optional

    The Brazilian postal code (CEP) of the applicant's residential address.

    classification: pii
  • residentialCityState string optional

    The city and state of the applicant's residential address.

    classification: pii

Contact information

  • mobilePhone string optional

    The applicant's mobile phone number, with a printed area-code parenthetical.

    classification: pii
  • landlinePhone string optional

    The applicant's landline phone number, with a printed area-code parenthetical.

    classification: pii
  • email string optional

    The applicant's email address.

    patternclassification: pii

Modo de emissão e entrega (issuance mode and delivery)

  • issuanceMode enum required

    The requested processing speed for the passport's issuance: urgent (7 business days) or standard (14 days), as printed on the form.

    enum: urgente | sem_urgencia
  • deliveryAddressDifferentFromResidence string optional

    The street address to which the completed passport should be delivered, when different from the residential address given above. The form's own preceding note states the consulate mails the finished document directly to the address the applicant chooses ('o Consulado se encarrega de enviá-lo diretamente para endereço que escolher').

    classification: pii
  • deliveryNeighborhood string optional

    The neighborhood (bairro) of the delivery address, when different from the residential address.

    classification: pii
  • deliveryPostalCode string optional

    The Brazilian postal code (CEP) of the delivery address, when different from the residential address.

    classification: pii
  • deliveryCityState string optional

    The city and state of the delivery address, when different from the residential address.

    classification: pii

Data (date of request)

  • dateOfRequest date required

    The date the request is signed, printed as a blank 'Data:' line near the form's close. Like every other field on this form, this line carries no AcroForm widget of its own (the entire document is a flat, widget-free print facsimile) — modelled here because it is a clearly designated, self-documenting field on the form's own face, consistent with this registry's established discipline for widget-less closing date lines (see `pt/mne/requerimento-cartao-cidadao-passaporte-consular`'s own `dateOfRequest` field).

Verification record

This file is the source-review record for this document version, per the manual-source-review-v1 practice. It documents the provenance of the published fields and flow and states the current verification claim honestly.

Current claim

  • status: draft
  • verification.method: manual-source-review-v1
  • verification.lastVerifiedAt: 2026-07-08

This is GOV-1833: a "GovSchema Standard Research" cycle pursuing the one lead pt/mne/requerimento-cartao-cidadao-passaporte-consular's own VERIFICATION.md (GOV-1797) explicitly flagged as unexplored: "a genuinely distinct domestic or consular passport-specific form remains an open, unscreened backlog candidate for a future cycle." GOV-1797 had examined Rio de Janeiro's req_cc.pdf only as a comparison point against São Paulo's Cartão de Cidadão-centric AcroForm, and concluded the São Paulo form's own conditional "Somente Passaporte" option was the closest passport-adjacent source found — explicitly not a passport-specific application. This cycle searched further at the Rio de Janeiro consulate specifically and found a second, separate document at the same domain.

Candidate screening

Passport — picked: Rio de Janeiro consulate's req_psspnovo.pdf

Searched riodejaneiro.consuladoportugal.mne.gov.pt beyond the req_cc.pdf GOV-1797 had already examined, and found images/req_psspnovo.pdf ("Requerimento de Passaporte") — a distinct, passport-specific intake form at the same consular post, not a variant or later version of req_cc.pdf. Unlike req_cc.pdf (Cartão de Cidadão-centric, referenced only in GOV-1797's comparison notes) and unlike São Paulo's cc_e_pep_formulario.pdf (also Cartão de Cidadão-primary, with a passport option conditioned on already holding a valid CC/BI), this form's own title, opening fields, and every downstream section (issuance-speed choice, document-delivery-by-mail option) are passport-specific throughout; the CC/BI number field that does appear is explicitly marked "(caso possua)" (if you have one) and used only as an optional cross-reference identity number, not the form's primary subject.

Re-confirmed while re-screening this cycle: Portugal's domestic passport route (gov.pt's "Pedir ou renovar o passaporte eletrónico português") still describes only an in-person, appointment-based, biometric-enrolment process via IRN with no downloadable citizen-facing form, consistent with every prior cycle's finding (Decreto-Lei n.º 83/2000 Art. 16). No other Portuguese consulate's site was found to publish a further, third passport-specific form distinct from this one and from São Paulo's CC-centric form.

Access notes

riodejaneiro.consuladoportugal.mne.gov.pt could not be reached directly from this environment: both curl and Node's native https client get a TLS handshake failure (SSL routines::unexpected eof while reading / ECONNRESET) immediately after the ClientHello, for every path on the domain — the same network-level block this registry's gov1797 cycle recorded for the sibling saopaulo.consuladoportugal.mne.gov.pt subdomain. Per this registry's established Wayback workaround (project memory gov-au-wayback-workaround.md), the document was instead retrieved via web.archive.org's snapshot:

  • req_psspnovo.pdf — Wayback snapshot 20240713201256 (2024-07-13), HTTP 200, application/pdf, 100,261 bytes, %PDF-1.5.

tools/verify-sources.mjs was run against this document; both riodejaneiro.consuladoportugal.mne.gov.pt URLs report WARN (ECONNRESET, tolerated as a transient/blocked-access signature per the tool's own design), not FAIL — consistent with the network-level block described above rather than a dead or fabricated citation.

Extraction method

pdfjs-dist (legacy Node build) was used to extract the page's text content with per-item (x, y) transform coordinates, then grouped into printed lines by y-coordinate and sorted left-to-right by x within each line, to reconstruct the form's exact field order and grouping without relying on raw extraction order. Separately, page.getAnnotations() was called and returned 0 annotations — this PDF carries no AcroForm or XFA layer at all (confirmed independently: the raw file bytes contain no /AcroForm or /XFA token anywhere), unlike either cc_e_pep_formulario.pdf (a genuine 45-widget AcroForm) or req_cc.pdf (also widget-free, per GOV-1797's own finding) at the sibling consulates. This document's entire field set is therefore modelled from its self-documenting, cleanly legible printed text layer alone — every field here is the same class of source GOV-1797's own dateOfRequest field used for its one widget-less line, applied to an entire one-page form rather than a single field.

Field inventory

25 fields[] entries (0 with a real AcroForm widget — the source form has no fillable layer at all) and 1 documents[] entry, reconstructed from the extracted text lines below (y-coordinate, top to bottom):

| Printed line (y-coord) | Field(s) modelled | |---|---| | Nome completo: (647) | fullName | | Nº do Cartão de Cidadão ou Bilhete de identidade (caso possua) : (633) | identityCardNumber | | Data de Validade (620) | identityCardValidityDate | | Possui Passaporte (Português) Válido ? Não Sim (...) (592/582) | hasValidPortuguesePassport | | Data de Nascimento: CPF: (561) | dateOfBirth, cpf | | Nome do pai: (547) | fatherName | | Nome da mãe: (533) | motherName | | Local de nascimento : / Nascidos em Portugal: / Freguesia : (506/492/478) | civilParishOfBirth | | Concelho : (464) | municipalityOfBirth | | Nascidos no Brasil ou outro país : / Cidade/Estado: (437/423) | birthCityState | | País : (409) | birthCountry | | Endereço de residência: (381) | residentialAddress | | Bairro: (368) | residentialNeighborhood | | CEP: Cidade/Estado: (354) | residentialPostalCode, residentialCityState | | Nº Celular : ( ) Nº Tel. Fixo ( ) (340) | mobilePhone, landlinePhone | | e-mail (326) | email | | Modo de emissão: Urgente (7 dias uteis) Sem urgência (14 dias ) (299) | issuanceMode | | Endereço para a entrega do documento (caso não seja o mesmo da residência): (243) | deliveryAddressDifferentFromResidence | | Bairro: (216) | deliveryNeighborhood | | CEP: Cidade/Estado: (202) | deliveryPostalCode, deliveryCityState | | Data: (166) | dateOfRequest |

documents[]: previousValidPassport, sourced from the form's own "caso sim, apresentar o passaporte válido no dia do atendimento" (if yes, present the valid passport on the day of the appointment) instruction, modelled with requiredWhen gated on hasValidPortuguesePassport equalling true.

Judgment calls

  1. Closes Portugal's Passport vertical, distinct from the National ID vertical pt/mne/requerimento-cartao-cidadao-passaporte-consular already occupies. This form's own title ("Requerimento de Passaporte") and every section are passport-specific; the one CC/BI field present is an optional cross-reference, not the form's primary subject — the inverse structure of the São Paulo sibling, where Cartão de Cidadão is primary and passport is the conditional option. This satisfies the distinction GOV-1797's own judgment call 1 drew when declining to double-count the São Paulo form under both verticals.
  2. No requiredWhen dependency is asserted between the "born in Portugal" fields (civilParishOfBirth/municipalityOfBirth) and the "born in Brazil or another country" fields (birthCityState/ birthCountry), for the same reason as the São Paulo sibling schema's judgment call 5: the form carries section headers, not a checkbox or radio control selecting between the two, so asserting a structural rule here would fabricate a dependency the source does not itself encode as a checkable condition (see project memory notequals-empty-string-absent-field-bug).
  3. No field is marked required: true on an explicit in-document mandatory-marker — this form's extractable text carries no "obrigatório" (or equivalent) annotation anywhere. Every required: true field (fullName, hasValidPortuguesePassport, dateOfBirth, fatherName, motherName, issuanceMode, dateOfRequest) is instead inferred from its role as a structurally necessary identity/parentage/ gating/closing field, the same softer basis disclosed in the São Paulo sibling schema's judgment call 8. identityCardNumber, cpf, email, and both address blocks are left optional for the same reason, plus the source's own "(caso possua)" (if you have one) qualifier on the identity card field.
  4. dateOfRequest is modelled despite carrying no AcroForm widget — consistent with the São Paulo sibling schema's own judgment call 4, except here it applies to the entire form rather than one closing line, since this document has no fillable layer at all. Included because it is a clearly designated, self-documenting field on the form's own face.
  5. No fee/payment documents[] entry. No fee schedule or payment instruction is printed anywhere on this one-page form (unlike the São Paulo sibling, whose separate fee-schedule PDF at least surfaced in a web search even though it could not be fetched). Omitted rather than fabricated, consistent with this registry's standing discipline after the GOV-1760/GOV-1763 fabricated-sourcing incidents.
  6. No live submission was attempted. Submitting this form at a real consular appointment triggers a real fee, a real biometric appointment, and a real change to the applicant's legal travel document — not a safe or reversible action to simulate against a live government process, consistent with this registry's standing discipline.

Validation

``` $ node tools/validate.mjs registry/pt/mne/requerimento-passaporte-consular/1.0.0/schema.json ok registry/pt/mne/requerimento-passaporte-consular/1.0.0/schema.json

1/1 document(s) passed.

$ node tools/validate-ajv.mjs registry/pt/mne/requerimento-passaporte-consular/1.0.0/schema.json ok registry/pt/mne/requerimento-passaporte-consular/1.0.0/schema.json [v0.3]

1/1 document(s) validated against the meta-schema (ajv 2020-12).

$ node tools/verify-sources.mjs registry/pt/mne/requerimento-passaporte-consular/1.0.0 verify-sources: checking 1 schema version directory...

pt/mne/requerimento-passaporte-consular/1.0.0 (3 URLs) [WARN] https://riodejaneiro.consuladoportugal.mne.gov.pt/ transient failure after 3 attempt(s) (ECONNRESET) — tolerated, re-check manually if this persists [WARN] https://riodejaneiro.consuladoportugal.mne.gov.pt/images/req_psspnovo.pdf transient failure after 3 attempt(s) (ECONNRESET) — tolerated, re-check manually if this persists

verify-sources: 1 directory, 3 URLs checked, 2 warning(s), 0 allowlisted, all clear. ```

Both WARNs are expected given the environment-level TLS block documented above under "Access notes," not evidence of a dead or fabricated source.

View the raw record (VERIFICATION.md)

Version history

  • 1.0.0 draft latest this page has verification record schema.json

Independent and non-affiliated

GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by Ministério dos Negócios Estrangeiros — Consulado-Geral de Portugal no Rio de Janeiro or any government. The authoritative source is always the live government form and its official instructions.