Censula API


Developer Portal for Conference Management System Integration

About API

Censula API enables you to retrieve conference data and papers from the system and display them on your website or integrate with other systems securely.

Secure

API Key authentication for every request

Fast

Responses in easy-to-use JSON format

Complete Data

Paper status, authors, revision history

Cross-Domain

CORS support for requests from any domain

Getting Started

Create an API Key to start using Censula API

Welcome, Guest Manage API Keys

Usage Examples

1. Retrieve your conferences

curl -X GET "https://censula.com/api/v1/conferences" -H "Authorization: Bearer YOUR_API_KEY"
👆 Replace YOUR_API_KEY with your actual API key.

2. Retrieve papers in a conference (with pagination)

curl -X GET "https://censula.com/api/v1/papers?conference_id=10&limit=20&page=1" -H "Authorization: Bearer YOUR_API_KEY"

Examples Count papers in a conference (.PHP)

// ────────────────────────────────────────────────────── // 1. CONFIGURATION SETTINGS // ────────────────────────────────────────────────────── $apiKey = 'Your_API_KEY'; // Replace with your actual API Key $conferenceId = xxx; // Replace with your specific Conference ID // ────────────────────────────────────────────────────── // ── Function to count total papers ── function countPapers($conferenceId, $apiKey) { $url = 'https://censula.com/api/v1/papers?conference_id=' . $conferenceId . '&limit=1&page=1'; $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, [ 'Authorization: Bearer ' . $apiKey, 'Content-Type: application/json' ]); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); curl_setopt($ch, CURLOPT_TIMEOUT, 10); $response = curl_exec($ch); $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE); curl_close($ch); if ($httpCode !== 200) { return ['error' => 'HTTP Error ' . $httpCode]; } $data = json_decode($response, true); if (!isset($data['data']['pagination']['total'])) { return ['error' => 'Invalid API response structure']; } return [ 'total' => $data['data']['pagination']['total'], 'conference' => $data['data']['conference']['title'] ?? 'N/A' ]; } // ── Execution ── $result = countPapers($conferenceId, $apiKey); if (isset($result['error'])) { echo 'Error: ' . $result['error']; } else { echo 'Total Papers in "' . $result['conference'] . '" = ' . $result['total'] . ' papers'; }
👆 Replace YOUR_API_KEY and adjust conference_id, limit, page as needed.

Examples PHP


3. Get conference details by ID

curl -X GET "https://censula.com/api/v1/conferences/10" -H "Authorization: Bearer YOUR_API_KEY"
👆 Replace YOUR_API_KEY and 10 with your conference ID.

4. Retrieve paper details with review history

curl -X GET "https://censula.com/api/v1/paper_details/11" -H "Authorization: Bearer YOUR_API_KEY"
👆 Replace YOUR_API_KEY and adjust id (paper ID).

Example JSON Response (for papers)

// Response (JSON) with pagination { "data": { "conference": { "id": 10, "title": "International Conference on Education, Technology and Innovation 2027" }, "papers": [ { "id": 11, "paper_title": "The Impact of Artificial Intelligence on Academic Conference Management", "status": "submitted", "submitted_at": "2026-06-10 19:35:04" } ], "pagination": { "current_page": 1, "per_page": 20, "total": 1, "total_pages": 1, "has_next": false, "has_previous": false } } }

API Endpoints

Core endpoints for accessing conference and paper data

Method Endpoint Description
GET /api/v1/conferences List your conferences
GET /api/v1/conferences/{id} Get conference details by ID
GET /api/v1/papers?conference_id={id}&limit={limit}&page={page} List papers in a conference (paginated)
GET /api/v1/paper_details/{id} Paper details + review history

Authentication

Every request to the API must include an Authentication Header with your API Key:

Authorization: Bearer YOUR_API_KEY

Important: API Keys are sensitive. Keep them private and never share them with others.

  • Always use HTTPS for API requests
  • Rotate your API keys regularly
  • Use environment variables to store API keys
  • Never commit API keys to version control

HTTP Status Codes

Understanding API response status codes

  • 200 OK - Request successful and data returned
  • 400 Bad Request - Invalid request parameters or format
  • 401 Unauthorized - Missing or invalid API Key
  • 403 Forbidden - Valid API Key but access denied to resource
  • 404 Not Found - Requested resource does not exist
  • 429 Too Many Requests - Rate limit exceeded, retry after delay
  • 500 Internal Server Error - Server-side error occurred

For Administrators

Manage conferences, users, review settings, and system configuration

Go to Dashboard