Campground API returning 403 while Activity Search API v2 works
roaringfork25
Topic created 1 week ago
Hello,
I'm trying to evaluate the ACTIVE / ReserveAmerica Campground API for a campground discovery application.
I created a Campground API key in the developer portal, and the key shows as active there. However, requests to the documented Campground API endpoints are returning 403 Forbidden.
I tested requests in the documented format, including:
For comparison, I also created an Activity Search API v2 key under the same developer account, and that API works correctly with documented requests such as:
Is the Campground API still available for new integrations?
If so, is there any additional activation, entitlement, affiliate setup, or approval required beyond creating an active Campground API key in the portal?
Are the documented /camping/campgrounds, /camping/campground/details, and /camping/campsites endpoints still the correct endpoints to use?
Thank you.
Hello,
I'm trying to evaluate the ACTIVE / ReserveAmerica Campground API for a campground discovery application.
I created a Campground API key in the developer portal, and the key shows as active there. However, requests to the documented Campground API endpoints are returning 403 Forbidden.
I tested requests in the documented format, including:
http://api.amp.active.com/camping/campgrounds?pstate=CO&siteType=2001&expwith=1&amenity=4005&pets=3010&api_key=... and also:
http://api.amp.active.com/camping/campgrounds?pname=BROWN%20COUNTY&pstate=IN&api_key=... http://api.amp.active.com/camping/campground/details?contractCode=IN&parkId=570043&api_key=... http://api.amp.active.com/camping/campsites?contractCode=IN&parkId=570043&api_key=... All of these calls return 403 Forbidden.
For comparison, I also created an Activity Search API v2 key under the same developer account, and that API works correctly with documented requests such as:
http://api.amp.active.com/v2/search?query=running&category=event&start_date=2013-07-04..&near=San%20Diego,CA,US&radius=50&api_key=... That request returns 200 OK, so the issue appears specific to the Campground API product rather than the developer account generally.
Could you please confirm:
Is the Campground API still available for new integrations? If so, is there any additional activation, entitlement, affiliate setup, or approval required beyond creating an active Campground API key in the portal? Are the documented /camping/campgrounds, /camping/campground/details, and /camping/campsites endpoints still the correct endpoints to use? Thank you.
Message edited by roaringfork25 1 week ago