Straddle icon

Straddle

Interact with Straddle API
Join our community

Actions81

Overview

This node operation updates an existing representative's information in the Straddle system by sending a PUT request to the API endpoint for a specific representative identified by their ID. It is useful when you need to modify details such as the representative’s name, date of birth, contact information, or relationship data.

Typical use cases include:

  • Correcting or updating personal information of a representative.
  • Synchronizing your internal database changes with the Straddle platform.
  • Maintaining up-to-date compliance and contact details for representatives.

For example, if a representative legally changes their last name or updates their mobile number, this node operation allows you to push those changes to Straddle seamlessly.

Properties

Name Meaning
Representative Id The unique identifier of the representative to update (required).
Request Id Optional client-generated identifier to trace and debug a single request (sent as HTTP header).
Correlation Id Optional client-generated identifier to trace and debug a series of related requests (HTTP header).
First Name The first name of the representative (required).
Last Name The last name of the representative (required).
Dob Date of birth of the representative in ISO 8601 format (YYYY-MM-DD) (required).
Ssn Last 4 Last 4 digits of the representative’s Social Security Number (required).
Email Email address of the representative (required).
Mobile Number Mobile phone number of the representative (required).
Relationship JSON object describing the relationship information of the representative (required).
External Id Optional unique identifier for the representative in your own system for cross-referencing.

Output

The node outputs the JSON response from the Straddle API after updating the representative. This typically includes the updated representative object with all current fields reflecting the changes made.

The output json field structure corresponds to the representative resource schema, which may contain nested objects such as address, compliance profile, and relationship details.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Straddle API via an API key credential.
  • The base URL for API requests depends on the configured environment (e.g., sandbox or production).
  • Proper permissions to update representative data in the Straddle account are necessary.

Troubleshooting

  • Missing Required Fields: If required properties like representative_id, first_name, or dob are missing, the API will reject the request. Ensure all mandatory fields are provided.
  • Invalid Date Format: The dob must be in ISO 8601 format (YYYY-MM-DD). Incorrect formats will cause validation errors.
  • Authorization Errors: If the API key credential is invalid or lacks permission, the request will fail with authentication errors.
  • Malformed JSON in Relationship: The relationship property expects valid JSON. Invalid JSON syntax will cause parsing errors.
  • Representative Not Found: If the representative_id does not exist, the API will return a not found error.

To resolve these issues:

  • Double-check all required inputs and their formats.
  • Verify API credentials and permissions.
  • Validate JSON input for complex fields before execution.

Links and References

Discussion