REST API

Programming interface for connecting external systems—such as CRM, accounting, and marketing tools—to the congress software.

A REST API (Representational State Transfer Application Programming Interface) is a standardized interface that allows external systems to retrieve data from the congress software. It serves as the technical foundation for integration with CRM, accounting, marketing tools, and custom-developed applications.

Data format: JSON, occasionally XML

Authentication: API key, OAuth 2.0

Access model: GET, POST, PUT, DELETE via HTTP

What is a REST API?

A REST API is the gateway through which other software systems communicate with the congress platform. Instead of exporting data manually, external applications request exactly the information they need. "REST" describes an architectural style that operates via the HTTP protocol and is resource-oriented (e.g., "attendee," "booking," "session"), accessed using standardized methods (GET, POST, PUT, DELETE).

In the context of a congress, the API is the technical prerequisite for ensuring that accounting exports, CRM synchronizations, and marketing automation run smoothly.

Typical use cases

  • CRM synchronization: New attendees are automatically created in the CRM
  • Accounting: Payment and invoice data are sent directly to the ERP or accounting system
  • Marketing Automation: Event attendance triggers email campaigns or newsletter segmentations
  • Custom Frontend: Custom conference frontend uses the API to display program data
  • Mobile App: Conference app retrieves program, attendee lists, and push notifications via the API
  • Business Intelligence: Data is loaded into data warehouse solutions for comprehensive analysis
  • Sponsor Portal: Exhibitors view their lead data in real time via the API

Security and performance requirements

  • Authentication: OAuth 2.0 or API keys with restricted scopes – never full admin rights
  • Encryption: HTTPS only, exclude older TLS versions
  • Rate Limiting: Converia protects against excessive usage, clear quotas per token
  • Pagination: Large datasets are delivered in pages instead of all at once
  • Versioning: API versions explicitly (e.g., /v1/, /v2/) so that updates do not break existing integrations

Best practices for integration

  • Idempotent write operations: Duplicate requests must not create duplicate entries
  • Error handling with retry logic and dead-letter queues
  • Set up monitoring and alerting for API errors
  • Maintain documentation of your integrations – who uses which system and for what purpose

REST API in Converia

Converia provides a full REST API with OAuth 2.0 authentication: attendee and booking data, program structure, check-in status, and payment information can be imported into any system.

Connect Converia to your system landscape

With the Converia REST API, you can integrate accounting, CRM, or custom applications in hours instead of weeks.

Full REST API with OAuth 2.0 – for CRM, accounting, and custom integrations.