GoTo Connect APIs Host Migration

This guide outlines the steps to smoothly transition your GoToConnect API calls from api.jive.com, which was marked as deprecated, to the new GoToConnect API host: api.goto.com.

Migration Timeline

The migration to the new host is very important and must be done as soon as possible. It is crucial to complete this migration as swiftly as possible to ensure uninterrupted services.

Please take note that precisely one year from the date of this document's publication, on January 15th, 2025, the old host will be officially decommissioned. As a result, it is imperative to complete your migration before this deadline.

Should you require assistance or encounter any challenges during this process, our team is here to provide guidance and support. Your timely action is greatly appreciated as we work together to ensure a seamless transition.

Overview of Changes

The primary adjustment you will need to make to your API calls for GoTo Connect is to replace the old host with the new one: api.goto.com. Below, we provide a few illustrative examples to guide you through this process.

API Call Examples

Here are some before-and-after examples to showcase the necessary modifications:

curl --request GET \
    --url 'https://api.jive.com/voice-admin/v1/extensions?accountKey=SOME_INTEGER_VALUE' \
    --header 'authorization: Bearer ACCESS_TOKEN'
        

curl --request GET \
    --url 'https://api.goto.com/voice-admin/v1/extensions?accountKey=SOME_INTEGER_VALUE' \
    --header 'authorization: Bearer ACCESS_TOKEN'
        

curl --request POST \
    --url 'https://api.jive.com/calls/v2/calls' \
    --header 'authorization: Bearer ACCESS_TOKEN' \
    --header 'content-type: application/json'                      
    --data '{                                                    
        "dialString": "SOME_STRING_VALUE",                    
        "from": {                                          
          "lineId": "SOME_STRING_VALUE" 
        } 
    }'
        

curl --request POST \
    --url 'https://api.goto.com/calls/v2/calls' \
    --header 'authorization: Bearer ACCESS_TOKEN' \
    --header 'content-type: application/json'                      
    --data '{                                                    
        "dialString": "SOME_STRING_VALUE",                    
        "from": {                                          
          "lineId": "SOME_STRING_VALUE" 
        } 
    }'
        

Remember, the key change lies in updating the host to api.goto.com across your API calls to api.jive.com.

Breaking Changes (Rate Limiting)

As of now, we are aware of only one possible breaking change related to rate limiting. Our rate limiting mechanism has been improved, and the changes have the potential to impact your requests.

Our team has diligently worked to ensure a seamless transition process. However, should you encounter any unexpected issues or have concerns, please do not hesitate to reach out to us via email at developer-support@goto.com. Your feedback and questions are highly valuable to us. Your inquiries will receive prompt attention and support as we work together to ensure a smooth migration process.