Create a PLACE with Zapier

Todd S

Zapier knows WordPress. It has built-in capabilities to create users and posts, find users and posts, update posts, and upload media. But it doesn't know GeoDirectory, so it doesn't know how to create a place. But I believe it's doable with their new (still in beta) feature within the WordPress app: API Request. This is basically a "roll your own" option. It allows me to specify the following:

HTTP Method
URL
Query String Parameters
Additional Request Headers
Body

I haven't got it quite right yet. Has anybody done this already?

Todd S

Using Zapier's WordPress API Request method I've been able to successfully GET a listing by ID, I've been able to successfully GET the system_status, and I've been able to successfully DELETE a place. Authentication is working great. What's failing is this POST. I'm sure I'm messing up the Body somehow. I'm getting this error every time:

{"code":"rest_missing_callback_param","message":"Missing parameter(s): zip","data":{"status":400,"params":["zip"]}}

So am I missing a callback parameter? I understand the programming concept of a callback but I haven't seen anything called callback in any of the GD API documentation. Or am I missing the zip? I absolutely have the zip in there, and I even added it to the URL to boot (it fails the same way without it). What am I doing wrong? What should the body of the call look like to add a place?

I modeled this off of the Postman example screenshot here: https://wpgeodirectory.com/docs-v2/api/posts/. When that failed I added a couple more values. BTW, I haven't been able to get Postman to do anything for me. It doesn't want to authenticate for some reason. I've tried both API Key and Basic Auth and I get 401 Unauthorized every time.

Thanks in advance, everyone!

Todd S

I just tried specifying all the data as URL parameters and got exactly the same reply. Help! Have I discovered a GD bug?

https://nearbylisting.com/wp-json/geodir/v2/places/?post_title=Bogus&post_content=TBD&author=9&zip=75001&post_category=108

rachell

I wish I had the skills to assist, but it is all above my head. Good Luck.

Todd S

I figured this out. For you, future reader, I will document how I fixed it. The specific errors were red herrings. The problem was that the Body of the message was being entirely ignored. To fix that I had to add an HTTP header. In the Zapier configuration screenshot above, under Additional request headers, I added this key-value pair.

Content-Type: application/json