Straddle icon

Straddle

Interact with Straddle API
Join our community

Actions81

Overview

This node allows updating (patching) platform information in the Straddle API. It is useful for modifying existing platform records by changing details such as business profile, metadata, or external identifiers. Typical use cases include updating a platform’s business address, industry classification, support contact channels, or adding custom metadata to keep platform data current and accurate.

For example, you might use this node to update the support email and phone number of a platform or to add new metadata keys that help categorize platforms internally.

Properties

Name Meaning
Platform Id The unique identifier of the platform to update (required).
Request Id Optional client-generated identifier to trace and debug a specific request.
Correlation Id Optional client-generated identifier to trace and debug a series of related requests.
Business Profile JSON object containing business profile information including address, industry, and support channels. Example structure: { "address": {...}, "industry": {...}, "support_channels": {...} }
Metadata JSON object with user-defined key-value pairs for custom metadata associated with the platform.
External Id A string representing an external identifier for the platform.

Output

The node outputs the updated platform data as JSON in the json output field. This includes all the patched fields such as the updated business profile, metadata, external ID, and any other platform attributes returned by the API after the patch operation.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Straddle API.
  • The base URL for API requests depends on the configured environment credential parameter.
  • The node sends HTTP PATCH requests with JSON bodies to the Straddle API endpoint corresponding to the platform ID.

Troubleshooting

  • Missing or invalid Platform Id: The operation requires a valid platform ID; ensure it is provided and correctly formatted.
  • Invalid JSON in Business Profile or Metadata: If these fields are not valid JSON, the request will fail. Use proper JSON formatting.
  • Authentication errors: Ensure the API key credential is correctly set up and has permissions to update platform data.
  • API endpoint errors: Check that the environment setting matches the correct API base URL and that the platform ID exists.
  • Header routing issues: The optional request-id and correlation-id headers must be strings if used; otherwise, omit them.

Links and References

Discussion