Skip to main content

API setup guide for accessing registration data

Learn how to configure and access the registration API in Launchpad to retrieve participant data and integrate with external platforms.

Updated over a month ago

The registration API in Launchpad allows administrators to extract core and custom registrant data through a secure endpoint. Whether you're syncing with CRMs, generating external reports, or building integrations, this guide walks through the setup and access process, including authentication, data structure, and expected responses.


Default API fields

By default, the API returns the following fields:

  1. First name

  2. Last name

  3. Phone

  4. Mobile phone

  5. Confirmation number

  6. Registration type

  7. Registration date

  8. Paid date

  9. Email

  10. Classification type

  11. Total collected

  12. Balance due

  13. Promo code

  14. Promo code description

  15. Marketing code

  16. Marketing code description

  17. Marketing channel

  18. Primary package

  19. Check-in date

  20. Job title

  21. Company name

  22. State

  23. Country


Authentication token setup

To use the API, you must generate an authentication token:

  • The token must have the “Registrations” permission enabled.

  • Each token is event-specific and should be securely stored.

  • This token is required in every API request under the params object.


Extending API fields

Admins can include up to 20 additional data fields from:

  • Profile additional questions

  • Registration additional questions

Each field must be selected from a dropdown and assigned a label, which is reflected in the API output.


Making an API request

To call the API:

  1. Use the format:

https://[event-url]/api/json-rpc

Example:

https://exampleevent.com/2025/api/json-rpc
  1. Use this JSON request format:

{   "jsonrpc": "2.0",   "method": "Registrations.getBasicInfo",   "params": {     "token": "your-auth-token"   },   "id": 1 }
  • Replace "your-auth-token" with your actual token.

  • Use optional filters inside the params field to narrow down the data.

API response example

A successful response will return paginated registrant records:

{   "result": {     "startingRegistration": "1",     "lastRegistration": "1000",     "totalRegistrations": "1200",     "registrations": [       {         "confirmation": "ABC123",         ...       }     ]   },   "id": "1",   "jsonrpc": "2.0" }

Error response example

If authentication fails or the request is malformed, you’ll receive an error message:

{   "error": {     "code": -32000,     "message": "Unauthorized access",     "data": null   },   "id": null }

Launchpad’s registration API offers a reliable way to access key event data programmatically. By configuring the authentication token, selecting the necessary fields, and formatting the API call correctly, you can integrate registration data into external systems with ease. Be sure to monitor your token usage and handle errors gracefully to maintain secure and efficient data flows.

Did this answer your question?