> ## Documentation Index > Fetch the complete documentation index at: https://developer.findity.com/llms.txt > Use this file to discover all available pages before exploring further. # Update partner > Updates an existing partner. Only the supplied properties are updated; unknown properties are ignored. For `vat` and `sendEventToExternalSystem`, omitting the property leaves its current value unchanged, while sending an explicit `null` clears it. `partnerCode` is the exception: a `null` value is treated the same as omitting the property and never clears the existing partner code, since it cannot be removed via this endpoint. See the request schema for the exact per-property behavior. `id` and `clientApplicationId` cannot be changed via this request. The caller must be allowed to administer the partner. Returns the updated partner. ## OpenAPI ````yaml /openapi/findity-admin-api.json put /partners/{partnerId} openapi: 3.1.0 info: title: Findity Admin API description: Findity Admin API version: 1.0.0 servers: - url: https://stage-api.findity.com/api/v1/admin - url: https://api.findity.com/api/v1/admin security: - bearerAuth: [] paths: /partners/{partnerId}: put: tags: - Partners summary: Update partner description: > Updates an existing partner. Only the supplied properties are updated; unknown properties are ignored. For `vat` and `sendEventToExternalSystem`, omitting the property leaves its current value unchanged, while sending an explicit `null` clears it. `partnerCode` is the exception: a `null` value is treated the same as omitting the property and never clears the existing partner code, since it cannot be removed via this endpoint. See the request schema for the exact per-property behavior. `id` and `clientApplicationId` cannot be changed via this request. The caller must be allowed to administer the partner. Returns the updated partner. operationId: updatePartner parameters: - name: partnerId in: path required: true description: Partner external ID schema: type: string example: abc123 requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PartnerUpdateRequest' example: name: Updated Partner Name vat: SE556123456789 responses: '200': description: Partner updated content: application/json: schema: $ref: '#/components/schemas/Partner' example: id: abc123 name: Updated Partner Name partnerCode: FINDITY vat: SE556123456789 clientApplicationId: '987654321' dateCreated: '2026-07-10T08:21:00Z' sendEventToExternalSystem: false settings: showReportOverview: true '400': description: > Bad request - invalid JSON body, no known properties, an unrecognized `settings` key, or a duplicate `partnerCode` content: application/json: schema: $ref: '#/components/schemas/400Error' examples: invalid json body: value: result: error code: INVALID_JSON_BODY description: Failed to parse json body no known properties: value: result: error code: NO_KNOWN_JSON_PROPERTIES description: No known, or only read-only properties received unrecognized settings key: value: result: error code: INVALID_PARTNER_SETTINGS_KEY description: 'Unknown settings key(s): reports' partnerCode already exists: value: result: error code: INVALID_PARAMETER description: Partner code FINDITY already exists '403': description: > Forbidden - either no partner exists with the given `partnerId`, or the caller is not allowed to update it. These two cases are intentionally indistinguishable, so a caller without access cannot use this endpoint to discover whether a `partnerId` exists. content: application/json: schema: $ref: '#/components/schemas/403Error' example: result: error description: Not allowed to update partner with id abc123 components: schemas: PartnerUpdateRequest: type: object description: >- Payload used to update a partner. Only the supplied properties are updated; unknown properties are ignored. `id` and `clientApplicationId` cannot be changed. properties: name: type: string description: Partner name. If supplied, must be a non-blank string. partnerCode: type: string nullable: true description: > Partner code, must be unique. Free-form string - the server does not enforce a length limit or character-set restriction on it beyond the uniqueness check. Omitting this property leaves the current partner code unchanged. Sending an explicit `null` is also treated as omission and never clears the partner code - it cannot be cleared via this endpoint. This is unlike `vat` and `sendEventToExternalSystem` below, where `null` is a meaningful value that clears the field; despite `nullable: true` being set here too, for `partnerCode` specifically `null` behaves exactly like omitting the property. vat: type: string nullable: true description: > VAT number. Free-form string - the server does not validate, normalize, or restrict its format. Omitting this property leaves the current VAT number unchanged. Sending an explicit `null` clears it. sendEventToExternalSystem: type: boolean nullable: true description: > Whether events should be sent to an external system. Omitting this property leaves the current value unchanged. Sending an explicit `null` clears it. settings: $ref: '#/components/schemas/PartnerSettings' required: [] Partner: type: object description: Partner resource returned when a partner is created or updated. properties: id: type: string description: Partner external ID name: type: string description: Partner name partnerCode: type: string nullable: true description: Partner code vat: type: string nullable: true description: VAT number clientApplicationId: type: string description: Client application that owns the partner dateCreated: type: string format: date-time description: Creation date sendEventToExternalSystem: type: boolean nullable: true description: Whether events are sent to an external system settings: $ref: '#/components/schemas/PartnerSettings' required: - id - name - clientApplicationId - dateCreated 400Error: type: object properties: result: type: string code: type: string description: type: string 403Error: type: object properties: result: type: string description: type: string example: result: error description: Not allowed PartnerSettings: type: object description: > Partner settings map. Only these top-level keys are allowed: `maxNumberOfCards`, `numberOfReportGroups`, `showReportOverview`, `fieldSettings`, `fortnox`. Any other top-level key is rejected with `INVALID_PARTNER_SETTINGS_KEY`. properties: maxNumberOfCards: type: integer readOnly: true description: > Maximum number of cards. Server-computed; always 2. Marked read-only for documentation purposes only - the server does not reject a create/update request that includes this property. If sent, the value is silently ignored: the server always overwrites it with 2 rather than returning a validation error or persisting the submitted value. numberOfReportGroups: type: integer description: Number of report groups. showReportOverview: type: boolean description: Whether the report overview is shown. fieldSettings: type: object description: Field configuration settings. Free-form object. additionalProperties: true required: [] fortnox: type: object description: >- Fortnox integration settings, e.g. partner mapping. Free-form object. additionalProperties: true required: [] additionalProperties: false required: [] securitySchemes: bearerAuth: type: http scheme: bearer ````