GET legal_entity_applications/[id]

Retrieve details of a specific legal entity application.

Endpoint

GET /api/v1/legal_entity_applications/{id}

Authentication

Requires a valid API key in the Authorization header:

Authorization: Bearer <your-api-key>

Path Parameters

Parameter	Type	Required	Description
id	string	Yes	The unique identifier of the legal entity application

Example Request

curl -X GET https://portal.eprospera.com/api/v1/legal_entity_applications/12345678-abcd-1234-abcd-123456789012 \
  -H "Authorization: Bearer <your-api-key>"

Response

Success Response (200 OK)

Field	Type	Description
data	object	Legal entity application details

Application Object Fields

Field	Type	Description
id	string	Application unique identifier
statusId	string	Current status of the application
applicationData	object	Complete application data
applicationVersion	string	Version of the application format
submittedAt	string | null	Submission timestamp (ISO 8601)
createdAt	string	Creation timestamp (ISO 8601)
approvedAt	string | null	Approval timestamp (ISO 8601)
rejectedAt	string | null	Rejection timestamp (ISO 8601)
legalEntityId	string | null	ID of created legal entity (if approved)

Status Values

• "Draft" - Application is being prepared
• "Pending Review" - Application is being reviewed
• "Approved" - Application has been approved
• "Rejected" - Application has been rejected

Example Response

{
  "data": {
    "id": "12345678-abcd-1234-abcd-123456789012",
    "statusId": "Approved",
    "applicationData": {
      "residencyType": "e_resident_entity_zf7j7u",
      "createdViaAPI": true,
      "entityDetails": {
        "name": "Example Tech Company",
        "extension": "LLC",
        "entityType": "llc",
        "jurisdictionOfFormation": "Próspera ZEDE",
        "nameStartsWithExtension": false,
        "residentEmail": "contact@example.com",
        "principalOffice": {
          "line1": "123 Business St",
          "city": "Próspera",
          "postalCode": "12345",
          "country": "Honduras"
        },
        "representatives": [
          {
            "residentPermitNumber": "80000000000012"
          }
        ],
        "registeredAgentProviderSelection": "provider_123"
      },
      "businessIntentions": "Software development services",
      "referralSource": "Online research",
      "website": "https://example.com"
    },
    "applicationVersion": "1.0.0",
    "submittedAt": "2024-01-15T10:30:00.000Z",
    "createdAt": "2024-01-15T09:15:00.000Z",
    "approvedAt": "2024-01-16T14:20:00.000Z",
    "rejectedAt": null,
    "legalEntityId": "123e4567-e89b-12d3-a456-426614174000"
  }
}

Error Responses

401 Unauthorized

Invalid or missing API key:

{
  "error": "Invalid API key"
}

404 Not Found

Application not found or you don't have access:

{
  "error": "Legal entity application not found"
}

500 Internal Server Error

Server error:

{
  "error": "Internal server error"
}

Application Data Structure

The applicationData field contains the complete application information including:

Entity Details

• Basic Information: Name, extension, entity type, and formation jurisdiction
• Contact Information: Resident email and principal office address
• Representatives: Information about entity representatives (includes your RPN)
• Registered Agent: Either a provider selection or custom registered agent details

Additional Information

• Business Context: Business intentions, referral source, website
• API Flag: createdViaAPI indicates this application was created via API
• Residency Type: Internal residency type identifier based on your selection

Legal Entity Reference

Once an application is approved, the legalEntityId field will contain the ID of the created legal entity, which you can use with the GET /legal_entities/{id} endpoint.

Access Control

You can only access applications that you created. The API automatically filters results based on your user account.