feat: extracting inline schemas to their own schema objects for better code gen (#219)

### TL;DR

Refactored OpenAPI specification by extracting inline schema definitions into reusable schema components.

### What changed?

Extracted inline schema definitions from API endpoints into separate reusable schema components in the `components/schemas` section. This affects multiple endpoints including:

- Platform configuration updates (`PlatformConfigUpdateRequest`)
- Customer KYC links (`KycLinkResponse`) 
- Transfer operations (`TransferInRequest`, `TransferOutRequest`)
- Payment approvals/rejections (`ApprovePaymentRequest`, `RejectPaymentRequest`)
- Bulk customer imports (`BulkCustomerImportJobAccepted`)
- UMA invitations (`UmaInvitationCreateRequest`, `UmaInvitationClaimRequest`)
- Sandbox operations (`SandboxSendRequest`, `SandboxUmaReceiveRequest`, `SandboxFundRequest`)
- API token creation (`ApiTokenCreateRequest`)

Each inline schema definition was replaced with a `$ref` reference to the corresponding component schema.

### How to test?

1. Validate the OpenAPI specification using an OpenAPI validator
2. Generate API documentation to ensure all schemas render correctly
3. Test API client generation to verify schema references resolve properly
4. Verify that all endpoint request/response schemas maintain the same structure and validation rules

### Why make this change?

This refactoring improves the OpenAPI specification by:
- Reducing duplication of schema definitions
- Making schemas reusable across multiple endpoints
- Improving maintainability by centralizing schema definitions
- Following OpenAPI best practices for schema organization
- Making the specification more modular and easier to manage

Author: pengying

mintlify/openapi.yaml

@@ -0,0 +1,12 @@
+type: object
+properties:
+  umaDomain:
+    type: string
+    example: mycompany.com
+  webhookEndpoint:
+    type: string
+    example: https://api.mycompany.com/webhooks/uma
+  supportedCurrencies:
+    type: array
+    items:
+      $ref: ./PlatformCurrencyConfig.yaml

openapi.yaml

@@ -0,0 +1,14 @@
+type: object
+required:
+  - jobId
+  - status
+properties:
+  jobId:
+    type: string
+    description: Unique identifier for the bulk import job
+    example: Job:019542f5-b3e7-1d02-0000-000000000006
+  status:
+    type: string
+    enum:
+      - PENDING
+      - PROCESSING

openapi/components/schemas/config/PlatformConfigUpdateRequest.yaml

@@ -0,0 +1,14 @@
+type: object
+properties:
+  kycUrl:
+    type: string
+    description: A hosted KYC link for your customer to complete KYC
+    example: "https://example.com/redirect"
+  platformCustomerId:
+    type: string
+    description: The platform id of the customer to onboard
+    example: 019542f5-b3e7-1d02-0000-000000000001
+  customerId:
+    type: string
+    description: The customer id of the newly created customer on the system
+    example: Customer:019542f5-b3e7-1d02-0000-000000000001

openapi/components/schemas/customers/BulkCustomerImportJobAccepted.yaml

@@ -0,0 +1,8 @@
+type: object
+required:
+  - inviteeUma
+properties:
+  inviteeUma:
+    type: string
+    description: The UMA address of the customer claiming the invitation
+    example: $invitee@uma.domain

openapi/components/schemas/customers/KycLinkResponse.yaml

@@ -0,0 +1,36 @@
+type: object
+required:
+  - inviterUma
+properties:
+  inviterUma:
+    type: string
+    description: The UMA address of the customer creating the invitation
+    example: $inviter@uma.domain
+  firstName:
+    type: string
+    description: First name of the invitee to show as part of the invite
+    example: Alice
+  amountToSend:
+    description: >
+      An amount to send (in the smallest unit of the customer's currency)
+      to the invitee when the invitation is claimed.
+
+      This is optional and if not provided, the invitee will not
+      receive any amount. Note that the actual sending of
+
+      the amount must be done by the inviter platform once the
+      INVITATION_CLAIMED webhook is received. If the inviter
+
+      platform either does not send the payment or the payment fails,
+      the invitee will not receive this amount. This
+
+      field is primarily used for display purposes on the claiming
+      side of the invitation.
+    type: integer
+    format: int64
+    example: 12550
+  expiresAt:
+    type: string
+    format: date-time
+    description: When the invitation expires (if at all)
+    example: '2025-09-01T14:30:00Z'

openapi/components/schemas/invitations/UmaInvitationClaimRequest.yaml

@@ -0,0 +1,13 @@
+type: object
+required:
+  - amount
+properties:
+  amount:
+    type: integer
+    format: int64
+    description: >-
+      Amount to add in the smallest unit of the account's currency (e.g.,
+      cents for USD/EUR, satoshis for BTC)
+    exclusiveMinimum: 0
+    maximum: 100000000000
+    example: 100000

openapi/components/schemas/invitations/UmaInvitationCreateRequest.yaml

@@ -0,0 +1,21 @@
+type: object
+required:
+  - quoteId
+  - currencyCode
+properties:
+  quoteId:
+    type: string
+    description: The unique identifier of the quote
+    example: Quote:019542f5-b3e7-1d02-0000-000000000006
+  currencyCode:
+    type: string
+    description: Currency code for the funds to be sent
+    example: USD
+  currencyAmount:
+    type: integer
+    format: int64
+    description: >-
+      The amount to send in the smallest unit of the currency (eg.
+      cents). If not provided, the amount will be derived from the quote.
+    exclusiveMinimum: 0
+    example: 1000

openapi/components/schemas/sandbox/SandboxFundRequest.yaml

@@ -0,0 +1,32 @@
+type: object
+required:
+  - senderUmaAddress
+  - receivingCurrencyCode
+  - receivingCurrencyAmount
+properties:
+  senderUmaAddress:
+    type: string
+    description: UMA address of the sender from the sandbox
+    example: $success.usd@sandbox.grid.uma.money
+  receiverUmaAddress:
+    type: string
+    description: UMA address of the receiver (optional if customerId is provided)
+    example: $receiver@uma.domain
+  customerId:
+    type: string
+    description: >-
+      System ID of the receiver (optional if receiverUmaAddress is
+      provided)
+    example: Customer:019542f5-b3e7-1d02-0000-000000000001
+  receivingCurrencyCode:
+    type: string
+    description: The currency code for the receiving amount
+    example: USD
+  receivingCurrencyAmount:
+    type: integer
+    format: int64
+    description: >-
+      The amount to be received in the smallest unit of the currency
+      (eg. cents)
+    exclusiveMinimum: 0
+    example: 1000