Bygg med Peoply API-et

Prompts for kodeagenten din

Bruk OpenAPI JSON i en integrasjon

Peoply API base URL: https://api.peoply.app
Peoply API docs: https://api.peoply.app/api
Peoply OpenAPI JSON: https://api.peoply.app/api/openapi.json
Peoply agent docs: https://peoply.app/llms.txt

Use the Peoply API to implement [DESCRIBE YOUR GOAL] in this repository. Inspect the repository and follow its existing architecture, data-fetching, error-handling, and test conventions.

Before planning or writing code, fetch and read https://api.peoply.app/api/openapi.json. Use paths, HTTP methods, operationId, parameters, required fields, enums, and schemas as the source of truth. Map the goal to the exact operations it needs. If authentication, response schemas, or behavior are missing or ambiguous, state that clearly instead of guessing. Prefer public GET operations unless the task explicitly requires protected access.

Present a short plan, then implement it. Build requests from the documented contract, validate untrusted responses at the application boundary, and handle non-2xx responses, timeouts, pagination, and empty data. Do not expose credentials or personal data. Add focused tests, run the repository checks, and summarize the API operations used.

Bygg en arrangement-feed

Peoply API base URL: https://api.peoply.app
Peoply API docs: https://api.peoply.app/api
Peoply OpenAPI JSON: https://api.peoply.app/api/openapi.json
Peoply agent docs: https://peoply.app/llms.txt

Add an upcoming Peoply events feed to this repository. Inspect the repository first and follow its existing architecture, data-fetching, UI, and test conventions.

Read https://api.peoply.app/api/openapi.json before writing code. Use the public GET https://api.peoply.app/events operation with afterDate set to the current ISO timestamp, orderBy=startDate, and orderDirection=asc. Include parameters marked as required by the current schema. Paginate with skip and take. Do not invent response fields; render only fields confirmed by OpenAPI or an existing typed client.

Show clear loading, empty, and error states. Handle time zones, URL encoding, request cancellation, and non-2xx responses. Do not send credentials or use protected or write operations. Add tests for the request parameters, pagination, and error state. Run the repository checks and summarize the result.

Legg til foreningssøk

Peoply API base URL: https://api.peoply.app
Peoply API docs: https://api.peoply.app/api
Peoply OpenAPI JSON: https://api.peoply.app/api/openapi.json
Peoply agent docs: https://peoply.app/llms.txt

Add Peoply organization search to this repository. Inspect the repository first and reuse its existing search, data-fetching, UI, and test patterns.

Read https://api.peoply.app/api/openapi.json before writing code. Use the public GET https://api.peoply.app/organizations operation and its name query parameter. Build query strings with URLSearchParams, debounce user input if this is an interactive client, cancel stale requests, and use the organization's stable ID for selection and links. Do not invent response fields.

Show useful loading, no-results, and error states. Do not send credentials or expose protected organization data. Add tests for URL encoding, stale responses, no results, and API errors. Run the repository checks and summarize the result.

Legg til kalenderabonnement

Peoply API base URL: https://api.peoply.app
Peoply API docs: https://api.peoply.app/api
Peoply OpenAPI JSON: https://api.peoply.app/api/openapi.json
Peoply agent docs: https://peoply.app/llms.txt

Add a public Peoply calendar subscription for an organization in this repository. Inspect the repository first and follow its existing component, link, and test conventions.

Read https://api.peoply.app/api/openapi.json before writing code. Use the public GET https://api.peoply.app/organizations/{orgId}/calendar.ics operation with a real stable organization ID from the surrounding data. Link directly to the feed unless the existing architecture requires a server proxy. Do not parse and rebuild the ICS payload, add credentials, or use a display name in place of orgId.

Make the action clear and accessible. Verify the generated URL, preserve the .ics response, add a regression test, run the repository checks, and summarize the result.

Ressurser

Viktig før du starter

  • Start med offentlige GET-kall for arrangementer og foreninger.
  • Bruk OpenAPI-kontrakten, ikke modellens hukommelse, som fasit.
  • Ikke legg passord, cookies eller persondata i en prompt.
  • Beskyttede kall bruker Peoplys browserbaserte innlogging og skal ikke videresendes til en autonom agent.
  • Organisasjoner kan også importere og dele arrangementer via offentlige .ics-feeder.