Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5661

PostalMethods returns error, possible API change.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.13.0
    • Fix Version/s: 5.13.2
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      PostalMethods was not working, returning an authentication error.

      API Docs:
      https://documenter.getpostman.com/view/10877655/2sAYJ1j2Ce#5fe4fff7-72ca-4ea2-a702-6a06bcda6fde

      Issues Found:

      Summary of Fixes Applied

      1. Reply Envelope Address Fix (Critical)

      • Changed from returnAddress.* to replyonEvelopeAddress.* when reply envelope is enabled
      • Added separate reply_envelope_address property

      2. Settings Loading Fix (Critical)

      • Changed to fetch PostalMethods settings directly using getSetting() instead of from company_settings array
      • This fixes the encrypted API key not being loaded

      3. API Compatibility Updates

      • Added required refId parameter (generates unique ID per request)
      • Added Name fields to sendToAddress and returnAddress
      • Added fileUrl parameter (empty string)
      • Added appendReplyOnEnvelopeAddress parameter
      • Changed file upload parameter from 'File' to 'file' (lowercase)
      • Improved error response parsing to check success and unAuthorizedRequest fields

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description They broke it again it seems.

        New API docs:
        https://documenter.getpostman.com/view/10877655/2sAYJ1j2Ce#5fe4fff7-72ca-4ea2-a702-6a06bcda6fde
        PostalMethods was not working, returning an authentication error.

        API Docs:
        https://documenter.getpostman.com/view/10877655/2sAYJ1j2Ce#5fe4fff7-72ca-4ea2-a702-6a06bcda6fde

        Issues Found:

        Summary of Fixes Applied

        1. Reply Envelope Address Fix (Critical)
        - Changed from returnAddress.* to replyonEvelopeAddress.* when reply envelope is enabled
        - Added separate reply_envelope_address property

        2. Settings Loading Fix (Critical)
        - Changed to fetch PostalMethods settings directly using getSetting() instead of from company_settings array
        - This fixes the encrypted API key not being loaded

        3. API Compatibility Updates
        - Added required refId parameter (generates unique ID per request)
        - Added Name fields to sendToAddress and returnAddress
        - Added fileUrl parameter (empty string)
        - Added appendReplyOnEnvelopeAddress parameter
        - Changed file upload parameter from 'File' to 'file' (lowercase)
        - Improved error response parsing to check success and unAuthorizedRequest fields
        admin Paul Phillips made changes -
        Summary Update PostalMethods to be compatible with their latest v2 API PostalMethods returns error, possible API change.
        admin Paul Phillips made changes -
        Issue Type Task [ 3 ] Bug [ 1 ]
        admin Paul Phillips made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        abdy Abdy Franco made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 39 minutes [ 9540 ]
        Worklog Id 18075 [ 18075 ]
        abdy Abdy Franco made changes -
        Status Reopened [ 4 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            admin Paul Phillips
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              28/Jan/26

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 39 minutes
              2h 39m