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

# v2.100.0 - Share Agreement Effective Date Clarification

> Clarified that effective_date cannot be set to null on share agreement PATCH endpoints

**Released 15th October 2026**

This patch release clarifies the behaviour of the `effective_date` field on the share agreement PATCH endpoints. No functional API behaviour has changed.

<Check>
  **Patch Release:** Documentation-only changes that clarify existing effective date behaviour. No breaking changes or functional modifications.
</Check>

## Documentation Updates

<AccordionGroup>
  <Accordion title="Share Agreement effective_date null-handling clarification" icon="calendar-day">
    **Updated endpoints:**

    * `PATCH /v2/orgs/share-agreements/{share_agreement_id}`
    * `PATCH /v2/orgs/tms-share-agreements/{tms_share_agreement_id}`

    **What changed:**

    The description of the `effective_date` field has been updated to clarify that it cannot be set to `null`. Omitting the field from the request body leaves the current value unchanged.

    **Before:**

    ```
    When data access begins. Check this before attempting to fetch fleet data.
    ```

    **After:**

    ```
    When data access begins. Check this before attempting to fetch fleet data.
    Cannot be set to null; omit it to keep the current value.
    ```

    The field type has also been formally documented as `string` with `date-time` format, consistent with how it is stored and returned.

    **Impact:**

    * No changes to API behaviour
    * Existing integrations are unaffected
    * If you previously sent `"effective_date": null` to clear the field, that request will be rejected — omit the field instead to leave it unchanged
  </Accordion>
</AccordionGroup>

## Integration Notes

<Steps>
  <Step title="Omit effective_date to preserve the current value">
    To update a share agreement without changing its effective date, simply omit the field from the request body:

    ```bash theme={null}
    # Correct — omit effective_date to leave it unchanged
    PATCH /v2/orgs/share-agreements/{share_agreement_id}
    {
      "expiration_date": "2026-12-31T00:00:00Z"
    }
    ```

    ```bash theme={null}
    # Incorrect — do not send null
    PATCH /v2/orgs/share-agreements/{share_agreement_id}
    {
      "effective_date": null
    }
    ```
  </Step>

  <Step title="No action required for most integrations">
    This is a documentation-only update. If your integration is currently working and does not send `"effective_date": null`, no changes are needed.
  </Step>
</Steps>

***

## Need Help?

<CardGroup cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/organizations-api">
    View complete endpoint documentation for the Organizations API
  </Card>

  <Card title="Contact Support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about your integration? Our team is here to help
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.