mocop
Browse · Docs · Guide · Analyze

AgendaForge Public REST API

API by AgendaForge · rest

The HTTP API that powers the AgendaForge Zapier, Make.com, and n8n integrations, and any custom server-to-server integration. Every request is authenticated with an organization API key (created in Settings > API Tokens; keys begin with afk_live_ and are shown once). Keys carry named scopes chosen at creation: public_api (this API, on by default), mcp:read and mcp:write (the AgendaForge MCP server for AI clients), and tickets:import (ticket imports, never on by default). Every endpoint here requires the public_api scope, except POST /api/v1/imports/tickets, which requires tickets:import; requests with a key that lacks the required scope receive 403 FORBIDDEN. All requests and responses are JSON. Every error, 4xx and 5xx alike, is JSON of the shape { "error": { "code": "...", "message": "..." } } with a machine-readable code and a human-readable resolution hint. Unknown paths under /api/v1 return 404 NOT_FOUND with the list of valid endpoints. Pagination: list endpoints (GET…

Endpoint: https://api.agendaforge.app/

Verification: observed. Source: crawl.

Capabilities (14)

  • List contacts (cursor-paginated)
  • Create a contact
  • Create up to 100 contacts in one request
  • Subscribe a target URL to a trigger event (REST Hook)
  • Remove a webhook subscription
  • Import up to 1 000 contacts asynchronously
  • Add update or cancel up to 1 000 imported tickets
  • Poll an async job
  • Validate the API key and return its organization
  • List an event's sessions (cursor-paginated)
  • Create a session
  • List an event's sponsors (cursor-paginated)
  • Create a sponsor
  • Pull sample records for a trigger event
About · Contact · Privacy