Skip to main content

Release 2026-02-03

This release strengthens automated seller onboarding by enabling platforms to initiate and track seller applications programmatically, while also improving the API input validation system to simplify integrations and error handling.

With the new onboarding capabilities, platforms can streamline seller activation through automated flows and receive clear lifecycle updates via webhooks. Additionally, enhanced validation errors provide structured metadata, making it easier to identify, localize and resolve request issues.

Seller onboarding support​

Platforms can now initiate the seller onboarding process through the Getpaid API, enabling an automated and scalable approach to adding new sellers. This streamlines the onboarding flow and allows platforms to embed seller activation seamlessly into their existing systems.

Starting a seller application is straightforward:

POST api.getpaid.io/v2/applications
{
  "reference": "53426",
  "applicant": {
    "email": "markus.keller@garagegermany.de"
  },
  "redirect": {
    "default": "https://titanauto.com/onboarding/complete?customer=53426"
  },
  "webhooks": {
    "url": "https://webhooks.titanauto.com/getpaid"
  }
}

This request automatically initiates the onboarding flow and returns a link to the Getpaid-hosted onboarding experience. Platforms receive webhooks when the application is submitted (including the start of any required compliance checks) and again once the onboarding process has been successfully completed, enabling clear tracking and automation throughout the seller activation lifecycle.

To track an application progress, platforms can query an endpoint that will provide the latest status:

{
  "id": "app_4fekhxdpss1et7rjp8t7rdpnw4",
  "status": "initiated",
  "reference": "53426",
  "flow": {
    "next_step": "https://onboarding.getpaid.io/v2/app_4fekhxdpss1et7rjp8t7rdpnw4?token=eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxIn0.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"
  },
  "created_at": "2025-10-24T14:45:22.993Z",
  "updated_at": "2025-11-09T14:15:22.993Z",
}

See the API Applications documentation for more information.

Improved input validation system​

The API input validation system has been streamlined to simplify error handling and provide richer, structured metadata for troubleshooting. This update makes validation errors easier to interpret, localize, and resolve programmatically, while preserving a consistent response format.

With this new approach, known validation errors are standardized and accompanied by additional metadata that surfaces actionable context (such as limits or constraints) in a machine-readable format. This allows platforms to build clearer error handling, improve user-facing messaging, and reduce debugging time.

Before:

Previous validation error format
{
  "type": "https://docs.getpaid.io/integration/api/responses#422---invalid-parameters",
  "title": "Invalid Parameters",
  "status": 422,
  "detail": "The request was invalid",
  "errors": {
    "field": ["field_max_length_exceeded_255"]
  }
}

Now, validation errors include a normalized error code and an accompanying errors_metadata object with structured details:

Updated validation error format
{
  "type": "https://docs.getpaid.io/integration/api/responses#422---invalid-parameters",
  "title": "Invalid Parameters",
  "status": 422,
  "detail": "The request was invalid",
  "errors": {
    "field": ["exceeds_max_length"]
  },
  "errors_metadata": {
    "field": {
      "exceeds_max_length": {
        "max_length": 255
      }
    }
  }
}

This enhancement enables platforms to reliably map errors to specific validation rules, display contextual guidance, and implement more robust client-side validation flows.

See the API error response documentation for full details.