Retrieve Product Application Details

The GET /v2/productApplication endpoint returns comprehensive details about a specific product application within the Netevia Banking platform. It exposes the application's current state, the associated account holder snapshot, and any verification or document requirements tied to that application.

Endpoint

GET /v2/productApplication

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when you need to review or process a product application on behalf of a partner or customer. It is particularly useful for tracking application progress (e.g., pending, approved, declined), confirming the product type associated with the application, and verifying that all customer details and compliance documents are accurate and complete.

Query Parameters

Response

200 OK

The response wraps all data inside a node object.

node object

{
  "node": {
    "typename": "PersonProductApplication",
    "id": "app_01HZ9XK2M3N4P5Q6R7S8T9U0V1",
    "createdAt": "2025-03-15T10:22:00Z",
    "updatedAt": "2025-06-01T14:35:00Z",
    "applicationState": {
      "status": "APPROVED"
    },
    "accountHolderSnapshot": {
      "typename": "PersonAccountHolder",
      "name": {
        "givenName": "Jane",
        "familyName": "Smith",
        "title": "Ms.",
        "suffix": null
      },
      "currentVerification": {
        "status": "VERIFIED",
        "reason": null,
        "results": [
          {
            "code": "KYC_PASS",
            "description": "Identity verification passed successfully."
          }
        ],
        "requiredDocuments": []
      },
      "primaryAuthorizedPerson": null,
      "businessProfile": null
    }
  }
}

Error Codes

Common Mistakes

• Omitting the applicationId query parameter — this parameter is required; the request will fail without it.
• Using an applicationId that belongs to a different partner scope — ensure the application was created under your authenticated partner account.
• Expecting document upload session details when none are present — requiredDocuments and documentUploadSession fields will be empty or null when verification is already complete.
• Confusing applicationState.status (the application workflow status) with currentVerification.status (the KYC/KYB check result) — both exist independently and must be checked separately.

Related Endpoints

• POST /v2/productApplication — Submit a new product application
• GET /v2/productApplication/list — List all product applications for a partner
• POST /v2/productApplication/document — Upload a required document for a product application
• GET /v2/accountHolder — Retrieve account holder details

Example

curl -X GET "https://api.banking.netevia.dev/v2/productApplication?applicationId=app_01HZ9XK2M3N4P5Q6R7S8T9U0V1" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"