ActiveNet SF RecPark API
Integuru generates a production-ready HTTP API for ActiveNet as deployed by San Francisco Recreation and Parks, the portal residents use for classes, camps and facility rentals. 7 verified actions run on your own resident login: search activities and facilities, check facility availability, read activity detail, and list your household members and registrations.
7
Verified actions live today
<3 sec
Response latency per call
99.9%+
Reliability rate on generated APIs
24/7
On-call maintenance on Production plans
Integration facts
- Authenticates against
- https://apm.activecommunities.com/sfrecpark/
- Authentication
- Login flows, including 2FA, handled by Integuru using your own ActiveNet SF RecPark credentials.
- Approach
- Direct HTTP requests, with no browser automation or RPA involved.
Endpoints
Available actions
Don't see the action you need?
The actions above cover the most common ActiveNet SF RecPark integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.
Guide
ActiveNet SF RecPark integration guide
Does ActiveNet have a public API?
ACTIVE Network, which runs ActiveNet, publishes two developer surfaces: an Activity Search API that returns public activity listings to developers who apply for a key, and an authenticated ACTIVE Net API that agencies use to integrate their own systems. Neither lets a resident act on their own account at one agency's site, such as San Francisco Recreation and Parks. Integuru's ActiveNet SF RecPark integration provides 7 verified actions on your own resident login at apm.activecommunities.com/sfrecpark.
| | ACTIVE Network developer APIs | Integuru for ActiveNet SF RecPark | |---|---|---| | Access | Key by application, or agency credentials | Your own resident login | | Covers | Public activity listings; agency-side records | Your household and registrations, facility availability, and search on the SF site | | Best for | Cross-agency aggregators and the agencies themselves | Apps and agents acting for one resident |
What you can do with the ActiveNet API
Find a class or camp. search_activities takes a free-text keyword, an age band with min_age and max_age, center_ids and category_ids as arrays, and a start_date and end_date window in YYYY-MM-DD. page_size runs 1 to 50 and defaults to 20; page_number is 1-based and echoed back as page. The filter ids are not published anywhere; read them from filters.categories and filters.centers in an earlier response. get_activity_detail takes the activity_id from a search result.
Find a court, field or room. search_facilities returns reservable facilities, 20 per page, filtered by keyword, a minimum attendee capacity, center_ids, facility_type_ids and event_type_ids. Pass back the search_client_id from the previous page so paging stays consistent across one search. get_facility_availability then takes a facility_id and a window of up to 31 days; start_date defaults to today and end_date to seven days later.
Read your household. get_login_user returns the signed-in resident. list_family_members returns the household, with include_retired to add archived members; the flag is honoured by the primary member endpoint and ignored when the account falls back to the household endpoint, and the response's source field tells you which one answered. list_my_registrations returns registration transactions with a start_date and end_date range, page_size 1 to 50, an optional filters array of filter ids, and attention_only to return just the records flagged as needing action.
Registering for an activity and reserving a facility are built on request through the Managed Service, starting from the ids these actions return.
Who uses this
Family-schedule apps run list_my_registrations and list_family_members nightly so a parent's calendar shows every swim lesson and camp week the household is enrolled in, without a login screen. Assistants built on the AI agents pattern take a request like a Saturday morning pickleball court for four, call search_facilities with attendee: 4, then get_facility_availability for the shortlist, and answer in one turn. Teams aggregating court time across San Francisco pair this page with Rec.us, which runs the city's tennis and pickleball courts, and with CourtReserve for private clubs, all through one login-based auth model.
Setup notes
Integuru authenticates against the SF Rec and Park ActiveNet site with the resident's own credentials and returns only that resident's household, registrations and the catalogue any signed-in resident can search. Every date is YYYY-MM-DD. activity_id and facility_id accept an integer or a numeric string. Keep availability windows to 31 days or fewer, and when you paginate search_facilities, carry search_client_id forward from the first page.
Get started
Install the CLI and connect your ActiveNet login:
npm install -g integuru
Or sign in at app.integuru.com and add ActiveNet SF RecPark. For registration and reservation actions, or for another city's ActiveNet site, the Managed Service scopes and builds them against your account. The integrations catalogue lists every live platform.
Good to know
Before you start
- Can I use it today?
- Yes. Every action listed above has been verified against live ActiveNet SF RecPark traffic. Install the CLI or sign in at app.integuru.com, connect your ActiveNet SF RecPark account, and start calling the endpoints.
- What if ActiveNet SF RecPark changes or breaks?
- On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
- What does it cost?
- Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.
FAQ