We’re trying to use the REST API to automatically create a listing (e.g. gd_places) from the WordPress PHP backend. Since it’s on HTTP local dev machine, we’re using OAuth 1.0a for authentication. After delving into GeoDirectory’s plugin for REST authentication, all the proper OAuth params (e.g. oauth_signature, oauth_consumer_key, etc.) have been implemented.
However, whenever the request is made, we get the error “Invalid signature – provided signature does not match”.
Trying with Basic Authentication on an HTTPS server with REST API enabled with all proper keys, it fails w/o error message, but the listing is NOT created. Instead, the response is the list of all current listings in that category as though a GET request was made.
We did not see any documentation on GeoDirectory’s site as to how to properly configure OAuth or any other authentication means to access the API from the backend.