Persistent API `data discrepancies` preventing programmatic NAP updates, seeing `403 forbidden` on key aggregators.

Author
Amit Gupta Author
|
1 hour ago Asked
|
1 Views
|
0 Replies
0

hey everyone, trying to automate NAP updates for a client with a custom script, but hitting a wall on some crucial local citations.

  • i'm consistently getting a 403 forbidden error when attempting to push changes programmatically, even with valid auth tokes.
  • this error is particularly prevalent when the system flags what it calls "minor data discrepancies".
  • will include a sample error log in the full post to illustrate the specific API response:
HTTP/1.1 403 Forbidden
Content-Type: application/json
{
  "error": {
    "code": 403,
    "message": "Access Denied: Data discrepancy detected. Cannot update fields with existing, conflicting data.",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "reason": "DATA_DISCREPANCY",
        "domain": "citation-api.example.com",
        "metadata": {
          "field": "address",
          "current_value": "123 Main St",
          "attempted_value": "123 Main Street"
        }
      }
    ]
  }
}
  • this is really slowing down our nap consistency efforts. any insights on how to bypass or programmatically resolve these data discrepancies?

waiting for an expert reply.

0 Answers

No answers yet.

Be the first to provide a helpful answer!

Your Answer

You must Log In to post an answer and earn reputation.