> ## Documentation Index > Fetch the complete documentation index at: https://docs.jupico.com/llms.txt > Use this file to discover all available pages before exploring further. # Update an application > Updates an existing application. The application must be in `review` status; once activated, it cannot be modified. ## OpenAPI ````yaml /openapi.json post /v1/provisioning/application/update openapi: 3.0.0 info: title: Jupico - OpenAPI 3.0 description: >- The Jupico API lets Service Providers onboard merchants, process card and eCheck (ACH) payments, run hosted payment pages, manage recurring billing, send payouts, and query every resource. All endpoints use HTTPS with Basic authentication and accept and return JSON. Endpoints are grouped by workflow: onboard merchants first, then accept payments, then move funds and report. termsOfService: https://help.jupico.com/references-and-resources/legal contact: email: support@jupico.com license: name: Jupico License url: https://jupico.com version: 1.0.5 servers: - url: https://sandbox-platform.jupico.com security: - basicAuth: [] tags: - name: Status description: Health check for the Jupico API. - name: Onboarding Invites description: >- Create and send invites that onboard merchants through the Jupico-hosted flow, with optional pre-filled identity, fees, and payout bank account data. - name: Provisioning description: >- Onboard merchants from your own UI. Collect onboarding data and submit it through the provisioning chain: applicant → application → submerchant. - name: Session description: >- Create browser authorization sessions for the Jupico web components, so card and bank account data is tokenized client-side and never touches your servers. - name: Tokenization description: >- Convert one-time tokens from the web components into permanent Jupico tokens, or tokenize raw card data if your systems are PCI DSS compliant. - name: Customer description: >- Create and manage customer records that payments, subscriptions, installments, and invoices link to. - name: Card Transactions description: >- Process credit and debit card transactions using tokenized card data: sale, authorization, capture, void, refund, and rollback. - name: eCheck Transactions description: >- Debit customer bank accounts via eCheck (ACH): sale, void, refund, rollback, and bank account tokenization. - name: Checkouts description: >- Hosted checkout sessions where customers complete payment on a Jupico-hosted page. - name: Payment Links description: >- Shareable links that open a Jupico-hosted payment page — no integration code needed at the point of sharing. - name: Invoices description: Create and email invoices that customers pay online. - name: Subscriptions description: >- Recurring billing. Plans define billing schedules and pricing models; subscriptions enroll customers against a stored payment token. - name: Installments description: Split a fixed total into scheduled payments with an optional deposit. - name: Payouts description: >- Send funds from a submerchant's available balance to a tokenized bank account with on-demand payout instructions. - name: Query description: >- Search and report across every resource: transactions, merchants, settlements, balances, disputes, fees, and more. All query endpoints accept the same filter, sort, and pagination envelope — see the Query Capabilities guide. paths: /v1/provisioning/application/update: post: tags: - Provisioning summary: Update an application description: >- Updates an existing application. The application must be in `review` status; once activated, it cannot be modified. operationId: updateApplication requestBody: required: true content: application/json: schema: type: object required: - smApplicationId properties: smApplicationId: type: string description: Must be exactly 24 characters example: 68f7a101547bd249c32b907b identity: type: object properties: owners: type: array items: type: object properties: title: type: string enum: - Mr. - Ms. - Mrs. example: Mr. description: Salutation of the owner (`Mr.`, `Ms.`, `Mrs.`). firstName: type: string maxLength: 24 example: Johns description: First name. middleName: type: string maxLength: 24 example: Michaels description: Middle name. lastName: type: string maxLength: 24 example: Doe description: Last name. birthDate: type: string format: date example: '1974-06-25' description: Date of birth (YYYY-MM-DD). phoneNumber: type: string maxLength: 15 example: '2149244554' description: Phone number of the owner. streetNum: type: string maxLength: 9 example: '1004' description: Street number. streetName: type: string maxLength: 40 example: Main Street Ct description: Street name. city: type: string maxLength: 30 example: McKinney description: City name. state: type: string description: US state code example: TX postalCode: type: string maxLength: 5 example: '75070' description: ZIP or postal code. ssn: type: string description: 9 digits example: '258267389' ownershipPercentage: type: integer example: 100 description: >- Percentage of the business this owner holds (0-100). email: type: string maxLength: 70 example: email@example.com description: Email address of the owner. position: type: string enum: - OW - CEO - CFO - COO - PRESIDENT - VICE PRESIDENT - DIR - TR - SEC - PA - MEMBER LLC - OTH - SP example: SP description: Role of the owner in the business. country: type: string example: US description: Two-letter ISO country code. description: >- Business owners. Required for individual and business entity types. description: Identity details for the business and its owners. responses: '200': description: Application updated successfully content: application/json: schema: type: object properties: code: type: string description: >- Machine-readable result code. See the Error Codes reference. success: type: boolean description: >- Whether the request was processed successfully. Declines return HTTP 200 with `success: false`. message: type: string description: Human-readable result message. data: type: object properties: smApplicationId: type: string description: Unique identifier for the application status: type: string enum: - review - approved - rejected example: review description: Current status. description: The response payload. security: - basicAuth: [] components: securitySchemes: basicAuth: type: http scheme: basic ````