WordPress/Zapier connection return a 400 error “Invalid paramater: status”

• 

  rocheapiandyou · Member · Nov 10, 2023 at 11:03 am

  • Copy link
  • Add topic to favorites

  Hi,

  I have a Zappier connection with my WordPress but one of my zap turn off by itself with this error message : “Invalid parameter: status”

  The zap is triggered on the update of a post with the “Private” status. When I turn on the zap and run a test with a private post, everything is fine but after a while, the zap turn off by itself with the error…

  I have contact the Zapier support but after 2 month of investigation, they do not know what is going wrong. Their last answer is to look with the WordPress community to see if this bug sounds familiar to someone.

  Here is the log file Zapier send us :

  Credentials are censored and data may be formatted and/or truncated.
  
  permalink: /messages/integration_333/cb4223d3-7363-11ee-a84c-62cca94c37d5
  timestamp: 2023-10-25T18:24:54.412Z
  
  selected_api: WordPressCLIAPI@1.0.4
  object_action: updated_post
  object_depth: 1
  
  --------------------------------------------------------------------------------
  REQUEST
  --------------------------------------------------------------------------------
  
  GET :censored:37:c101717cee:/wp-json/wp/v2/member?per_page=100&orderby=modified&order=desc&status=private
  
  user-agent: Zapier
  Accept: application/json
  Content-Type: application/json
  X-ZAPIER-AUTH: :censored:245:49d87f16dc:
  
  --------------------------------------------------------------------------------
  RESPONSE
  --------------------------------------------------------------------------------
  
  400
  
  access-control-allow-headers: Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type
  access-control-expose-headers: X-WP-Total, X-WP-TotalPages, Link
  allow: GET
  connection: close
  content-type: application/json; charset=UTF-8
  date: Wed, 25 Oct 2023 18:24:54 GMT
  link: <:censored:37:c101717cee:/wp-json/>; rel="https://api.w.org/"
  strict-transport-security: max-age=31536000
  transfer-encoding: chunked
  vary: Origin
  x-content-type-options: nosniff
  x-robots-tag: noindex
  
  {
    "code": "rest_invalid_param",
    "message": "Paramu00e8tre(s) non valide(s)u00a0: status",
    "data": {
      "status": 400,
      "params": {
        "status": "Lu2019u00e9tat est interdit."
      },
      "details": {
        "status": {
          "code": "rest_forbidden_status",
          "message": "Lu2019u00e9tat est interdit.",
          "data": {
            "status": 401
          }
        }
      }
    }
  }

  Can someone as a lead on this ?

  Thanks !