Legacy Dev Forum Posts

 View Only

Sign Up

Update an email route's BCC address via API

  • 1.  Update an email route's BCC address via API

    Posted 06-05-2025 18:19

    Nebojsa_Radovanovic | 2021-03-29 20:53:20 UTC | #1

    Hi, I've been trying to find an API to update the BCC address in an email address configuration, since doing it from the UI is not possible if the email has been created already, and came upon this API: PUT /api/v2/routing/email/domains/{domainName}/routes/{routeId}

    When trying to run this API, field "pattern" is required, but it is not clear what value should "pattern" have, the documentation about it only says that it is supposed to be "The search pattern that the mailbox name should match." I tried various things such as the domain name, full email, parts of it, but nothing works, the server returns a 500 error: { "message": "The server encountered an unexpected condition which prevented it from fulfilling the request.", "code": "internal.server.error", "status": 500, "contextId": "c8eb5af0-99eb-47cd-8ab7-d1c06d21480c", "details": [], "errors": [] }

    For reference, i'm using this body (email domain edited to be domain.com): { "pattern": "donations@domain.com", "fromName": "Donations", "fromEmail": "donations@domain.com", "autoBcc": [ { "email": "test@domain.com" } ] }

    Any idea why this isn't working? What is the correct way to populate the "pattern" key here?


    tim.smith | 2021-03-30 21:26:48 UTC | #2

    Can you confirm what environment you were using and when you made that request? I can't find the context ID in us-east (as indicated on your profile) in the last 7 days.


    Nebojsa_Radovanovic | 2021-03-31 07:35:29 UTC | #3

    Oh yeah, forgot to mention, we tried this in a Canada region org.


    tim.smith | 2021-03-31 16:45:37 UTC | #4

    I chatted with the dev team and I believe you're missing the id property; the docs are incorrect. Can you also open a case with Genesys Cloud Care to report the incorrect API documentation? Reporting the bug there will attach standard SLAs to the issue report to ensure it's addressed appropriately.


    system | 2021-05-01 16:45:41 UTC | #5

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 10444