mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the "Marketplace" resource of the mittwald mStudio API, specifically allowing users to update ("patch") contributor information. It is useful for scenarios where you need to modify details about a contributor in the marketplace, such as updating contact information, descriptions, or contract ownership data.

Practical examples include:

  • Updating a contributor's description in multiple languages.
  • Changing the contact person user ID associated with a contributor.
  • Modifying deviating contract owner details like address or support information.
  • Adjusting homepage or imprint information related to the contributor.

Properties

Name Meaning
Contributor Id The unique identifier of the contributor to be updated (required).
Contact Person User Id The user ID of the contact person for this contributor.
Descriptions A JSON object containing localized descriptions about the contributor (e.g., in German and English).
Deviating Contract Owner A JSON object specifying an alternative contract owner’s contact details, including address and phone numbers.
Deviating Name An alternative name for the contract owner if it differs from the default.
Deviating Support Information A JSON object with support-related contact info, such as email.
Homepage URL string representing the contributor’s homepage.
Imprint Text or string containing imprint/legal notice information related to the contributor.

Output

The node outputs JSON data reflecting the updated contributor information as returned by the mittwald mStudio API after the patch operation. This typically includes the contributor's current state with all applied changes.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the mittwald mStudio API.
  • The base URL for API requests is https://api.mittwald.de.
  • The node uses standard HTTP headers for JSON content (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing Contributor Id: Since the contributor ID is required, omitting it will likely cause an error. Ensure this property is set.
  • Invalid JSON in properties: Properties like descriptions, deviatingContractOwner, and deviatingSupportInformation expect valid JSON strings. Malformed JSON will cause parsing errors.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate with the API.
  • API endpoint issues: Network problems or incorrect base URL configuration can lead to request failures.
  • Empty or null values: Some fields like phone numbers may contain nulls; ensure that the API accepts these or provide valid data.

Links and References

Discussion