Data Integrity Suite Product Announcements

 View Only

Improving Performance & Compliance: Region Checks for Data Integrity API Usage

  Thread closed by the administrator, not accepting new replies.
  • 1.  Improving Performance & Compliance: Region Checks for Data Integrity API Usage

    Posted 08-01-2025 05:54
    Edited by Product Communications 08-01-2025 05:54
    No replies, thread closed.

    28 July 2025

    New Region-Based Restrictions for Precisely API Calls

    Moving forward, your API calls will only be successful if the requested region aligns with the regions you have subscribed to for that specific API service. If an API request specifies a region for which you do not have a subscription, the call will result in an error message.

    This change helps us

    • Ensure you receive the best performance from services allocated to your subscribed regions.
    • Maintain compliance with regional data regulations.
    • Optimize resource allocation to better serve all our customers.

    Illustrated Example

    Let's say you have an active subscription for our Geocode API in the AMER (Americas) region.

    • Successful Call Example: If you make a Geocode API request for an address located in New York, USA (which falls within the AMER region), your request will be processed successfully.

    JSON

    // Example Geocode API request for an AMER address

    {

      "address": "1600 Amphitheatre Parkway, Mountain View, CA",

    }

    You'll receive a successful response with geocoding results.

    • Error Call Example: However, if you make a Geocode API request for an address located in London, UK (which falls within the EMEA region), and your subscription only covers AMER, your request will fail, and you'll receive an error message.

    JSON

    // Example Geocode API request for an EMEA address with AMER subscription

    {

      "address": "10 Downing Street, London, SW1A 2AA, UK",

    }

    You would receive an error similar to

    JSON

    {

      "code": "403",

      "message": "Forbidden: Region not authorized for this subscription."

      // Or similar message indicating region mismatch/unauthorized access

    }

    Action Required 

    Please ensure that your API requests for all Precisely services adhere to the regions you have purchased. Review your current subscriptions and adjust your API call parameters as necessary to avoid service interruptions once this change is live.

    If you have any questions about your subscribed regions or need to adjust your subscription to include additional regions, please don't hesitate to contact your account representative or our support team.

    We appreciate your understanding and cooperation as we continue to enhance our services.

    This change will go into effect on Thursday August 28, 2025.

    Contact Information

    If you would like technical assistance, please contact the Precisely Global Support team at Precisely Support.

    Product documentation is available in the Precisely Help Center at help.precisely.com.