> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cadanapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Submit business filing fields

> Submit statutory filing fields for a business in a jurisdiction. Use this
endpoint for fields returned by the required-fields endpoint with
`entity: "business"` and `scope` containing `"filing"`.

Fields are validated against the jurisdiction's field definitions.
Unknown keys are rejected.




## OpenAPI

````yaml /openapi/statutory-compliance.yaml put /v1/statutory/businesses/{business_id}/fields/{country_code}
openapi: 3.0.0
info:
  title: Statutory Compliance API
  version: 0.1.0
  description: Statutory filing, government remittance, and compliance tracking API
  termsOfService: https://cadanapay.com/terms-and-conditions
  contact:
    email: api@cadanapay.com
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
servers:
  - url: https://api.cadanapay.com
    description: Prod Server
  - url: https://dev-api.cadanapay.com
    description: Dev Server
security:
  - Authorization: []
tags:
  - name: Jurisdictions
    description: Discover supported countries, required fields, and filing types
  - name: Filings
    description: >-
      Create, submit, and track statutory returns — from upcoming obligations
      through acceptance
  - name: Remittances
    description: Government payments linked to filings
  - name: Requirements
    description: Prerequisites that must be satisfied before filing
  - name: Events
    description: Immutable audit trail
  - name: Statutory Fields
    description: Submit and read entity-level statutory filing data
paths:
  /v1/statutory/businesses/{business_id}/fields/{country_code}:
    put:
      tags:
        - Statutory Fields
      summary: Submit business filing fields
      description: >
        Submit statutory filing fields for a business in a jurisdiction. Use
        this

        endpoint for fields returned by the required-fields endpoint with

        `entity: "business"` and `scope` containing `"filing"`.


        Fields are validated against the jurisdiction's field definitions.

        Unknown keys are rejected.
      operationId: putBusinessFields
      parameters:
        - $ref: '#/components/parameters/XMultiTenantKey'
        - $ref: '#/components/parameters/BusinessIdPath'
        - $ref: '#/components/parameters/CountryCode'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PutStatutoryFieldsRequest'
            example:
              fields:
                betriebsnummer: '12345678'
                finanzamtNummer: '2722'
      responses:
        '204':
          description: Fields saved successfully
        '400':
          $ref: '#/components/responses/BadRequest'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    XMultiTenantKey:
      name: X-MultiTenantKey
      in: header
      required: false
      schema:
        type: string
      description: >-
        Required when using a Platform API token. The tenant key identifying
        which business to operate on.
    BusinessIdPath:
      name: business_id
      in: path
      required: true
      schema:
        type: string
      description: Business identifier
      example: biz_01ABC
    CountryCode:
      name: country_code
      in: path
      required: true
      schema:
        type: string
        pattern: ^[A-Z]{2}$
      description: ISO 3166-1 alpha-2 country code
      example: MX
  schemas:
    PutStatutoryFieldsRequest:
      type: object
      required:
        - fields
      description: Request body for submitting statutory filing fields.
      properties:
        fields:
          type: object
          additionalProperties:
            type: string
          description: |
            Key-value pairs of field data. Keys must match the `key` values
            from the jurisdiction's required-fields response.
          example:
            steuerID: '97148835200'
            personengruppenschluessel: '101'
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              example: invalid_request
            message:
              type: string
              example: countryCode is required
            details:
              type: array
              nullable: true
              items:
                type: object
                properties:
                  field:
                    type: string
                  message:
                    type: string
  responses:
    BadRequest:
      description: Invalid request parameters
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    Authorization:
      type: http
      scheme: bearer
      bearerFormat: API_SECRET_KEY

````