Organization Merge API is public | Community
Skip to main content

Organization Merge API is public

  • April 10, 2024
  • 4 replies
  • 0 views

Hey Org Merge community,

I'm pleased to share that we have released our public API's for Organization Merge. 

There are three methods supported via API;

  1. Create a new organization merge
  2. Show the status of an organization merge
  3. List all organization merges for a specific organization

These APIs should allow for the automation of organziation merges where Zendesk is not the source of truth of your organization data. Additionally, the status APIs will allow for the remote  notification back to the source system and / or user when org merge is remotely triggered via API.

Although these APIs are listed in our standard developer docs, they should be treated as an extension of the Org Merge Beta and some initial testing is recommended.

All other information about these methods are covered in our developer docs, but if you have a specific question that you'd like answered you can post it here.

Hope this is helpful. 

Thanks,
James

4 replies

Thomas92
  • July 11, 2024

Hi, 

The endpoint to Merge Organization With Another Organization doesn't seems to work when I tried to merge two organization using Postman. 

I got a 404 status and : 

{
   "error": "InvalidEndpoint",
   "description": "Not found"
}

Does anyone encounter the same error ? 

 


Alex142
  • July 11, 2024

Hey @thomas92 - the "Merge Organization With Another Organization"  API is working on our end.

Can you please confirm the path you're seeing 404s on?

It should be: POST https://{your_domain}/api/v2/organizations/{organization_id}/merge.


Thomas92
  • July 12, 2024

Hi, 

I was misled by the imported fork of the API that indicate it is a PUT :

 

 

I change it into a POST and it works like a charm. Thanks. 

Have a nice day. 


Alex142
  • July 18, 2024

Hi @thomas92 - thank you for providing that extra information, I'm sorry that the Postman collection was showing the wrong value.

We had an issue that temporarily caused the collection to stop syncing, but that's now been fixed!

You should now see the correct HTTP method:

Thanks again for reporting this!