Support

Home Forums Event Espresso Premium json api problem getting events

json api problem getting events

Posted: December 27, 2013 at 6:52 am


Gabriel Solano

December 27, 2013 at 6:52 am

the problem is i need to create the url to get the events for an Android app
i have the session id, i could login
and i create this url:
http://ticketdog.es/espresso-api/v1/events/{fzy…
but the answer of the system is:
{“status”:”Query parameter ‘q’ not a valid parameter of resource ‘Event'”,”status_code”:400}
i have no idea to continue or get a correct answer


Dean

December 27, 2013 at 7:26 am

Hi,

Have you made sure the API is public? Check the JSON settings in the Event Espresso menu.


Gabriel Solano

December 27, 2013 at 7:40 am

hello
yes the api is public, what else coul it be?


Tony

  • Support Staff

December 27, 2013 at 8:03 am

Hi Gabriel,

Can I ask which Server Platform you are using? Linux/Apache?

You could also try enabling ‘API Debug mode’ and see if that throws any more errors. Event Espresso -> API Settings. ‘API Debug Mode’


Gabriel Solano

December 28, 2013 at 7:42 am

ok i will turn on debugging mode.
anyway you can send me an example of an event query with the session id concat?
i keep getting an error that a parameter is missing when i try to query an event.


Dean

December 30, 2013 at 5:46 am

Hi Gabriel,

I have asked one of the developers to see if he can provide further assistance with this. Please bear with us, as due to the Christmas period staff working hours are erratic.


Michael Nelson

  • Support Staff

December 30, 2013 at 1:36 pm

So if you fetched the session Id and let’s say it’s ‘monkey123’, and your blog’s url is ‘mysite.com’, then you would send the request to ‘mysite.com/espresso-api/v1/events/monkey123’.

The error you’re receiving, saying that “Query parameter ‘q’ not a valid parameter of resource ‘Event'”, means the system thinks you’re sending a query like the following: mysite.com/espresso-api/v1/events/monkey123?q=123 (ie, where “q” is that query parameter). And of course, “q” is not a valid query parameter (whereas “id”,”limit”,”Datetime.id”, etc, are. See documentation for full list).
Does that answer your question?


Gabriel Solano

January 2, 2014 at 9:13 am

ok two thing
one. i cant find the option to turn on the debugging feature i’m using ver.
Event Espresso – 3.1.35.P

two. i still cant get it to work
after login the query that i create is:
http://ticketdog.es/espresso-api/v1/events/0hreu2qy3b?event_name__like=%25tango%25
but the reply is the same:
{“status”:”Query parameter ‘q’ not a valid parameter of resource ‘Event'”,”status_code”:400}


Josh

  • Support Staff

January 2, 2014 at 1:56 pm

Here is a screenshot that points to where you can turn on debugging.


Michael Nelson

  • Support Staff

January 2, 2014 at 4:37 pm

Thanks Gabriel for posting your exact queries being used. I can reproduce the issue on your server, but the exact same query works fine on mine. So I think there’s nothing wrong with your usage of the API.

SO… What version of the json api are you using? And what version of Event Espresso core? What other addons do you have active? (which may be interfering and adding the ‘q’ query parameter)


Gabriel Solano

January 3, 2014 at 4:22 am

hi heres is long list of plugins being used:
Event Espresso version 3.1.35.P
WordPress version WP 3.7.1
Installed plugins
Admin Menu Editor Pro by Janis Elsts version 1.92,
Akismet by Automattic version 2.5.9,
All In One Schema.org Rich Snippets by Brainstorm Force version 1.1.5,
Appointments+ by Hakan Evin version 1.4,
Cookie warning by Marie Manandise, MAJWeb version 1.3,
Duplicator by LifeInTheGrid version 0.4.6,
Event Espresso – Calendar by Event Espresso version 2.2.0.p,
Event Espresso – Custom Template Display by Event Espresso version 1.0,
Event Espresso – Pasarela de pago para CECA (modulosdepago.es) by Mikel Martin (ZhenIt Software) version 1.0,
Event Espresso – MailChimp Integration by version 1.2,
Event Espresso – Members Addon by Event Espresso version 1.9.8.p,
Event Espresso – Multi Event Registration by Seth Shoultes version 1.0.5.p,
Event Espresso – Permissions by Event Espresso version 1.5.5.p,
Event Espresso – Roles and Permissions Pro by Event Espresso version 2.0.6,
Event Espresso – Recurring Events by Event Espresso version 1.1.8.p,
Event Espresso Template – Category Accordion by Event Espresso version 1.0.p,
Event Espresso Template – Recurring Events Table w/ Dropdowns by Event Espresso version 1.0,
Event Espresso – Ticketing by Event Espresso version 2.1.p,
Event Espresso by Event Espresso version 3.1.35.P,
Gravity Forms + Custom Post Types by Brad Vincent version 3.0.1,
Gravity Forms by rocketgenius version 1.7.13,
Gravity Forms MailChimp Add-On by rocketgenius version 2.3,
Gravity Forms Signature Add-On by Rocketgenius version 1.3,
Gravity Forms User Registration Add-On by rocketgenius version 1.7,
Installer by OnTheGoSystems Inc. version 0.7.1,
Post Types Order by Nsp Code version 1.6.5,
Pretty Link Pro by Caseproof version 1.6.5,
Revolution Slider by ThemePunch version 3.0.95,
User Switching by John Blackbourn version 0.8.5,
WordPress SEO by Joost de Valk version 1.4.22,
WP SMTP by BoLiQuan version 1.1.6,
WP Smush.it by WPMU DEV version 1.6.5.4,
Afiliado Royal by Caseproof, LLC version 1.3.3


Josh

  • Support Staff

January 3, 2014 at 8:04 am

Hi Gabriel,

I don’t see which version of the JSON api in your list. Can you check?


Gabriel Solano

January 3, 2014 at 10:40 am

Event Espresso API Plugin
Desactivar | Editar | Check compatibility
A JSON/XML API for Event Espresso

Versión 2.0.2.p | Por Event Espresso, (Mike Nelson) | Visitar la web del plugin


Josh

  • Support Staff

January 3, 2014 at 3:22 pm

Hi Gabriel,

It may help to update the version you have to be current (v.2.1 is the current version).


Michael Nelson

  • Support Staff

January 3, 2014 at 3:36 pm

Yeah I agree with Josh. However, I’m guessing one of those addons you have is adding a random ‘q’ to the querystring. WE’ve tested the JSON api with all the event espresso addons and there’s no conflicts. But those other ones…. easiest way to do that would be to deactivate them one by one and see if the problem persists, or start with none active and activate them one by one…

The support post ‘json api problem getting events’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso